Confluence Integration
Use Confluence integration to let Dawn discover spaces, browse pages, read documentation, and search page content inside linked Confluence spaces.
Before you start
- A Confluence Cloud site URL, usually
https://your-org.atlassian.net. - The Atlassian account email that owns the API token Dawn should use.
- A regular Atlassian API token for that same account.
- Permission for that Atlassian user to browse the spaces Dawn should discover.
This guide is for Confluence Cloud only. Dawn does not support Confluence Server or Data Center in this first release.
Create the API token
- Sign in to your Atlassian account at id.atlassian.com/manage-profile/security/api-tokens.
- Open Security and then API tokens.
- Click Create API token.
- Name it something like
Dawn Confluence. - Create the token and copy it immediately.
Dawn expects a normal Atlassian API token. Paste only the token value into Dawn. Do not combine it with the email in the input.
Connect Confluence in Dawn
- Open Integrations in Dawn and click Add connection.
- Choose Confluence.
- Enter the Confluence Cloud site URL.
- Enter the Atlassian account email that owns the token.
- Paste only the token value into the API token field.
- Click Connect.
- Review the discovered spaces and link the ones you want available in the workspace.
- Assign those linked spaces to the agents that should use them.
What Dawn discovers
Dawn discovers the Confluence spaces visible to the Atlassian account behind the token. Each linked source is a space-scoped documentation surface.
- Browse pages from the linked space root.
- Read page content from pages inside that linked space.
- Search for pages inside the linked space.
Current limitations
- Dawn treats Confluence as a read-focused documentation source in v1.
- Macro-heavy pages may be simplified when rendered for runtime use.
- Binary attachments are not treated as first-class readable files in this release.
- Permission changes in Confluence can cause linked spaces or pages to disappear until access is restored.
Troubleshooting
- 401 on validation: make sure the email and token belong to the same Atlassian account, and that you pasted only the token value.
- No spaces appear: the Confluence user behind the token probably lacks access to the spaces you expected to discover.
- Used a page URL instead of the site URL: Dawn expects the Confluence Cloud site root, not a page URL.
- Read or search fails for one page: the connection may have lost access to that page or space even if validation still succeeds.