Common scenarios
| Symptom | Likely cause | Fix |
|---|---|---|
| Sync fails with unauthorized | Access token is invalid, expired, or lacks read access to the specified space | Regenerate the token with the right scope and update the source. |
| Space ID not found | The Space ID field is wrong or you entered a collection ID instead | Open the space in GitBook, pull the ID from the URL (after /space/) or from the GitBook API. Update the source. |
| Sync succeeds but the content folder is empty | The token can authenticate but doesn’t have read access to the content stream of that space | Verify the token’s access in GitBook. Some tokens are scoped to specific content — use one with full space read. |
| I want a second space synced | One space per connection | Add a second GitBook source in OpenCX with a different space ID (and optionally a different token). |
| None of the above | — | Contact support with the connection ID. |
Related Documentation
Connect GitBook
Re-check credentials and space ID.
GitBook overview
What this source does.
Website crawler
Fallback for public GitBook sites.
Connect a knowledge source
All sources.