> ## Documentation Index > Fetch the complete documentation index at: https://wiredesk.ai/docs/llms.txt > Use this file to discover all available pages before exploring further. # Sync from your help centre, Notion or Confluence > Keep the agent's knowledge in step with Zendesk Guide, Intercom Articles, Notion or Confluence: what each one syncs, how often, and what to do when an article fails. If your answers already live in a help centre or a wiki, connect it instead of copying it. Wiredesk reads every article, and from then on checks for changes every fifteen minutes on its own. An article you edit reaches the agent within one check. An article you archive, delete or unshare stops being quoted. Each sync only re-reads the articles whose edit time moved since the last one, so a large help centre costs no more to keep current than a small one. | Source | Connects with | What it syncs | | - | - | - | | **Zendesk Guide** | This agent's Zendesk connection, from [Actions › Connections](https://wiredesk.ai/docs/integrations/helpdesks.md) | Published help centre articles. Drafts are left out, and so are restricted articles unless you ask for them. | | **Intercom Articles** | This agent's Intercom connection, from [Actions › Connections](https://wiredesk.ai/docs/integrations/helpdesks.md) | Published articles. | | **Notion** | An internal integration secret you paste | The pages and databases shared with the integration that you pick, and the pages inside them. | | **Confluence** | Your Confluence Cloud address, Atlassian email and an API token | Every current page in the spaces you pick. | Google Drive is not available yet. ## Connect a source **1. Open Knowledge** Go to **Agents → your agent → Knowledge** and find **Sync from**. **2. Pick the source** Click **Zendesk Guide**, **Intercom Articles**, **Notion** or **Confluence**. **3. Connect it** For Zendesk Guide and Intercom Articles there is nothing to type: the sync uses the connection the agent already has. If it has none, connect it under **Actions › Connections** first. For Notion and Confluence, paste the credentials and click **Find pages** or **Find spaces**. Wiredesk checks them and shows what they can see. Tick what the agent should learn from. **4. Wait for the first sync** The source appears in the list and the first sync starts straight away. A large help centre can take a few minutes. To add or remove a source you need the Owner or Admin role. ### Zendesk Guide The sync reads through the same OAuth connection the agent opens tickets with, so nothing new has to be approved. Its access already covers help centre articles. **Include restricted articles** also syncs articles a user segment limits to signed-in users or to agents. Leave it off unless the agent only talks to people allowed to read them: it can quote anything it has read to anyone. ### Intercom Articles The access token behind this agent's Intercom connection needs the **Read and list articles** permission. In Intercom, go to **Settings → Integrations → Developer Hub → your app → Configure → Authentication**, turn it on, and connect the integration again if the token changed. ### Notion **1. Create a connection** In Notion, go to **Developer tools → Connections → New connection**. Pick **API token** as the method, then on its **Configuration** tab leave only **Read content** ticked. Older workspaces call this an internal integration, under **Settings → Connections → Develop or manage integrations**. **2. Give it the pages** On the connection's **Content access** tab, click **Edit access** and add each page or database the agent should read. Pages inside an added page come with it. You can also add it from a page's **••• → Connections**. **3. Paste the token** Copy the connection's **API token** into Wiredesk and click **Find pages**. Each row of a database is synced as its own page, with its properties ("Status: Published") above its text. ### Confluence Create an API token at [id.atlassian.com](https://id.atlassian.com/manage-profile/security/api-tokens), signed in as someone who can read the spaces you want. In Wiredesk, enter your Confluence address (for example `acme.atlassian.net`), that person's email and the token, click **Find spaces**, and tick at least one. Only Confluence Cloud addresses ending in `.atlassian.net` are accepted. ## What the list shows A connected source's row shows how many articles it holds, how many passages they make, and when it last synced, for example "42 articles · 210 passages · synced Oct 8, 10:15 AM". Click the row to see every article, with a link to it. Click **Sync now** to check for changes straight away instead of waiting for the next fifteen-minute check. ## When something fails | What you see | What it means | What to do | | - | - | - | | "2 articles couldn't be read" on the row, and the reason on each article | Those articles could not be fetched or indexed. Each keeps answering from its last good copy, and the next sync tries it again. | Usually nothing. If it persists, check the article opens for the account you connected. | | A reason in amber under a ready source | The last sync could not list the articles at all, so nothing was changed. Everything keeps answering as it did. A source that keeps failing is tried less often, up to once a day, and the row says when the next try is. | Fix what it names (often a revoked key), then click **Sync now**. | | A reason in red | The first sync failed. Nothing is indexed yet. It is retried the same way. | Fix what it names, then click **Sync now**. | | "Zendesk isn't connected to this agent any more" | The agent's Zendesk or Intercom connection was removed. | Connect it again under **Actions › Connections**. | | "Only the first 2000 articles are synced" | The source holds at most 2,000 articles. | Pick fewer pages or spaces, or split them across sources. | | "120 articles left to read" | One sync reads up to 500 changed articles. The rest are read by the next one, within fifteen minutes. | Nothing. A big first sync takes a few rounds. | | "has more than one sync can list" | The provider listed more than one sync can page through, so some articles may be missing. Nothing is removed while that is so. | Pick fewer pages or spaces, or split them across sources. | ## Removing a source Click the bin icon on its row. Every article's passages come out of the knowledge base straight away, and for Notion and Confluence the stored token is deleted with it. Disconnecting Zendesk or Intercom under **Actions › Connections** stops its sync at the next check, but keeps what was already synced until you remove the source. ## Related * [Knowledge overview](https://wiredesk.ai/docs/knowledge/overview.md) * [Keep it current](https://wiredesk.ai/docs/knowledge/keep-it-current.md) * [Helpdesk integrations](https://wiredesk.ai/docs/integrations/helpdesks.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.