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