Connect Confluence

Using the intended Atlassian account:

1. Open the account’s security settings.
2. Go to API token management.
3. Create the appropriate scoped or non-scoped token.
4. Give it a descriptive name, such as Agent Barn — Knowledge Agent.
5. Set an expiration or rotation plan when available.
6. Copy the token.
7. Record which authentication type it uses.

Before connecting:

1. Confirm that the account can access the Confluence site.
2. Confirm that it has Confluence product access.
3. Open each intended space.
4. Verify page visibility.
5. Review space permissions.
6. Review page-level restrictions.
7. Remove access to unrelated spaces where possible.
8. Test one read-only action using the account.

The API token inherits the account’s effective Confluence access.

1. Stop the Agent, or begin the web interface’s restart-aware edit flow.
2. Open the Agent.
3. Go to Configuration.
4. Select Keys & integrations.
5. Select Edit.
6. Add Confluence under Integration credentials.
7. Choose Enter credentials.
8. Enter the base Atlassian site URL.
9. Select Scoped token or Non-scoped token.
10. Enter the account email.
11. Paste the API token.
12. Apply the configuration.
13. Restart the Agent if it was running.
14. Validate the credential.
15. Test space and page access.

The token is hidden after it is saved.

Use a Shared Confluence Credential

Confluence is supported by Organization Shared Credentials. To attach one:

1. Open the Agent’s integration configuration.
2. Select Confluence.
3. Choose Use shared credential.
4. Select the named Confluence credential.
5. Apply the configuration.
6. Restart the Agent.
7. Validate and test the connection.

Assign the Confluence Skill

The credential supplies authentication. The Confluence Skill gives the Agent detailed aai-cli instructions.

If the active Template requires Confluence:

1. Open the Agent’s Skills configuration.
2. Confirm that the Confluence Skill is assigned.
3. Confirm its pinned version.
4. Save the configuration.
5. Start the Agent.

An explicit Template requirement must be satisfied by an explicit Skill assignment.

1. Open Keys & integrations.
2. Find Confluence.
3. Select Validate.
4. Review the returned identity or service-account summary.
5. Resolve authentication errors.
6. Continue with space-level testing.

Validate a non-scoped credential

For a non-scoped token, Agent Barn requests:

https://example.atlassian.net/wiki/rest/api/user/current

Validation confirms that the site is reachable, the email and token authenticate, the account has Confluence product access, authentication was not treated as anonymous, and the connected identity is available.

{
  "validation_status": "valid",
  "validation_identity": "Knowledge Agent ([email protected])",
  "validation_error": null,
  "missing_scopes": []
}

Validate a scoped credential

Scoped tokens cannot use the legacy current-user endpoint used for non-scoped identity validation. Agent Barn instead requests:

https://api.atlassian.com/ex/confluence/{cloud_id}/wiki/api/v2/spaces

Any successful response confirms that the scoped token can authenticate through the gateway. The identity is reported as a service-account-style site summary:

Service account (example.atlassian.net) · 3 space(s) accessible

The count reflects the first returned result set, and should be treated as a connectivity summary rather than a complete access audit.

Verify space access

List the Confluence spaces available to the connected account.

aai-cli confluence spaces list \
  --limit 20 \
  --profile confluence-work

To check a known space:

aai-cli confluence spaces get DOCS \
  --profile confluence-work

Review the results for missing intended spaces and unexpected access.

Verify page listing and reads

aai-cli confluence pages list \
  --space DOCS \
  --status current \
  --limit 10 \
  --profile confluence-work

Using a specific space key reduces the chance of exposing unrelated content during verification.

Read a known non-sensitive page:

aai-cli confluence pages get 3964929 \
  --profile confluence-work

Confluence page operations use numeric page IDs. Confirm that the Agent can see the expected body and metadata without accessing restricted pages.

Verify comments

aai-cli confluence pages comments list 3964929 \
  --limit 10 \
  --profile confluence-work

To test comment creation on a designated page:

aai-cli confluence pages comments create 3964929 \
  --body "Agent Barn integration verification." \
  --profile confluence-work

Do not test writes against production documentation without approval.

Verify attachments

aai-cli confluence pages attachments list 3964929 \
  --limit 10 \
  --profile confluence-work

Download a known non-sensitive attachment:

aai-cli confluence pages attachments download \
  3964929 \
  att3997705 \
  --output local/logs/confluence-verification.txt \
  --profile confluence-work

Attachment upload requires separate write permission, and should be tested only on a designated page.

Verify page creation or editing

For an Agent intended to write pages, use a test space.

aai-cli confluence pages create \
  --space-key DOCS \
  --title "Agent Barn integration verification" \
  --body "Temporary verification page." \
  --profile confluence-work

aai-cli confluence pages update 3964929 \
  --title "Agent Barn integration verification — updated" \
  --body "Updated verification content." \
  --profile confluence-work

Clean up temporary content after the test.

1. Create a replacement token in Atlassian.
2. Record whether it is scoped or non-scoped.
3. Stop the Agent, or begin a restart-aware edit.
4. Open Keys & integrations.
5. Enter the complete replacement Confluence credential.
6. Re-enter the site URL, authentication type, and email.
7. Apply and restart.
8. Validate the credential.
9. Test space and page access.
10. Revoke the old token.

Stored credential values cannot be retrieved or partially edited.

Change the Confluence account

1. Prepare a token for the replacement Atlassian account.
2. Confirm its product, space, and page access.
3. Replace the complete credential.
4. Apply and restart.
5. Validate the identity.
6. Test intended spaces and pages.
7. Revoke the old token when appropriate.

The replacement account may have different page restrictions, even when it belongs to the same spaces.

1. Stop the Agent, or begin a restart-aware edit.
2. Identify any assigned Skill requiring confluence.
3. Remove or replace the Skill when permitted.
4. Open Keys & integrations.
5. Select Remove for Confluence.
6. Apply the configuration.
7. Restart the Agent.
8. Confirm that Confluence is unavailable.
9. Revoke the token in Atlassian.

Agent Barn rejects removal while a remaining assigned Skill requires Confluence.