Notion Integration

Connect Qualflare to Notion to create a page in a Notion database whenever a defect, failed launch, failure cluster or flaky test appears.

Notion Integration

The Notion integration creates a page in a Notion database when something noteworthy happens in your testing. QA findings land where your team already plans work, instead of in a tool someone has to remember to check.

You choose the database and the events, per project.

Setup

Step 1: Connect Notion

In Notion, create or choose the database you want Qualflare to write into. A board or table view works well.
In Qualflare, go to Workspace Settings → Integrations
Find Notion and click Connect
You are redirected to Notion to authorize Qualflare
Notion asks which pages you want to share. Select the database from step 1
You are redirected back to Qualflare with the integration installed

Qualflare can only write to what you share on that consent screen. If you skip the database there, deliveries fail later with object_not_found — the database exists, but the connection cannot see it. You can change what is shared at any time from the database's ⋯ → Connections menu in Notion.

Step 2: Configure a project

Go to Project → Integrations
Click Configure on the Notion integration
Paste the Database ID
Tick the events that should create a page
Save

Finding the database ID

Paste the whole URL. Qualflare reads the database id out of it.

Open the database in Notion, copy its link, and paste it into the Database ID field. Both URL shapes Notion uses are understood:

https://www.notion.so/acme/QA-Defects-a8aec43384f447ed84390e8e42c2e089?v=6b4c1e...
https://app.notion.com/p/a8aec43384f447ed84390e8e42c2e089?v=6b4c1e...

A Notion URL contains two ids: the database, and the v= one, which is a view of it. They are the same length and often differ only in the middle, because Notion creates an object and its default view at the same moment.

Pasting the v= value by hand saves without complaint and then fails on every delivery — with the same object_not_found error an unshared database gives, so it is easy to chase the wrong cause. Paste the URL and let Qualflare pick.

If you would rather supply the id alone, it is the part before the ? — 32 hex characters, with or without dashes.

What creates a page

Qualflare event	The page Notion gets
Defect created	`[Defect #12] <defect name>`
Launch failed	`[Launch #48] Failed — <status>`
Cluster created	`[Cluster] <cluster name>`
Flaky test detected	`[Flaky] <test case name>`

Each event is opt-in per project, so a project can create pages for defects only.

For a defect, the page body carries severity, status, category, environment, team and root causes when they are set, followed by the description and the expected/actual results.

Different projects can write to different databases — configure each one separately.

Qualflare only creates pages. It does not edit, move, archive or delete anything in your workspace, and it never reads the contents of your pages. Once a page exists, it is yours.

The one thing it does read is the database's own structure — Notion's API requires looking up which data source a database holds before a page can be added to it.

No property setup required

You do not have to map Qualflare fields onto Notion properties, and there is nothing to reconfigure when you change the database's schema.

Every Notion database has exactly one title property, whichever name you give it, and that is what Qualflare writes the page title to. Everything else goes into the page body as ordinary text.

Disconnecting

Removing the integration in Workspace Settings → Integrations revokes Qualflare's access token with Notion, so Qualflare can no longer reach your workspace.

Notion decides how the connection is then shown on its side, so check Settings → Connections in Notion if you want to confirm it is gone.

Pages Qualflare already created stay where they are. They are yours.

Troubleshooting

"database_id must be a database id, not a URL". A Notion URL is now accepted and parsed, so this means the value is neither — a link from somewhere other than Notion, or a truncated one. See Finding the database ID.

Pages are not being created. Open Project → Integrations → Recent deliveries. Every attempt is recorded there with its outcome, and a failed one names the reason.

object_not_found in a delivery. Two causes produce this, and they look identical:

The database is not shared with the Qualflare connection. Open the database in Notion, use ⋯ → Connections, and add Qualflare.
The configured id is a view id, not the database id — the v= part of the URL. Re-paste the whole URL and let Qualflare extract the right one.

It is also what you see if the database was deleted.

"this database has several data sources". Notion databases can hold more than one data source, and Qualflare will not guess which to write to — pages would land somewhere arbitrary with nothing reporting a problem. Point the integration at a single-source database.

"Reconnect required" on the integration card. The access token was revoked in Notion, or the connection was removed there. Reconnect from Workspace Settings → Integrations.

Notion Integration