Skip to main content

​
Confluence Integration

Confluence integration enables Annie to access your knowledge base, allowing it to search pages, retrieve documentation, and correlate incidents with existing runbooks, procedures, and historical knowledge.

​
Setup Guide

The recommended way to connect is Connect with Atlassian (OAuth). One authorization covers both Confluence and Jira. You can still use an email + API token as a fallback.
  1. Go to the Anyshift integrations page
  2. Navigate to the Knowledge Base section
  3. Select Confluence
  4. Click Connect with Atlassian
  5. Sign in to Atlassian and approve access for your site
  6. You return to Anyshift with the connected site shown (for example, your company Atlassian domain)
The same connection also enables Jira. You do not need to authorize twice if you later open the Jira integration page. To disconnect, use Disconnect on the Confluence or Jira integration page. That removes the shared Atlassian OAuth connection for the project.

​
Option B: Email + API token (fallback)

Use this if your organization prefers API tokens, or if OAuth is unavailable.
  1. Go to the Anyshift integrations page
  2. Navigate to the Knowledge Base section
  3. Select Confluence
  4. Under the API token section, click Add
  5. Enter your Confluence Domain, Email, and API Token
  6. Click Save

​
Confluence Domain

Enter your Atlassian domain (e.g., yourcompany.atlassian.net). This is the same domain you use to access Confluence Cloud. For example, if you access Confluence at https://acme.atlassian.net/wiki, enter acme.atlassian.net.

​
Email

Enter the email address associated with your Atlassian account (e.g., user@company.com).

​
API Token

Anyshift supports both scoped and classic Atlassian API tokens. Prefer scoped tokens for least-privilege access. No admin configuration is required. Any Atlassian user can create a token and connect their Confluence instance. Scoped API token
  1. Go to Atlassian API Token Management
  2. Click Create API token
  3. Select Scoped token type
  4. Enter a label (e.g., “Anyshift Confluence Integration”)
  5. Grant the following permissions:
    • All read:confluence-* scopes (content, spaces, users, props, etc.)
    • search:confluence - Search Confluence content (required; this is not a read:* scope)
    • read:me - Read your profile information
    • read:account - Read account information
  6. Click Create
  7. Copy the token and paste it into Anyshift
Classic API token Classic tokens inherit all permissions of the Atlassian account.
  1. Go to Atlassian API Token Management
  2. Click Create API token
  3. Select Classic token type
  4. Enter a label (e.g., “Anyshift Confluence Integration”)
  5. Click Create
  6. Copy the token and paste it into Anyshift
For more details, see Atlassian’s API Token documentation. Keep your API token secure and do not share it publicly.

​
Required Permissions

Annie performs read-only operations on your Confluence instance. Access follows the Atlassian account you authorize (OAuth) or the account tied to your API token. Your account needs access to:
  • View spaces
  • View pages and their content
  • Search content using CQL
Annie does not create, modify, or delete any pages, comments, or other content in your Confluence instance.

​
How It Works

Once connected, Annie can leverage your Confluence instance during:
  • Incident Investigation: When analyzing an incident, Annie searches for related runbooks, troubleshooting guides, and architecture documentation to find relevant context
  • Question Answering: When you ask about specific topics, Annie retrieves documentation directly from Confluence
  • Correlation: Annie can correlate alerts and incidents with documented procedures, known issues, and operational playbooks

​
Example Use Cases

  • “Search Confluence for the deployment runbook”
  • “Find documentation about Redis failover procedures”
  • “What does the architecture page say about the payment service?”
  • “Search for post-incident reviews related to database outages”
Annie will search your Confluence instance using CQL (Confluence Query Language) and cite relevant pages in its responses.

​
CQL Query Examples

Annie can construct CQL queries automatically based on your questions:

​
Supported Features

Annie can access the following Confluence data: Pages
  • Search pages using CQL or text search
  • Get full page content (title, body, metadata)
  • Navigate page hierarchies (parent/child pages)
  • View space page trees
Page Metadata
  • View comments on pages
  • Get labels applied to pages
  • Access page version history
  • Compare page versions (diffs)
Attachments
  • List attachments on pages

​
Space Scoping

You can optionally restrict which Confluence spaces Annie can access by specifying Allowed Spaces when configuring credentials. Enter a comma-separated list of Confluence space keys (e.g., ENG,OPS,SRE). When configured:
  • Searches are automatically scoped to the specified spaces
  • Direct page access is restricted — Annie cannot fetch pages from spaces not in the list
  • Space listings only show the allowed spaces
Leave the field empty to allow access to all spaces the service account can see. This is useful when a service account has broad access but you want Annie to focus on specific documentation spaces. For stronger isolation, you can also configure space-level permissions on the Atlassian service account itself.

​
Security

  • OAuth access and refresh tokens, and API tokens, are encrypted at rest using AWS KMS
  • Anyshift only reads from your Confluence instance (no write operations)
  • All communication uses HTTPS/TLS encryption
  • Credentials are validated against Atlassian APIs when you connect

​
Troubleshooting

​
OAuth connect fails or returns an error

  1. Consent cancelled: Start again with Connect with Atlassian and approve access.
  2. Wrong Atlassian account: Sign out of Atlassian in the browser, then reconnect with the account that can see your Confluence site.
  3. Connection shows error status: Disconnect and reconnect with Atlassian so Anyshift can obtain a fresh grant.

​
”401 Unauthorized” or “Invalid credentials” error (API token)

This is usually caused by one of the following:
  1. Token missing required scopes (scoped tokens only): Ensure your scoped token has all read:confluence-* scopes, plus search:confluence (this is a separate scope, not covered by read:*), read:me, and read:account.
  2. Email/token mismatch: Verify your email matches your Atlassian account email exactly.
  3. Expired or revoked token: Generate a new API token from your Atlassian account settings.

​
”No pages found” when searching

  • Verify your account has permission to view the spaces being searched
  • Check that the CQL query syntax is valid
  • Ensure pages exist matching your search criteria

​
Connection timeout

  • For API token setup, verify your Confluence domain is correct (e.g., yourcompany.atlassian.net)
  • Check that your Atlassian instance is accessible
Ready to get started? Configure Confluence Integration