Skip to content

Confluence integration

Connect DXDT to Confluence Cloud with read-only access so the platform can search and retrieve runbooks and documentation during incidents. DXDT never creates or edits content.

Setup time ~8 minutes
Difficulty Easy

Access required: Atlassian account with read access to relevant Confluence spaces

Prerequisites

  • An Atlassian Cloud account that can log in to your Confluence site
  • Read (view) access to the Confluence spaces DXDT should search
  • Your Confluence site host, e.g. yoursite.atlassian.net

Setup

1. Choose a least-privilege Atlassian user

An Atlassian API token inherits the full permissions of the user who creates it. Use (or create) a user whose Confluence access is limited to read/view on the spaces DXDT needs, and avoid site-admin accounts.

Note

The token grants exactly what this user can see, so scoping the user scopes DXDT.

2. Create an API token

Sign in as that user and go to https://id.atlassian.com/manage-profile/security/api-tokens. Click Create API token, give it a label such as DXDT Confluence, and copy the generated token immediately — it is shown only once.

  • Open id.atlassian.com/manage-profile/security/api-tokens
  • Click Create API token
  • Label it DXDT Confluence and copy the value

3. Identify your site and email

Your email is the Atlassian login email of that user. Your site is the Confluence host, either the slug yoursite or the full URL https://yoursite.atlassian.net.

Note

A trailing /wiki is fine — DXDT strips it automatically.

4. Enter the values in DXDT

In the DXDT plugin Configuration tab, paste the Site, Email, and API Token into their fields and save. DXDT validates the credentials with a read-only ping.

Configuration fields

Field Where to find it
Site (site) Your Confluence host — slug yoursite or full URL https://yoursite.atlassian.net.
Email (email) The Atlassian login email of the least-privilege user who created the token.
API Token (api_token) The token from Create API token at id.atlassian.com/manage-profile/security/api-tokens.

Verify the connection

Save on the Configuration tab, then watch the Live Status panel turn healthy — DXDT runs a read-only ping and can then list spaces.

Security

Credentials are stored encrypted per-tenant and used only for read-only Confluence calls.

Troubleshooting

401 Unauthorized on save

Wrong email/api_token pair, or the token was mistyped or expired. Regenerate the token and re-enter it with the exact login email of the token owner.

Search returns no pages

The token owner cannot view the spaces being searched. Grant that user read/view access to the relevant spaces, or point DXDT at a user who already has it.

Cannot reach site / 404

Incorrect site value. Use the *.atlassian.net host (slug or full URL); remove any extra path beyond /wiki.


Vendor documentation: https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/