Connect Jira Service Management

A step-by-step guide with pictures, from the Speakvora agent's own Connect tab.

Short answer: This connects your own Atlassian account to your Speakvora agent. Then a customer can text where is order 1234 and get the answer in seconds, and the agent can send status and tracking texts. The agent only reads. It can never create, change or delete anything in Atlassian. Only the status word and the order number.

Every key, number and name in the pictures is a made-up example. Nothing here asks you to share a real key with anyone but the app on your own computer.

This connects your own Atlassian account to your Speakvora agent. Then a customer can text *where is order 1234* and get the answer in seconds, and the agent can send status and tracking texts. The agent only reads. It can never create, change or delete anything in Atlassian. Only the status word and the order number are ever texted back, never names, prices, items or addresses.

TIP: You need about 15 minutes, a computer, and the sign-in for your Atlassian account (the owner or a manager). You can't break anything: if a step does not work, nothing has changed and you can just try again. The keys and screens below are made-up examples.

NOTE: This guide was written from Atlassian's public developer documentation (the addresses and sign-in style were read there) and has not been tried yet on a live Atlassian account. If a screen looks different from what is described, press Connect, then Download report, and send it to support. We fix it for everyone.

Who this is for: it saas support. How Atlassian gives access: You create the key yourself in your own account; no approval is needed. What it costs you: API access is not separately charged in the docs read; it needs a Jira Service Management site.

Part 1. Get your key from Atlassian

Do this on your computer, in a new browser tab, signed in to Atlassian.

  1. Sign in to your Atlassian account as an admin or the person who will own the connection (a dedicated service account is best).
  2. Make sure that account is an agent on your service project so it can see requests.
  3. Open [[id.atlassian.com, go to Security > API tokens]].
  4. Press Create API token, name it Speakvora, set an expiry, and copy the token.
  5. In Speakvora, enter your site name (the part before .atlassian.net), the account email and the token.
  6. Press Test; Speakvora lists your service desks to prove the token works.
  7. Give customers a request key such as ITH-123; Speakvora reads that request and its status.

WARNING: If Atlassian asks which permissions to give, tick only the read-only ones: Account must have Browse/customer access to the service project (the request API returns only requests the account may see), API token (read calls only). Never give write or admin access.

TIP: To copy the key, click inside the box that shows it, press Command + C on a Mac or Ctrl + C on Windows (or right-click and choose Copy). Nothing will look different. It is now in your clipboard, ready to paste. Keep it private: anyone who has it can read your orders.

Part 2. Open the Connect tab in your agent

  1. Open your agent's dashboard (the page you open from the Start Speakvora Agent file).
  2. Press Connect in the menu. On a phone the menu is the bar along the top; slide it sideways if you do not see Connect.
  3. Step 1: press Connect (1)

  4. Under Your apps type Atlassian in the box that says Find an app (1), or scroll down the list.
  5. Step 2: the Find an app box (1)

  6. Press Jira Service Management. A card slides up. (If you only see apps for your own kind of business, that is on purpose: your agent only shows the systems that make sense for it.)
  7. Step 3: an app's card. The Full Guide button (1) opens this page.

Part 3. Paste it in

3 boxes to fill in. Click inside a box, press Command + V on a Mac or Ctrl + V on Windows, then move to the next:

  1. Your Atlassian site name. The first part of your Jira address, for example your-company in your-company.atlassian.net.
  2. Atlassian account email. The email of the Atlassian account that owns the API token. Use an account that can view the service project.
  3. API token (secret: it stays on this computer and is never shown again, only the last few characters). Created at id.atlassian.com under Security, API tokens.
  4. Part 3: each numbered box is one thing to paste. These are made-up examples.

TIP: Pasted by mistake into the wrong box? Click the box, press Command + A (Ctrl + A on Windows) to select all, then paste again.

Part 4. Test it

  1. Press the orange Save and test button.
  2. Atlassian is asked for one harmless record, just to prove the key works. Nothing is changed in Atlassian.
  3. Part 4: the green message under the buttons means it worked (1)

YOU SHOULD SEE: green words starting with Connected.

WARNING: Red words mean it did not work yet. Read them, then see If something is wrong below. Nothing bad happened.

What happens next

  • A customer texts something like where is order 1234. The agent answers *Your order 1234 is preparing.* (the status word from Atlassian), or *I could not find that order. A team member will check and reply.*
  • Each person can ask five times an hour. If Atlassian is down, the conversation carries on and the problem is written to Activity.
  • Mode: the agent asks Atlassian when a customer asks.

If something is wrong

  • It says the key was refused (401 or 403): copy the key again from Atlassian. Make sure there is no space before or after it, and that it is a live key for the right shop or location.
  • It cannot find an order (404): the number is not in Atlassian, or Atlassian uses a longer number than the one on the receipt.
  • It says too many requests (429): wait a minute and press Save and test again.
  • Atlassian says you need a plan or approval: Atlassian recommends basic auth with an API token only for personal scripts and bots; OAuth 2.0 (3LO) is the route for integrations. The customer can use a token from a dedicated low-permission service account. Speakvora only sends GET requests.
  • Still stuck? Press Connect, then Download report, and email it to support. It never contains keys or customer messages.

Atlassian's own instructions: https://developer.atlassian.com/cloud/jira/service-desk/rest/intro/

All help guides · Every agent feature · AI receptionist by industry

Questions

What if this happens: It says the key was refused (401 or 403)?

copy the key again from Atlassian. Make sure there is no space before or after it, and that it is a live key for the right shop or location.

What if this happens: It cannot find an order (404)?

the number is not in Atlassian, or Atlassian uses a longer number than the one on the receipt.

What if this happens: It says too many requests (429)?

wait a minute and press Save and test again.

What if this happens: Atlassian says you need a plan or approval?

Atlassian recommends basic auth with an API token only for personal scripts and bots; OAuth 2.0 (3LO) is the route for integrations. The customer can use a token from a dedicated low-permission service account. Speakvora only sends GET requests.

What if this happens: Still stuck??

Press Connect, then Download report, and email it to support. It never contains keys or customer messages.