> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wolfia.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Slab Integration: Sync Your Wiki Posts into Wolfia
> Connect Slab to Wolfia with a bot token, index every post in your workspace, and keep answers grounded in documentation your team already maintains.
Teams that keep their internal handbook, policies, and engineering runbooks in Slab answer the same questions in security reviews and RFPs. Wolfia reads those posts straight from the workspace, cites them in answers, and follows along as teammates edit, publish, and remove pages.
## What Wolfia reads
Wolfia indexes the posts the bot token can see. There is no picker; the whole workspace syncs.
Each post is indexed under its Slab title with its full text, so citations point at the page by name.
A post that changes in Slab is refreshed on the next sync. Posts with no changes are left as they are.
A post that no longer exists in Slab is removed from the knowledge base on the next sync.
Access is read only. Wolfia never edits, publishes, or archives anything in Slab. Posts with an empty body cannot be indexed and show a **Failed** status.
## Before you start
* An admin, expert, or integration admin role in Wolfia. Only these roles can connect integrations.
* A Slab bot token for your workspace. Wolfia points you to `https://{portal}.slab.com/admin/developer`, where `{portal}` is your workspace subdomain. Opening that page generally requires Slab admin access; check with your Slab admin if you cannot see it.
A Slab connection is shared across your organization. One bot token serves the whole workspace, and anyone who can manage integrations can update it from the Knowledge Hub.
## Connect Slab
Open `https://{portal}.slab.com/admin/developer` for your workspace and create a bot token. Copy it; you will paste it into Wolfia in the next step.
In Wolfia, go to **Knowledge Hub** and find **Slab** in the list of integrations. It is listed under Knowledge with an **Organization** badge.
Click **Connect**. In the **Connect Slab** dialog, paste the token into **Bot token** and click **Connect**. Wolfia stores the token securely and confirms with **Slab integration connected successfully**. The first sync starts on its own.
Open the **Slab** page in the Knowledge Hub. Posts appear in the table as Wolfia indexes them, and the connection shows under **Connected integrations**.
Indexing time depends on the size of your workspace. Wolfia paces its requests to stay within Slab's API limits, so a large wiki can take a while on the first pass. You can keep using Wolfia while it runs.
## Keep Slab in sync
* **Automatic sync**: Wolfia re-reads your workspace every day, picking up new posts, edits, and removals.
* **Sync now**: click **Sync now** on the Slab page to refresh immediately, for example after publishing a policy update.
* **Check status**: click **Manage** to open **Manage Slab integration**. It shows the sync status (**Completed**, **In Progress**, **Failed**, or **Draft**) and the **Last synced** time, and has its own **Sync now** button.
* **Rotate the token**: in the same dialog, paste a new token under **New bot token** and click **Save bot token**. Do this whenever the token is regenerated in Slab.
* **Exclude a post**: in the Slab table, use **Exclude from knowledge base** on any post you do not want answers to draw on. Excluded posts stay excluded across future syncs until you choose **Include in knowledge base**.
* **Disconnect**: click **Disconnect** and confirm. This removes every post Wolfia synced from Slab from the knowledge base and cannot be undone.
## Good practices
* Create the bot token from a workspace admin account rather than a personal one, so the connection survives team changes.
* Keep drafts and superseded pages out of Slab, or exclude them in Wolfia, so answers cite the current version.
* After rotating the token in Slab, update it in Wolfia right away. A stale token makes the next sync fail.
## Frequently asked questions
Not at connection time. Wolfia syncs every post the bot token can see. To keep specific posts out of answers, exclude them from the Slab table in the Knowledge Hub.
The most common cause is a bot token that was revoked or regenerated in Slab. Click **Manage**, paste the current token under **New bot token**, click **Save bot token**, then **Sync now**.
Confirm the post has body text; empty posts show a **Failed** status. Then click **Sync now**. If the post is still missing, check whether the bot token can open it in Slab.
No. Access is read only. Wolfia only reads post titles and content.
No. Only posts whose content changed are reprocessed. Unchanged posts keep their existing knowledge.
## Related pages
Every source Wolfia can index and how they fit together.
Upload documents directly when they do not live in Slab.
Sync wiki pages from Confluence the same way.
Index a public documentation site alongside your wiki.