> ## Documentation Index
> Fetch the complete documentation index at: https://docs.meetjamie.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Confluence

> Let Jamie find and read Confluence pages before a meeting, and publish meeting notes as new pages, page updates, or comments afterward

## Set up for yourself

Works on all plans. Your own connection works in Ask Jamie, Sidekick, briefings, and your own workflows. Jamie signs in with your Atlassian account email and an Atlassian API token.

**1. In Atlassian**

1. Open [**Atlassian account → Security → API tokens**](https://id.atlassian.com/manage-profile/security/api-tokens)
2. Click **Create API token**, give it a name such as Jamie, and choose an expiry date. Don't choose **Create API token with scopes**, because Jamie connects to your site address and scoped tokens don't work there
3. Copy the token right away. Atlassian shows the token only once

**2. In Jamie**

1. Open [**Settings → Agent → Connectors**](https://app.meetjamie.ai/settings/agent#connectors)
2. Find **Confluence** and click **Connect**
3. In **Atlassian site URL**, enter the address you see when you are signed in to Confluence, such as `yourteam.atlassian.net`
4. In **Atlassian account email**, enter the email of the account that created the token
5. Paste the token into **API key** and click **Connect**. Jamie tests the token with a check that changes nothing in Confluence

To test or change the token later, open **Confluence** and click **Manage key**.

Jamie sees only the spaces and pages your Atlassian account can see. Every page and comment that Jamie writes shows as yours.

> [!NOTE]
>
> One Atlassian API token works for both Jira and Confluence on the same site. Jamie still asks you to connect each one on its own, so you choose which of the two Jamie can use.

## Set up for the workspace (admins only)

Needs the Team or Enterprise plan. Only [workspace workflows](https://docs.meetjamie.ai/agent/workflows.md#workspace-workflows) use this connection. Jamie signs in as an Atlassian account that your team creates only for Jamie.

**1. In Atlassian**

1. Create an Atlassian account for Jamie and give it access to the Confluence spaces it should use. Don't use your own account
2. Signed in as that account, create an API token under [**Atlassian account → Security → API tokens**](https://id.atlassian.com/manage-profile/security/api-tokens) with **Create API token**
3. Copy the token right away. Atlassian shows the token only once

**2. In Jamie**

1. Open [**Settings → Agent → Connectors**](https://app.meetjamie.ai/settings/agent#connectors) and select **Confluence**
2. Under **Workspace connection**, click **Add service account key**
3. Enter the **Atlassian site URL** and the **Atlassian account email** of the account you created
4. Paste the token into **Atlassian API token** and click **Save Confluence key**

Workspace workflows act as that Atlassian account, not as the person whose meeting it is. So Jamie puts the meeting owner's name in everything it writes.

## What Jamie can do

Jamie can:

* Find spaces and search pages by title or text
* Read a page before a meeting to bring you up to speed
* Publish meeting notes as a new page under the parent page you choose
* Add a section to an existing page, or leave a comment under it

Jamie can do more than this list. It can't delete anything in Confluence.

Try asking: *"Publish the notes from this meeting under our Weekly syncs page in Confluence"*

## Disconnect

* **Your own connection.** Open **Confluence** in [**Settings → Agent → Connectors**](https://app.meetjamie.ai/settings/agent#connectors). Click **Manage key**, and then click **Disconnect**.
* **The workspace connection.** Under **Workspace connection**, click **Disconnect**. Workspace workflows that use Confluence pause. They start again when a workspace admin connects Confluence again.

To stop the token working everywhere, revoke it in [**Atlassian account → Security → API tokens**](https://id.atlassian.com/manage-profile/security/api-tokens).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.