Skip to main content
Connecting Confluence allows Traversal to surface runbooks, procedures, and postmortems during investigations and cite relevant internal documentation as evidence.

​
What Traversal reads

  • Pages — page content searched via CQL and fetched by ID
  • Spaces — space metadata used to scope searches

​
Atlassian Cloud setup

1

Create an Atlassian API token

  1. Open Atlassian API tokens and sign in
  2. Create a standard Atlassian API token, give it a descriptive name, and choose an expiration date
  3. Copy the generated token right away. Atlassian only shows it once
2

Configure in Traversal

Go to Company Knowledge > Integrations, select Confluence, and enter:
  • Confluence site URL (usually https://company.atlassian.net/wiki)
  • Your Atlassian account email
  • API token

​
Required scopes for scoped tokens

If your organization uses scoped Atlassian API tokens, grant the following minimum Confluence scopes for optimal agent performance:
Only search:confluence is needed for the connection health check on the Traversal UI to pass.

​
Confluence Data Center setup

Choose either authentication method:
  1. Choose a Confluence account that can read the pages and spaces you want Traversal to access.
  2. Go to Company Knowledge > Integrations and select Confluence.
  3. Choose Username & Password and enter the full Confluence URL, username, and password.
  1. Confirm that your Confluence Data Center installation is version 7.9 or later. For older installations, use Username & Password.
  2. In Confluence, select your avatar, then go to Settings > Personal access tokens.
  3. Create a token, optionally set an expiration date, and copy it right away.
  4. Go to Company Knowledge > Integrations and select Confluence.
  5. Choose Bearer Token and enter the full Confluence URL and Personal Access Token.
Include the complete context path in the URL, such as /confluence, when applicable.

​
Private network access

If the service endpoint is not directly reachable by Traversal (as is common with self-hosted services), deploy a Traversal Connector in a network that can reach it. When configuring the integration, select that connector under Network Access Needed. The service endpoint does not need public internet exposure. See Set up the Traversal Connector for deployment and network requirements.

​
More information