Skip to main content
Configure the source at AI Training → Data Sources.

Set up the sync

1

Open Data Sources

2

Add a Confluence source

Click Add source → Confluence.
FieldExampleWhere to get it
Domainyourcompany.atlassian.netYour Atlassian instance domain. No https://.
Email[email protected]The Atlassian account the API token belongs to.
API TokenATATT…Generate at Atlassian API tokens. The token needs Confluence read access.
3

Start the sync

Click Connect. The first run does a full pull of every page the credentials can read. Large instances take longer — expect 10 minutes to an hour for thousands of pages.
4

Verify in AI Instructions

Open AI Training → AI Instructions. Pages appear under Confluence, each linked to its source URL in your instance.

What gets synced

Whole-instance pull. Page titles, body content (converted from Confluence storage format to HTML), and the webui back-link.
  • Personal spaces (key starts with ~) → internal — the AI uses them only in agent-facing surfaces.
  • All other spaces → public — the AI can cite them in customer replies.
Override per-page in AI Instructions if a specific page needs different visibility.
Each sync run is a full re-pull with overwrite. The benefit: deletions in Confluence propagate correctly. The cost: each run is heavier than an incremental pull. Typical cadence is set by Airbyte’s scheduler — adjust on the connection schedule if you need it less often for a huge instance.

Limits

Value
Streams syncedpages
Sync modefull_refresh_overwrite
Sync cadenceAirbyte polling — typically every few hours
Credential typeDomain + email + Atlassian API token
DeploymentCloud only. Server / Data Center not supported.
Selective scopingNone today — whole instance pulled
AttachmentsNot synced

Confluence overview

What this source does and doesn’t.

Troubleshooting

Auth errors, missing pages, slow syncs.

Website crawler

Fallback for scoped subsets.

Connect a knowledge source

All sources.