Skip to main content
The Confluence integration enables AirMDR to:
  • Retrieve pages, blog posts, comments, tasks, and attachment metadata.
  • Search content and identify related pages, spaces, labels, and users.
  • Review space permissions and role assignments during access investigations.
  • Retrieve page history and hierarchy to understand content changes and relationships.

Authentication methodAirMDR authenticates using HTTP Basic authentication with:
  • Email: The email address of the Atlassian account that owns the token.
  • API Token: A token created for that account.
Select the connection configuration that matches your token:Scoped tokens must use Atlassian’s API gateway. These credential requirements also match the supplied AirMDR connection screenshots.

Pre-requisites

An active Atlassian account with access to the required Confluence Cloud site.
Permission to create API tokens under your organization’s Atlassian policies.

Setup Steps

1

Confirm the integration account’s access

  1. Open your Confluence Cloud site.
  2. Sign in using the account that will own the AirMDR API token.
  3. Open each space that AirMDR must access.
  4. Open a representative page in each space.
  5. Confirm that the account can view the required content.
  6. If access is missing, ask the relevant administrator to grant the required permissions.
    A valid token can authenticate successfully while individual skills fail because the account cannot access their target content.
2

Obtain the Atlassian account email

The email is an existing account identifier; you do not generate it.
  1. In Confluence, select your profile avatar.
  2. Select Account settings.
  3. Open Email.
  4. Copy the email address associated with the account.
  5. Use this address in the AirMDR Email field.
You can also open Atlassian account settings directly.Example: airmdr-confluence@example.comAtlassian documents the navigation path through the avatar, Account settings, and Email.
Use the email of the account that creates the token.
3

Create an API token

Choose one of the following methods.Option A: Create an API token with scopes
  1. Open Atlassian API tokens.
  2. Select Create API token with scopes.
  3. Enter a descriptive name, such as AirMDR-Confluence-ReadOnly.
  4. Select an expiration date.
  5. Select Confluence as the app.
  6. Select the scopes listed in Section 3.3.
  7. Select Create.
  8. Copy the token into an approved password manager.
Option B: Create an API token without scopes
  1. Open the same API tokens page.
  2. Select Create API token.
  3. Enter a descriptive name and expiration date.
  4. Select Create.
  5. Copy the token into an approved password manager.
Atlassian permits token lifetimes of 1–365 days. The token value cannot be retrieved after the creation screen is closed.
If prompted, complete Atlassian’s identity verification before creating the token.
The Confluence API token may be visible only once.
If it is lost, generate a new token and update the AirMDR integration.
Do not include the token in screenshots, email, chat, Jira tickets, or documentation examples.
4

Obtain the Site URL

  1. Return to your Confluence site.
  2. Open the Confluence home page or any page within that site.
  3. Check the browser address bar.
  4. Copy the scheme and hostname.
  5. Remove /wiki and any remaining page path.
Example:The supplied AirMDR field guidance accepts the site root and ignores paths after the hostname. Entering the root URL keeps the configuration clear.
5

Obtain the Cloud ID

Complete this step when using a scoped API token.Method A: Retrieve it in your browser
  1. Open a new browser tab.
  2. Enter the following address, replacing your-domain with your site hostname:
  3. Press Enter.
  4. Locate the cloudId value in the response:
  5. Copy only the value, excluding the quotation marks.
  6. Paste it into the AirMDR Cloud ID field.
Method B: Retrieve it through the administration UI
This method requires access to Atlassian Administration.
  1. Open Atlassian Administration.
  2. Select the organization that owns your Confluence site.
  3. Navigate to Apps → Sites.
  4. Select the required site.
  5. Check the browser address bar for a URL containing:
  6. Copy the identifier immediately after /s/.
Atlassian documents both methods. The Cloud ID differs from the Organization ID; ensure it belongs to the intended Confluence site.

Confluence Credential Reference Table

Validate Connectivity

Use this when troubleshooting credentials outside AirMDR. Set the account email: ATLASSIAN_EMAIL='airmdr-confluence@example.com' For a scoped token, set:
For an unscoped token, set:
Check the current user:
When curl prompts for a password, paste the API token. Confirm that the response identifies the expected account. A successful HTTP response alone is insufficient if the result represents anonymous access. The current-user endpoint requires Confluence site access and an appropriate user-read scope for scoped authentication. Then test page access:
Replace the example page ID with a page the connected account can view. Atlassian documents page access and the read:page:confluence scope for these read operations.

Configure Confluence in AirMDR Integrations Dashboard

  1. Navigate to AirMDR, provide the credentials and click Login
  2. Navigate to the AirMDR Integrations Dashboard in the left navigation pane and select ADMIN → Integrations.
  3. Use the search option, enter the keyword “Confluence”, select the Connections tab, and click + New Connection button.
  4. Use the following values in the AirMDR integration configuration screen:
    1. In Remote Agent, select an AirMDR Remote Agent when Confluence API requests must run through an approved network route. Ensure the selected agent can resolve and reach api.atlassian.com for scoped API tokens, or your Confluence site hostname for unscoped API tokens, over HTTPS. For direct connectivity from AirMDR, leave this field unselected.
    2. In Expiry, select the Atlassian API token’s expiration date or an earlier date required by your organization’s credential-rotation policy.
      Expiry controls credential validity in AirMDR. It does not automatically rotate, extend, or revoke the token in Atlassian. Before expiry, create a replacement token, update API Token and Expiry, save and validate the connection, and then revoke the previous token when it is no longer required.
  5. Click Save.

Skills provided by this Integration

To view the details of Input Parameters and Output for the respective skills
  • Go to AirMDR → Confluence Integration page.
  • Select the Skills tab and click on the required listed skills.

Permissions and Roles by Skill

The following permissions apply to the Atlassian account connected to AirMDR. All listed skills perform read-only operations. Confluence user means an authenticated account with permission to access the Confluence site. API scopes apply when using a scoped API token and do not override the account’s resource permissions.
Organization, site, or space administrator access is not a blanket requirement for these skills. Grant only the access needed for the intended investigations.

Additional Information

Recovery sequence
  1. Confirm the expected Confluence site.
  2. Confirm the token owner’s email.
  3. Check token expiration and validity.
  4. Verify Site URL and Cloud ID configuration.
  5. Validate the current user.
  6. Test a known accessible space and page.
  7. Check scopes for the failing skill.
  8. Check connectivity from the selected execution environment.
  9. Retry the affected skill.
Where to checkRecommended monitoringMonitor for:
  • Repeated authentication failures.
  • Permission errors affecting previously accessible content.
  • Rate-limit responses.
  • Remote Agent connectivity failures.
  • Upcoming token expiration.
  • Unexpectedly empty or incomplete results.
Example log entriesThe following entries are illustrative troubleshooting examples, not a verified AirMDR log schema:
Recommended log levelsWhere logging controls are available:
Do not log tokens, authorization headers, or complete sensitive document bodies
✅ Do
  • Use a dedicated integration account: Use an organization-managed Atlassian account with a designated owner.
  • Apply least privilege: Grant access only to the spaces and content required for AirMDR investigations.
  • Use scoped API tokens: Select the documented read scopes required by the integration.
  • Protect credentials: Store the API token in an approved password manager and restrict access to AirMDR connection settings.
  • Verify the account and site: Ensure the email belongs to the token owner and the Cloud ID identifies the intended Confluence site.
  • Maintain secure connectivity: Use HTTPS with certificate validation enabled. If using a Remote Agent, ensure it can reach the required Atlassian endpoints.
  • Track expiry and rotate tokens: Set AirMDR Expiry no later than the token’s expiration date. Validate replacement credentials before revoking the previous token during routine rotation.
  • Review access periodically: Reassess account permissions when spaces, playbooks, ownership, or investigation requirements change.
❌ Don’t
  • Do not expose tokens: Never include API tokens or authorization headers in documentation, screenshots, logs, tickets, or messages.
  • Do not grant unnecessary privileges: Avoid administrator roles, write scopes, or delete scopes for the supplied read-only skills.
  • Do not use the account password: Enter an Atlassian API token in the API Token field.
  • Do not mix credentials: Avoid pairing one account’s email with another account’s token or using a Cloud ID from a different site.
  • Do not bypass access restrictions: Do not make restricted content public to resolve an integration permission error.
  • Do not disable certificate validation: Correct certificate or proxy trust issues before retrying.
  • Do not assume Expiry renews the token: Updating AirMDR Expiry does not extend or replace the Atlassian token.
  • Do not rely only on authentication success: Test the required skills against representative content to confirm sufficient access.
  • 📧 Contact AirMDR Support through your designated support channel.
  • 🔁 Rotate credentials regularly. Recommended cadence: As per your internal security policy
  • 🔄 Replace a token before expiration. Review the connection when:
    • The integration account owner changes.
    • Spaces or content permissions change.
    • The Confluence site changes.
    • New skills or playbooks are introduced.
    • Token policies change.
    • The selected Remote Agent changes.
Data exchangedThe returned information depends on the selected skill and the connected account’s access.Authentication and request flow

When an approved Remote Agent route is used, the selected agent provides the execution path to the appropriate API destination.
Mermaid Diagram 3Ports and endpointsCommon API paths include:These are Atlassian reference paths. An AirMDR skill may call multiple endpoints depending on its inputs.Encryption and credential handling
  • Use HTTPS for requests to Atlassian.
  • Keep certificate validation enabled.
  • Store tokens only in approved credential-management locations.
  • Restrict access to connection management and investigation outputs.
  • Apply your organization’s retention policy to retrieved content.
Atlassian documents TLS 1.2 or later for customer data in transit over public networks and AES-256 encryption at rest for Confluence Cloud data drives. These statements describe Atlassian’s environment; they do not establish AirMDR’s storage controls.