> ## Documentation Index > Fetch the complete documentation index at: https://www.minitap.ai/docs/llms.txt > Use this file to discover all available pages before exploring further. # Notion > Let Mini read your specs and PRDs in Notion, and file findings to a Notion database as pages that show their status in Minitap. Connect Notion and Mini reads the specs and PRDs your team already wrote, so it knows how the app is meant to work when it writes and runs tests. The same connection lets you send any finding to a Notion database as a new page, or link it to a page you already have, with the page's status shown on the finding. | With Notion connected | Where you see it | | - | - | | Mini reads the pages and databases you shared | **Test suite → Knowledge**, under **Mini learns from** | | Mini uses them in conversations and drafts | **In Mini's context**, in a draft or the onboarding conversation | | Findings go to a database as pages | The **Ticket** menu on issues, UI/UX suggestions and failed criteria | ## Connect Notion **1. Open Integrations** Go to **Settings → Integrations** (also reachable from an app's **App settings → Integrations**). A workspace owner or admin can connect Notion. **2. Pick what to share** Click **Connect** on the **Notion** row. Notion asks which pages to share with Minitap: pick the specs, PRDs and product docs Mini should read, and the database your team files bugs in. Mini only reads what you share. You can also connect Notion while setting up the workspace, or from a finding's **Ticket** menu (**Connect Notion**) before any tracker is connected. To share more later, add the Minitap connection to more pages from Notion. ## Mini reads your specs Once pages are shared, Mini reads them and keeps what it learns for every chat, scenario and run. It reads new and edited pages on its own. When you ask Mini in a draft to cover a feature, it works from the spec your team wrote. To see what Mini took in, open **Test suite → Knowledge**. Under **Mini learns from**, the **Notion** source shows **Pages and databases you shared**, how many pages Mini read and when it last read one. Open it to see the pages. Knowledge Mini wrote from a Notion page cites it as its source. See [Knowledge](https://www.minitap.ai/docs/minitest/setup/knowledge.md). In a draft or the onboarding conversation, the **In Mini's context** panel lists the Notion pages and databases Mini can read, by title. If it says nothing is shared with Minitap right now, the connection works but no page was shared yet. ## File a finding to a database You can send an [issue](https://www.minitap.ai/docs/minitest/triage/issues.md), a [UI/UX suggestion](https://www.minitap.ai/docs/minitest/triage/suggestions.md) or a failed criterion in a [run report](https://www.minitap.ai/docs/minitest/runs/run-report.md) to Notion. **1. Open the Ticket menu** Click **Ticket** on the finding. With several trackers connected, pick **Notion** at the top of the menu. **2. Create a new page** Click **Create a new Notion ticket**, then pick the **Database**: type a few letters to search the databases shared with Minitap. **3. Set the properties and create** Minitap shows the database's select, multi-select and status properties. A status starts on the database's first to-do option. Click **Create ticket in Notion**. The new page takes the finding's title in its title property. Its content holds the report: a **View in Minitap** link and, for an issue or failed criterion, a **Watch the recording** link, what happened, Mini's root cause analysis with the steps to reproduce, and a context table with the scenario, criterion, platform, build and severity. A UI/UX suggestion's page holds what Mini found, the screen, its severity and the scenarios it was seen in. ## Link a page you already have Open the **Ticket** menu and search instead of creating. Notion pages have no short key, so search by title or paste the page's link. Typed words match rows of your shared databases; with an empty search, the menu shows the recently updated ones. Pick a page and the finding is linked to it. A finding holds one ticket at a time. To change it, open the issue in the **Issues** tab and click **Unlink ticket**: the link goes, and the page stays in Notion. ## Page status on the finding A linked finding shows the page's title and, when the database has a status property, its current status, and opens the page in Notion on click. Minitap reads the status from Notion each time it shows it. If the page is deleted or archived, Minitap drops the link. ## From the CLI ```bash theme={"theme":{"light":"github-light","dark":"vesper"}} # The databases shared with Minitap, with their IDs minitest --app issues ticket targets notion # File an issue as a page in a database minitest --app issues ticket create --provider notion --target # Find a page by its title or link, then link it by its ID minitest --app issues ticket search notion "Checkout spinner never stops" minitest --app issues ticket link --provider notion --ticket ``` See the [CLI reference](https://www.minitap.ai/docs/minitest/reference/cli-commands.md) for the other `issues ticket` commands. ## Next steps > [card] [Knowledge](https://www.minitap.ai/docs/minitest/setup/knowledge.md) > > Everything Mini knows about your app, and where it learned it. > [card] [Triage issues](https://www.minitap.ai/docs/minitest/triage/issues.md) > > Decide which failures deserve a ticket. > [card] [Linear](https://www.minitap.ai/docs/minitest/integrations/linear.md) > > File the same findings as Linear issues. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.