Connecting Confluence allows Traversal to surface runbooks, procedures, and postmortems during investigations and cite relevant internal documentation as evidence.Documentation Index
Fetch the complete documentation index at: https://docs.traversal.com/llms.txt
Use this file to discover all available pages before exploring further.
What Traversal reads
- Pages — page content searched via CQL and fetched by ID
- Spaces — space metadata used to scope searches
Required scopes
When issuing a scoped Atlassian API token, grant the following minimum Confluence scopes for optimal agent performance:| Scope | Used for |
|---|---|
search:confluence | CQL search across pages — required for the agent to discover relevant runbooks and docs |
read:page:confluence | Fetching full page content by ID after a search hit |
read:space:confluence | Resolving space metadata used to scope searches and label results |
read:attachment:confluence | Reading attachments referenced from pages |
Only
search:confluence is needed for the connection health check on the Traversal UI to pass.Setup
- Atlassian Cloud
- Self-hosted (Server or Data Center)
Create an Atlassian API token
- Open Atlassian API tokens and sign in
- Create a standard Atlassian API token, give it a descriptive name, and choose an expiration date
- Copy the generated token right away. Atlassian only shows it once
Traversal exposes two Confluence authentication modes:
- Basic Authentication for Atlassian Cloud
- Bearer Token for self-hosted Confluence Server or Data Center