Skip to content
The docs are now organized by product area. Old links still work. Report a broken link

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.

Last updated

The Qualflare Notion integration creates a page in the Notion database you choose when a defect is created, a launch fails, a failure cluster is found or a test turns flaky; a workspace Editor installs it once, and each project picks a database.

QA findings land where your team already plans work. Qualflare only creates pages: it never edits, moves, archives or deletes anything in your Notion workspace.

What the integration does

The Notion card is under Testing on the workspace Integrations page. Each project picks which of these events create a page: Defect Created, Launch Failed, Cluster Created and Flaky Test Detected. Different projects can write to different databases.

Before you begin

  • You install Notion on the workspace Integrations page Editor+ · workspace (requires the Editor role or higher in the workspace).
  • You set up each project on its own Integrations page Editor+ · project (requires the Editor role or higher in the project).
  • In Notion, create or choose the database Qualflare should write into. A board or table view works well.

Install Notion

  1. In the workspace sidebar, open Integrations, then the Testing tab
  2. On the Notion card, click Install
  3. On Notion, approve the Qualflare connection, and when Notion asks which pages to share, select the database you chose
  4. You are sent back to Integrations, with the Notion card installed

The Qualflare Notion integration can only write to what you share on Notion's consent screen. If you skip the database there, every delivery fails with object_not_found. You can share it later from the database's ⋯ > Connections menu in Notion.

Configure a project

  1. In the project sidebar, open Integrations and click Configure on Notion (Edit once it is set up)
  2. In Database ID, paste the database's link from Notion, or its id
  3. Optionally fill in Database Name: "Display name shown in the UI — does not affect where pages are created."
  4. Under Events, select which events create a Notion page
  5. Click Save

Find the database ID

To give Qualflare a Notion database ID, paste the whole link: open the database in Notion, copy its link and paste it into Database ID. Qualflare reads the database id out of both link shapes Notion uses:

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

The id is the 32 hex characters before the ?, with or without dashes.

A Notion link holds two ids: the database's, and the v= one, which belongs to a view of it. Pasting the v= value saves without an error, then every delivery fails with the same object_not_found an unshared database gives. Paste the whole link and Qualflare picks the right id.

Check deliveries

Each page Qualflare tries to create is a row in the project's Recent deliveries, with Notion's error in Detail when it fails. For Defect Created, the new page also shows on the defect as a Notion page chip under Linked issues.

What the page contains

A Notion page's title depends on the event:

EventPage title
Defect Created[Defect #12] <defect name>
Launch Failed[Launch #48] Failed — <status>
Cluster Created[Cluster] <cluster name>
Flaky Test Detected[Flaky] <test case name>

For a launch, the body lists its status, branch and failed count; for a cluster, its pattern and affected cases; for a flaky test, its suite and flaky rate. For a defect, the body lists the severity, environment, category, status, team and root causes that are set, then the description and the expected and actual results. Every page ends with Created automatically by Qualflare.

No property setup required

The Qualflare Notion integration needs no mapping of fields onto Notion properties, and nothing to change when you edit the database's schema. Every Notion database has exactly one title property, whatever you name it, and Qualflare writes the page title there. Everything else goes into the page body as text.

To add a page, Qualflare reads the database's structure, because Notion's API needs to know which data source the database holds. It never reads the contents of your pages.

Reconnect and remove

Qualflare refreshes its Notion access token on its own. If Notion refuses the refresh, the card shows Reconnect. The card has no Install button while Notion is installed, so remove Notion and install it again. The card says "Reconnect required — remove it and install it again." Removing Notion deletes the project settings, so note each project's database and events first.

Removing Notion deletes every project's Notion settings and their delivery history. To use Notion again, install it and set up each project from scratch.

On the Notion card in the workspace Integrations page, click the trash icon, then Remove. Qualflare also asks Notion to revoke its access token. To confirm the connection is gone, check Settings > Connections in Notion. Pages Qualflare already created stay where they are.

Data sent to Notion

Qualflare sends the page title and body above: a defect's number, name, severity, environment, category, status, team, root causes, description and expected and actual results; a launch's number, status, branch and failed and total counts; a cluster's name, pattern and case count; or a test case's name, suite and flaky rate.

Troubleshooting

  • No page appears. Open Recent deliveries: Detail has the reason.
  • object_not_found in a delivery. The database isn't shared with the Qualflare connection (share it from ⋯ > Connections in Notion), the Database ID is a view id (paste the whole link again, see Find the database ID), or the database was deleted.
  • "database_id must be a database id, not a URL". The value is neither a Notion link nor an id, for example a link from another site or a cut-off one. See Find the database ID.
  • "notion database has <n> data sources; Qualflare cannot tell which to write to". The database holds more than one data source, and Qualflare won't guess which to write to. Point the project at a database with a single data source.
  • unauthorized in a delivery, or the card shows Reconnect. The connection was removed or its access revoked in Notion. See Reconnect and remove.