> 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/guides/data-management/add-notion-article.md). # Add a Notion article Share a Notion page with the Siit connection from Notion, then sync it from the Siit integration settings so the article appears in your knowledge base and can be published Here is a quick video 📹 showing the process: {% embed url="" %} Otherwise, here are all the steps you need to do to add a Notion article following the integration ⤵️ ### Choose the Notion article you want to add Go to Notion and click on the article you want to upload. Then, click on the **“…”** at the top right of the page on Notion
### Add a connection between the Notion article & Siit A drop-down menu appears Scroll down to the bottom of the drop-down menu, and click on : **“add connections”**
Then enter “Siit” in the search bar that appears Click on “Siit” application A message appears. Click on **“Confirm”**
### Synchronize your article on Siit platform Finally, go to the Siit admin platform Click on **the “⚙️”** (top right of the page) Then click on **Integration library** and select **Notion**. Click on the **“…”** at the top right of the Notion block. Select “Synchronize”
### That’s it, wait a minute and your article will appear in Context -> Articles. --- # 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/guides/data-management/add-notion-article.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.