> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/integrations/knowledge-base/notion.md). # Notion Connect Notion to Siit so your existing wiki powers AI answers, agent replies, and the Portal Knowledge Base. Pages stay in Notion, your team keeps editing where they already work. ### What you get * **Live sync from Notion to Siit.** Selected pages and databases sync into Siit Articles and refresh automatically — edits made in Notion flow into Siit on the next sync. * **Source of truth stays in Notion.** Siit reads from Notion. It never modifies your pages. * **Powers every Siit AI surface.** Synced articles are used by the Triage Agent (answers and deflection at intake) and the IT Agent (autonomous answers in Slack, Teams, and the Portal), with source citations linking back to the original Notion page. * **Searchable Portal Knowledge Base.** Employees browse and search synced Notion content directly in the Siit Portal. * **Agent-friendly inserts.** Agents can insert synced articles directly into request replies as rich cards. * **Source tracking.** Every synced article in Siit shows "Source: Notion" with a link back to the original page. ### How the sync works * **Initial import** — once you authorize Notion and pick the workspace, pages, or databases you want synced, Siit pulls them in and converts each one into a Siit Article. * **Continuous sync** — synced content refreshes on a schedule. Notion edits flow into Siit automatically. * **Scope-by-page or by-database** — you control exactly what's synced. Start with one or two high-value pages or databases, then expand. * **Permissions are respected** — Siit honors Notion's access controls. Pages the connected integration can't see won't appear in Siit. * **Status preserved** — synced articles can be Draft or Published in Siit. You decide when to make them visible to employees. ### Where synced Notion content shows up * **Portal Knowledge Base** — employees search and browse synced articles in the Siit self-service portal. * **Triage Agent** — suggests the relevant Notion-sourced article to an employee at intake, before a request is created. * **IT Agent** — the AI Agent cites Notion-sourced articles when answering employees in Slack, Teams, or the Portal. * **Request replies** — agents insert synced articles directly into responses as rich cards. * **Workflow actions** — automated replies can attach Notion-sourced articles (e.g., "send the password reset guide when a reset request is submitted"). ### Before you connect * A Notion admin (or workspace owner) able to install the Siit Notion integration. * A clear idea of which pages or databases to sync first. Quality beats quantity for AI accuracy — start with your 10–20 most-used internal docs. ### Connect Notion 1. In Siit, go to **Settings → Workspace → Integration library**, find **Notion** in the Knowledge Base section, and click **Connect**. 2. Sign in to Notion as an admin and approve the requested access. 3. In Notion's authorization screen, select the specific pages and databases Siit can read. Only what you select here will be available to sync. 4. Back in Siit, pick the pages or databases you want imported as Articles. 5. Run the initial sync and review the imported Articles in **Context → Articles**. For the detailed walkthrough, see our Help Center guide: [Notion integration setup](https://help.siit.io/notion-integration). ### After the connection * **Review imported Articles** in **Context → Articles**. Each one shows "Source: Notion" with a link to the original page. * **Publish what's ready.** Synced articles default to a state where you can review and publish them deliberately. See our Help Center guide: [Add a Notion article](https://help.siit.io/add-notion-article). * **Categorize** — organize Articles by team or topic (IT, HR, Policies, Security) so the Portal browsing experience is clean. * **Enable AI** — make sure the Triage Agent and the IT Agent are configured to use your Articles. The more high-quality content you sync, the better the AI performs. * **Validate suggestions** — over the first week, watch which articles AI surfaces in real conversations. Retire or rewrite anything that's outdated or noisy. ### Sync frequency Notion content refreshes automatically on a schedule. Trigger an immediate refresh from **Settings → Workspace → Integration library → Notion → Synchronize** if you've just edited a critical page and need it reflected in Siit straight away. **Synchronize** hides itself while a sync is running and for 3 hours after the last one, so it reappears once a new run can usefully start. ### Common use cases * **AI-powered self-service.** Employees ask "How do I reset my Okta MFA?" in Slack. The IT Agent searches synced Notion pages, finds the matching guide, and answers with a source link — no ticket created. * **Faster agent replies.** An agent opens a new VPN-access request and inserts the right Notion-sourced article into the reply from the composer's article picker. * **Portal browsing for new hires.** A new hire lands on the Siit Portal and browses synced Notion onboarding guides — finding answers before their Day-1 questions pile up. * **Deflection at submission.** When an employee starts submitting a "Password reset" service, Siit suggests the relevant Notion article first; many employees resolve it themselves. * **Content lifecycle alignment.** Your IT or HR team edits a policy page in Notion. On the next sync, every Siit surface reflects the update — no manual republishing. ### Tips * **Start with a focused scope.** Sync the one or two databases where your highest-quality, most-used documentation lives. Don't sync your entire Notion workspace. * **Title pages as questions employees ask.** "How do I reset my Okta MFA?" retrieves better than "Okta MFA Reset Procedure." * **Keep one source of truth per topic.** If the same content exists in Notion and another tool, pick one. AI can't judge which version is canonical. * **Use Notion databases for structured content.** A "How-to" or "Policy" database with consistent properties syncs predictably and stays organized in Siit. * **Review what AI is surfacing.** In **Context → Articles**, the analytics view shows which articles AI suggests most often. Low-quality or outdated ones can be retired. ### Help Center guides * [Notion integration setup](https://help.siit.io/notion-integration) — step-by-step setup with screenshots * [Add a Notion article](https://help.siit.io/add-notion-article) — how to bring specific Notion pages into Siit and publish them ### Troubleshooting **Pages missing from the picker.** During the Notion authorization step, only the pages and databases you explicitly select are made available to Siit. Re-authorize and add the missing pages to the integration's access scope. **A synced article is empty or partial.** Notion blocks like embeds, synced blocks, or third-party widgets may not render in Siit. Edit the Notion page to use native blocks, then re-sync. **Edits in Notion aren't reflected in Siit.** The sync runs on a schedule. Trigger an immediate refresh from **Settings → Workspace → Integration library → Notion → Synchronize**. **AI isn't suggesting Notion articles.** Confirm the Article is set to **Published** in Siit (Drafts are excluded from AI). Also check that the Triage Agent or the IT Agent has Articles enabled as a source. **"Connection lost" or reauthorization needed.** A Notion admin revoked the integration's access, or the workspace policy changed. Reconnect from **Settings → Workspace → Integration library → Notion**. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.siit.io/integrations/knowledge-base/notion.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.