Thunders and Shortcut talk to each other in both directions.
Way 1: Thunders → Shortcut: when a test fails, you don't need to jump into Shortcut, open a new story, and manually copy over what went wrong. Thunders AI can create that story for you, right from the failed run, with the context already attached.
Way 2: Shortcut → Thunders: already have your requirements written up as Shortcut stories? Point Thunders AI at one, and it'll use it as a knowledge base to generate test plans and test cases for you.
Prerequisites
Before you can report bugs to Shortcut, you'll need:
A Shortcut account, with access to the workspace and project you want bugs reported into. This is where your stories will land, so make sure it's one you actually have permission to create stories in.
Connect Shortcut
Both ways below share the same one-time setup: connecting your Shortcut account to Thunders, per project.
An important thing to know: connections in Thunders are personal and per project : there are no more shared, org-wide tokens. This means every teammate who wants to use Shortcut, in either direction, needs to connect their own account.
There are two equally valid ways to connect, depending on where you happen to be in the app : but both rely on the same Shortcut API token, so grab that first.
Generate a Shortcut API token
Shortcut authenticates via an API token rather than a sign-in prompt, so before either option below, you'll need one:
Click Create Token and give it a name.
Set the scope to Full access.
Click Create.
Copy the token : you'll paste it into Thunders in the next step.
Option A : From Thunders AI
Go to the Thunders AI tab.
Click the brain icon : this opens the connectors list.
Click + Add connector.
Select Shortcut from the list of available integrations.
Authenticate with your Shortcut account when prompted.
Option B : From the Connectors tab
Go to the Connectors tab.
Look for Shortcut in the list of integrations.
Click Connect.
Paste the same Shortcut API token into Thunders when prompted (see Generate a Shortcut API token above).
Both paths lead to the same result, so use whichever is more convenient : if you're already chatting with Thunders AI, the brain icon saves you a tab switch; otherwise the Connectors tab gives you a full overview of everything you have connected.
Way 1: Thunders → Shortcut : Report a bug
Once Shortcut is connected, reporting a bug takes just a few clicks:
Go to the failed run you want to report on.
Click the bug icon next to the failed step.
Click Report bug.
Select Shortcut as the integration you want to send this bug to.
In the Guidance field, write a short, natural-language prompt describing your ticket preferences : for example, which project or workflow state it should go into, the severity, who should be assigned, or anything else relevant. You don't need to fill out a rigid form; just describe what you want in plain language.
Click Send.
Thunders AI takes it from there. If anything, important is missing to create the story : say, which Shortcut project to use : it will ask you directly in chat. Just answer, and it continues.
Once everything is in place, the story is created successfully in Shortcut, and Thunders AI will let you know it's done.
Way 2: Shortcut → Thunders : Build test plans and test cases from a story
Already have your requirements captured in Shortcut? You can use that story as a knowledge base and have Thunders AI generate test plans and test cases from it : no retyping required.
Make sure Shortcut is enabled as a connector in your Thunders AI chat (see Connect Shortcut above).
In the chat, reference the Shortcut story you want to use : a title, a story ID, or a link all work.
Ask Thunders AI to build a test plan or test cases from it, for example: "create test cases from SC-1234" or "turn this Shortcut story into a test plan: ".
Thunders AI reads the story and drafts the test plan or test cases for you to review and refine.
Good to know
This exact same flow also works for accessibility reports: no separate process to learn.
The steps above are the same for every other integration Thunders supports: Linear, Jira, ClickUp, Notion, Azure DevOps, or even a custom integration you've added yourself. What changes from one integration to another is mainly what you mention in your Guidance prompt (a team for Linear, a project for Jira, a project for Shortcut, and so on): the connection steps and the reporting flow itself stay the same.
Way 2 works with any Shortcut story you have access to. Just give Thunders AI the title, ID, or link, and it pulls the rest itself.