> ## Documentation Index > Fetch the complete documentation index at: https://docs.woes.dev/llms.txt > Use this file to discover all available pages before exploring further. # Notion Integration > Connect Notion and import selected product notes, FAQs, setup guides, and support playbooks into the Woes Context Library. # Notion Integration Notion logo Notion is a live context integration for teams that keep product knowledge, implementation notes, FAQs, support scripts, release notes, or troubleshooting playbooks in Notion. When you connect Notion, Woes can import selected pages into the Context Library. Agents and operators can then use that material as grounded evidence alongside API specs, docs sites, GitHub repositories, and pasted source content. ## At A Glance | Use Notion for | Where it appears | | -------------------------------------------------------------------------- | ------------------------------------------------------------------------------ | | Product notes, FAQs, setup guides, migration notes, and support playbooks. | Integrations, Context Library, agent source selection, and retrieved evidence. | ## What It Does The Notion integration helps Woes answer support questions with practical knowledge that often lives outside formal API reference docs: * Product behavior notes. * Customer onboarding guides. * Internal FAQs. * Troubleshooting playbooks. * Release and migration notes. * Setup guides that explain how customers should configure your product. Imported Notion pages become searchable context for the workspace. You can attach those sources to specific agents so each agent only answers from the material that belongs to its product, website, or customer segment. ## What Gets Imported Woes imports the readable content from each shared Notion page you select. Good Notion pages include: * Clear titles. * Short sections with descriptive headings. * Exact product names, feature names, and configuration terms. * Troubleshooting steps and known failure cases. * Links to related docs, API references, or customer-facing pages. * Notes about when an operator should take over instead of letting AI answer. If you need multiple pages, select each page you want Woes to use. If a child page contains important content, share and import that page too. ## Setup In Woes, go to **Workspace Settings -> Integrations**. Find **Notion** and click **Connect**. You will be sent to Notion to approve the connection. Select the Notion workspace that contains the pages you want Woes to use. In Notion, make sure the relevant pages are shared with the Woes integration. Pages that are not shared will not appear in Woes. Return to Woes, open the Notion integration, and select each shared page you want to add. Woes imports a page into Context as soon as you select it. Open **Agents**, choose the right agent, and attach the imported Notion source so the agent can retrieve it when answering. ## Where It Appears In Woes | Surface | What you do there | | ---------------------------------- | ------------------------------------------------------------------------------- | | Workspace Settings -> Integrations | Connect, reconnect, disconnect, and select shared Notion pages to import. | | Context Library | Review imported Notion sources, inspect coverage, and rescan or delete sources. | | Agents | Attach Notion sources to the agents that should use them. | | Inbox | Operators can review retrieved evidence when an agent uses imported context. | ## Permissions And Access Notion only shows Woes the pages available to the authorized Notion connection. If a page does not appear during import, check Notion and confirm the page or its parent is shared with the Woes integration. Disconnecting Notion stops new page listing and imports. Already imported Woes context sources remain in the Context Library until an admin deletes them. Only import pages that are safe for your support workspace to use as context. Do not import pages containing passwords, private customer secrets, access tokens, or content that agents should never retrieve. ## Maintaining Notion Context When Notion content changes, update the matching source in Woes so agents use the latest guidance. * Re-select or rescan pages after important product, pricing, or setup changes. * Keep troubleshooting pages specific and step-by-step. * Remove outdated pages from Context when they should no longer influence answers. * Attach Notion sources only to agents that should answer from that material. ## Troubleshooting | Issue | What to check | | ----------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- | | The Notion page does not appear in Woes | Share the page with the Woes integration in Notion, then refresh the page list in Woes. | | Imported context is too vague | Add clearer headings, examples, troubleshooting steps, and links in Notion, then update the source in Woes. | | The wrong agent is using the page | Open the agent and remove the Notion source from agents that should not use it. | | A disconnected workspace still has old Notion sources | Delete the imported source from Context if you no longer want Woes to retrieve it. | ## Best Practices * Keep one page focused on one workflow, feature, or support scenario. * Use customer-safe language when the page may be cited or summarized. * Put internal escalation notes in clearly labeled sections. * Include links to the canonical API docs when Notion explains an API behavior. * Review agent answers after importing new pages to confirm the retrieved evidence is useful. ## Related Docs * [Sources](/context/sources) * [Knowledge Base Overview](/knowledge-base/overview) * [Agents](/agents/overview) * [Context Learning](/agents/context-learning)