Thunders and ClickUp talk to each other in both directions.
Way 1 — Thunders → ClickUp: when a test fails, you don't need to jump into ClickUp, open a new task, and manually copy over what went wrong. Thunders AI can create that task for you, right from the failed run, with the context already attached.
Way 2 — ClickUp → Thunders: already have your requirements written up as ClickUp tasks? 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 ClickUp, you'll need:
A ClickUp account, with access to the workspace and list you want bugs reported into. This is where your tasks will land, so make sure it's one you actually have permission to create tasks in.
Connect ClickUp
Both ways below share the same one-time setup: connecting your ClickUp 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 ClickUp, 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:
Option A — From Thunders AI
Go to the Thunders AI tab.
Click the 🧠 brain icon — this opens the connectors list.
Click + Add connector.
Select ClickUp from the list of available integrations.
Authenticate with your ClickUp account when prompted.
Option B — From the Connectors tab
Go to the Connectors tab.
Look for ClickUp in the list of integrations.
Click Connect.
Authenticate with your ClickUp account when prompted.
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 → ClickUp — Report a bug
Once ClickUp 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 ClickUp 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 list it should go into, the priority, 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 task — say, which ClickUp list to use — it will ask you directly in chat. Just answer, and it continues.
Once everything is in place, the task is created successfully in ClickUp, and Thunders AI will let you know it's done.
Way 2: ClickUp → Thunders — Build test plans and test cases from a task
Already have your requirements captured in ClickUp? You can use that task as a knowledge base and have Thunders AI generate test plans and test cases from it — no retyping required.
Make sure ClickUp is enabled as a connector in your Thunders AI chat (see Connect ClickUp above).
In the chat, reference the ClickUp task you want to use — a title, a task 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 this ClickUp task: " or "turn this task into a test plan: ".
Thunders AI reads the task 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, Notion, Shortcut, 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 list for ClickUp, and so on): the connection steps and the reporting flow itself stay the same.
Way 2 works with any ClickUp task you have access to — just give Thunders AI the title, ID, or link, and it pulls the rest itself.