---
title: "Notion Integration"
description: "Connect TestOrchestrator to Notion as a read-only integration source — reference Notion pages from test objects and generate test cases from a Notion spec or PRD."
source: "https://testorchestrator.com/docs/integrations/notion"
---

# Notion Integration

Notion is a built-in integration source in TestOrchestrator. Once an administrator connects your Notion workspace, your team can reference a Notion page from a test case, run, or exploration, and point the AI test-case generator at a Notion spec, PRD, or requirements doc to draft cases. The connection is **read-only** — TestOrchestrator reads the pages you share with it and never writes anything back to Notion.

> Notion is a built-in [integration source](https://testorchestrator.com/docs/integrations/integration-sources). Everything about [relations](https://testorchestrator.com/docs/integrations/relations), project scope, and where links appear is shared with all other sources — this page covers what is specific to Notion.

> **Read-only by design.** TestOrchestrator only reads the Notion pages you explicitly share with the integration. It does not post comments, write back statuses, perform two-way sync, or modify any Notion content.

## Connecting Notion in Settings

Notion is configured like any other source in **Admin → Integrations → Trackers**. The shared mechanics — the SOURCE, CAPABILITIES, and PROJECTS tabs, testing the connection, and enabling or disabling the source — are covered in [Trackers](https://testorchestrator.com/docs/integrations/integration-sources). The steps below cover what is specific to Notion.

1. In Notion, the workspace owner creates an **internal integration** at _notion.so/my-integrations_ and copies the integration token it generates.
2. Still in Notion, **share** the specific pages or databases you want TestOrchestrator to read with that integration — TestOrchestrator can only see content that has been shared with it.
3. In TestOrchestrator, open **Admin → Integrations → Trackers** and click **Create a source**. Choose **Notion** as the provider.
4. For the authentication type, supply the **Notion internal integration token** you copied as the source credential.
5. **Test** the connection to confirm TestOrchestrator can reach Notion, then assign the source to **all projects** or to **specific projects** on the PROJECTS tab.

## Referencing a Notion page

Once the Notion source is enabled for a project, members with permission to manage external references can link a Notion page to a test case, run, or exploration.

1. On a test case or run, click **Link issue**.
2. Paste the Notion page’s link or its ID. Notion pages can’t be searched from TestOrchestrator; with the source’s token the page is fetched _by key_, so its title appears before you link it.
3. On a test case, choose the [link type](https://testorchestrator.com/docs/integrations/relations) under **Link as**, then pick the page.

The reference is one-directional: it records a pointer from the TestOrchestrator object to the Notion page. Nothing is written back into Notion.

## Generating test cases from a Notion page

Point the AI test-case generator at a Notion page — typically a spec, PRD, or requirements doc — to draft test cases that map to your project's template. Generation is initiated from inside TestOrchestrator; there is no Notion-side action, sidebar, or @mention. The drafted cases are created in the project you generate them into and can be reviewed and edited like any other test case.

> Test-case generation from a Notion page is an AI-assisted feature and is available on plans that include AI capabilities. Generated cases are drafts — always review them against the source page before relying on them.

## Who can do what

| Action | Who can do it |
| --- | --- |
| Create, test, or disable the Notion source; assign projects | Admins with access to the Integrations admin page |
| Reference a Notion page from a test object | Project members with permission to manage external references |
| Generate test cases from a Notion page | Project members with permission to generate test cases (AI plans only) |

## Related

- [Trackers](https://testorchestrator.com/docs/integrations/integration-sources) — How sources are configured, the authentication types available, capabilities, and project scope.
- [Link types](https://testorchestrator.com/docs/integrations/relations) — Define the semantic labels — General or Defect — applied to every external link.
