> For the complete documentation index, see [llms.txt](https://docs.eesel.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eesel.ai/integrations/knowledge/confluence/confluence-setup.md).

# Set up Confluence

Confluence setup for your AI agent, screen by screen: create an Atlassian API token, then connect it in eesel, with a screenshot for each step.

Setting up Confluence for your AI agent takes one API token from Atlassian and one secure form in eesel. An API token is a password-like key that lets eesel read Confluence. You create the token in your Atlassian account, then paste it into eesel with your Confluence subdomain and email.

This way needs no Atlassian Marketplace app. To install the Marketplace app instead, see [Connect with the Marketplace app](https://docs.eesel.ai/integrations/knowledge/confluence.md#connect-with-the-marketplace-app).

## Before you begin

* You need a **Confluence Cloud** site, at an address like `yourcompany.atlassian.net`. If your Confluence address does not end in `.atlassian.net`, [get in touch](https://docs.eesel.ai/support/contact-us.md).
* Pick the **Atlassian account** your agent will use. Your agent signs in as this account, so it sees only what this account sees. The account needs a Confluence licence, a seat with access to Confluence, and must be able to open the spaces you want answered from.
* Have your **subdomain** ready. It is the part before `.atlassian.net` in your Confluence address. Use `yourcompany`, not `yourcompany.atlassian.net`.

## Walkthrough

{% stepper %}
{% step %}

### Open your Atlassian API tokens page

Sign in to Atlassian as the account your agent will use. Open [your API tokens page](https://id.atlassian.com/manage-profile/security/api-tokens). You can also get there from your Atlassian account: open **Security**, then **API tokens**.

<figure><img src="https://3732419023-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2xXO0947TYoPIhGoBgSE%2Fuploads%2Fgit-blob-ff938e6ebd06fea7e701a3c7be442827b71443b8%2Fconfluence-atlassian-api-tokens.png?alt=media" alt="The API Tokens page in Atlassian account settings under Security, with Create API token and Create API token with scopes buttons and a list of existing tokens"><figcaption><p>The API tokens page in your Atlassian account.</p></figcaption></figure>

Click **Create API token**. Do not use **Create API token with scopes**. eesel needs the plain token.
{% endstep %}

{% step %}

### Name the token and pick an expiry

Give the token a name your team will recognise, for example `eesel Confluence`. Pick an expiry date, then click **Create**.

<figure><img src="https://3732419023-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2xXO0947TYoPIhGoBgSE%2Fuploads%2Fgit-blob-f6d0de32da86b8a3a9332920b46c77e3614eca46%2Fconfluence-atlassian-create-token.png?alt=media" alt="The Create an API token dialog in Atlassian, with the name eesel Confluence filled in, an expiry date, and a Create button"><figcaption><p>The Create an API token dialog, with a name and an expiry date.</p></figcaption></figure>

Atlassian allows up to one year. A longer expiry means you reconnect less often. When the token expires, your agent stops reading Confluence until you connect again with a new token.
{% endstep %}

{% step %}

### Copy the token

Atlassian shows the new token once. Click **Copy**, then click **Done**.

<figure><img src="https://3732419023-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2xXO0947TYoPIhGoBgSE%2Fuploads%2Fgit-blob-af5bff4399e52ba43992d40ddc02b53eda7c7551%2Fconfluence-atlassian-copy-token.png?alt=media" alt="The Copy your API token dialog in Atlassian, with the token masked, a Copy button and a Done button"><figcaption><p>The new token, masked, with the Copy button beside it.</p></figcaption></figure>

{% hint style="warning" %}
Copy the token before you click **Done**. Atlassian does not show it again. If you lose it, create a new one.
{% endhint %}
{% endstep %}

{% step %}

### Ask your agent to connect Confluence

In the eesel dashboard, ask your agent in the chat to connect Confluence. It opens a secure form with one field for the token, and asks for your subdomain and email in the chat.

<figure><img src="https://3732419023-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2xXO0947TYoPIhGoBgSE%2Fuploads%2Fgit-blob-9eacc9d8195833f0ebb2b88aef6b3b1ad1bd882c%2Fconfluence-api-token-connect-chat.png?alt=media" alt="The dashboard chat where the user asks to connect Confluence, and the agent shows a secure form with an Atlassian API token field and asks for the Confluence subdomain and the Atlassian account email"><figcaption><p>The agent opens a secure form for the token and asks for two details.</p></figcaption></figure>

Prefer to click? Open **Integrations** in the left sidebar, pick **Confluence**, then choose **API token**. It asks for the same three things in one form.
{% endstep %}

{% step %}

### Paste the token into the secure form

Paste the token into the form and click **Save securely**.

<figure><img src="https://3732419023-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2xXO0947TYoPIhGoBgSE%2Fuploads%2Fgit-blob-caec7979f9605517e2b121a39fc5280cc87e2011%2Fconfluence-api-token-form-filled.png?alt=media" alt="The secure form in the dashboard chat with the token pasted in and masked, and the Save securely button ready to click"><figcaption><p>The form filled in, with the token masked.</p></figcaption></figure>

A person always pastes the token in. If an AI tool such as Claude Code runs the setup, it waits for you to do this step.
{% endstep %}

{% step %}

### Give your subdomain and email

Reply in the chat with your subdomain and the email on the Atlassian account that made the token. Your agent connects, then lists the spaces it can read to show the connection works.

<figure><img src="https://3732419023-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2xXO0947TYoPIhGoBgSE%2Fuploads%2Fgit-blob-2c9359c1c931041b108d29737d01ac2166206d33%2Fconfluence-api-token-connected-chat.png?alt=media" alt="The dashboard chat where the user gives the subdomain and email, and the agent confirms Confluence is connected and lists four spaces it can read"><figcaption><p>The agent confirms the connection and lists the spaces it can see.</p></figcaption></figure>

**Check it worked.** **Confluence (API token)** appears in the left sidebar. Open it to see the connection and the actions your agent can take. From a terminal, `eesel status` lists the integration as connected.

<figure><img src="https://3732419023-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2xXO0947TYoPIhGoBgSE%2Fuploads%2Fgit-blob-d9ce23f8c16890d6660c07a772c28f3da36fb282%2Fconfluence-api-token-integration-page.png?alt=media" alt="The Confluence (API token) integration page in eesel, marked Connected with the site name, and a Read group of four actions: Get Confluence Page, List Child Pages, List Confluence Spaces and Search Confluence"><figcaption><p>The integration page, with the four read actions your agent can use.</p></figcaption></figure>

eesel does not copy your pages. Your agent reads Confluence live each time it answers.
{% endstep %}
{% endstepper %}

## Troubleshooting

<details>

<summary>The connection fails</summary>

* Check the **subdomain** is only the part before `.atlassian.net`.
* Check the **email** is the one on the Atlassian account that made the token, not a team alias.
* Check you used **Create API token**, not **Create API token with scopes**.
* New tokens can take up to a minute to work. Wait a minute and connect again.

</details>

<details>

<summary>It worked, then every Confluence answer started failing</summary>

The token has probably expired, or someone revoked it. Create a new token and ask your agent to connect Confluence again.

</details>

<details>

<summary>Connected, but your agent cannot find a page</summary>

Your agent sees what the connected account sees. Check that account can open the space and the page in Confluence. The account also needs a Confluence licence. An account that only has Jira can sign in but cannot read Confluence.

</details>

## FAQ

<details>

<summary>Is it safe to give eesel a Confluence API token?</summary>

Yes. The token goes into a secure form, straight to eesel, never into the chat, and the form expires in 30 minutes. Your agent reads Confluence, and can create a page or change one's title or body as the connected account. eesel's safety check holds a risky change for your approval, unless you set those actions to ask you first.

</details>

<details>

<summary>Can I use the same token for Jira and Confluence?</summary>

Yes, if the account has both a Jira and a Confluence licence. It is the same kind of Atlassian API token. A separate token for each makes it easier to revoke one without breaking the other.

</details>

## Related pages

* [Confluence](https://docs.eesel.ai/integrations/knowledge/confluence.md) for what your agent does with your wiki
* [Jira Service Management](https://docs.eesel.ai/integrations/helpdesks/jira-service-management.md) and [its setup page](https://docs.eesel.ai/integrations/helpdesks/jira-service-management/jira-service-management-setup.md), which use the same kind of token
* [Slack](https://docs.eesel.ai/integrations/communication/slack.md) for asking your agent in a Slack thread
* [Actions and Approvals](https://docs.eesel.ai/instructions-and-memory/actions-and-approvals.md) for choosing what your agent may do
* [Set up from Claude Code or the terminal](https://docs.eesel.ai/getting-started/set-up-from-a-coding-agent.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.eesel.ai/integrations/knowledge/confluence/confluence-setup.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
