Confluence
Atlassian
System integration
Lets the Agent answer from Confluence pages with a shared account, or work as each end user: search, read, create and edit pages and comment after they confirm.
Connection routes
About the routes →FDE Rune
API key or tokenWhile the deployment is being designed, the FDE Agent first looks at the Confluence site's spaces, page trees, labels and how much content they hold. Needs an account that a site admin invites by email with view access, plus its API token.
Workspace Connector
API key or tokenWith a shared account (e.g. an organization account), the Agent searches the chosen spaces and reads pages to answer with a link to each source; it changes nothing. Needs a Confluence account just for the Agent, plus a read-only API token.
Connector
OAuth authorizationEach end user connects their own Atlassian account once. The Agent sees only what they can see and, after they confirm, creates pages, edits pages and comments in their name. Needs an OAuth app shared in the organization.
Documentation
Lets Asgard Agents answer questions from Confluence Cloud pages:
- Which page covers a policy, FAQ or procedure
- What a page says, with a link to it
- Which pages carry a label or changed recently
When each end user connects their own account, the Agent can also create pages, edit pages and add comments for them. Confluence records these changes in their name. The person confirms every change before it is sent.
What you need
- A Confluence Cloud site (
<site>.atlassian.net). - On paid plans, each account added to Confluence for Asgard takes a Confluence user seat.
- An API token is valid for up to a year, so it needs renewing.
- If the Atlassian organization blocks members from creating API tokens, an organization admin needs to allow it.
If the accounts, API tokens or OAuth app aren't set up yet, the FDE Agent walks you through creating them step by step. Creating them needs no coding.
Rollout consultation
Atlassian and Confluence Cloud are trademarks of their owner.