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

# Give AI Agents Search and Edit Access to Confluence

> Let agents search Confluence with CQL, read pages, and publish updates. Connect in one click with OAuth, and the gateway keeps the token hidden.

## Overview

Buckle connects AI agents to Confluence Cloud. Agents can search your wiki, read pages, and create or update them. The gateway injects the token into every request, so your agent never sees it.

Connecting takes one click. You don't create an Atlassian app or copy any keys.

## What you will set up

* A Confluence Cloud connection through Atlassian OAuth, with no app or keys to create
* Automatic token injection on every Confluence request
* Per-agent, per-tool access, such as read freely and approve page edits

## Connect Confluence

**1. Click Connect**

In the Buckle dashboard, open **Settings** > **Apps** > **Confluence** and click **Connect Confluence**.

![Buckle connect window for Confluence, showing the Buckle and Confluence logos, the Connect to Confluence button, and an auto-connect countdown.](https://mintcdn.com/onecli-17d3f772/hJP3XqgFsBDnXHKy/images/integrations/confluence/buckle-connect-confluence.png?fit=max\&auto=format\&n=hJP3XqgFsBDnXHKy\&q=85\&s=bf65ce7c4ff7a269c76731847ab66472)

The Confluence connect window in Buckle.

**2. Accept in Atlassian**

Sign in to Atlassian, pick your Confluence site, and click **Accept**. You're done. Buckle keeps the connection active from then on.

> [!NOTE]
>
> You don't need to be a Confluence admin. Atlassian may show a notice that the app hasn't been reviewed by Atlassian yet. It's safe to continue.

## What agents can do

* Search all spaces with CQL, filtered by space, type, label, or contributor
* Read a page's full content, metadata, comments, and attachments
* Create pages and update existing ones
* Add comments and labels
* List spaces and browse page hierarchies

## Controlling access

[Grant](/docs/guides/agent-access.md) the connection to each agent that needs it, and choose per tool what runs freely, what needs approval, and what's blocked. Organization [rules](/docs/guides/rules.md) add guardrails on top. A blocked request never reaches Confluence.

To disconnect, remove the connection in **Settings** > **Apps** > **Confluence**, then revoke Buckle in Atlassian under **Account settings** > **Connected apps**.

***

## Self-hosted: use your own Atlassian app

> [!NOTE]
>
> **Skip this section on Buckle Cloud.** It's only for self-hosted Buckle without `ATLASSIAN_CLIENT_ID` and `ATLASSIAN_CLIENT_SECRET` set, or if you want your own company name on Atlassian's consent screen. One Atlassian app serves both Jira and Confluence: if you already set one up for Jira, add the Confluence scopes below and you're done.

> [accordion] 1. Create the Atlassian app
>
> Follow [Create the Atlassian app](/docs/integrations/jira.md#self-hosted-use-your-own-atlassian-app) on the Jira page. If you already have one for Jira, reuse it.

> [accordion] 2. Add the Confluence permissions
>
> Open **Permissions**, click **Add** next to **Confluence API**, then **Configure**. Add these on both tabs:
>
> | Tab | Scopes |
> | - | - |
> | **Classic scopes** | `read:confluence-content.all`, `write:confluence-content`, `read:confluence-space.summary`, `search:confluence` |
> | **Granular scopes** | `read:page:confluence`, `write:page:confluence`, `read:space:confluence`, `read:content:confluence` |
>
> Also add `read:me` under **User identity API** if it isn't there yet, and the Jira scopes from the [Jira page](/docs/integrations/jira.md#self-hosted-use-your-own-atlassian-app). Atlassian keeps one consent per person for each app, so Buckle asks for the Confluence and Jira scopes together. If any of them is missing from the app, Atlassian shows an error instead of the consent screen.
>
> > [!WARNING]
> >
> > Use `read:confluence-space.summary` (**space**), not `read:confluence-content.summary` (**content**). If the space scope is missing, Atlassian shows "Something went wrong" instead of the consent screen.
>
> > [!NOTE]
> >
> > **Upgrading an existing app?** Buckle now also asks for `search:confluence`, which CQL search needs. Add it to the app's **Classic scopes** before you upgrade Buckle, or Atlassian shows an error instead of the consent screen. Then reconnect Confluence so the new token includes it. Until you do, search returns `401` "scope does not match" while page reads keep working.

> [accordion] 3. Add the callback URL and connect
>
> In Buckle, open **Settings** > **Apps** > **Confluence** > **Custom credentials** and copy the **Redirect URI**. It ends in `/v1/apps/oauth/atlassian/callback`, the same URI as Jira. Add it to the app's **Callback URLs** under **Authorization**. Then paste the app's **Client ID** and **Secret**, select **Save credentials**, then **Connect** and accept in Atlassian.
>
> ![Buckle Custom credentials card for Confluence with the setup guide link, the Redirect URI and its copy button, and the client ID and secret fields.](https://mintcdn.com/onecli-17d3f772/hJP3XqgFsBDnXHKy/images/integrations/confluence/buckle-custom-credentials-confluence.png?fit=max\&auto=format\&n=hJP3XqgFsBDnXHKy\&q=85\&s=278f37dfd6fad1de3829428a66b8ad46)
>
> Copy the Redirect URI from Custom credentials in Buckle.

## FAQ

> [accordion] Do I need to be a Confluence admin to connect?
>
> No. Any Confluence user can connect. Atlassian may show a notice that the app hasn't been reviewed yet, and it's safe to continue.

> [accordion] Does the agent see my Atlassian token?
>
> No. The token stays in Buckle, and the gateway adds it to each Confluence request at the proxy. See [How it works](/docs/how-it-works.md).

> [accordion] Can an agent read Confluence without editing pages?
>
> Yes. When you [grant](/docs/guides/agent-access.md) the connection, allow search and read tools and block or require approval for creating and updating pages.

> [accordion] How do I reconnect or revoke access?
>
> Reconnect from **Settings** > **Apps** > **Confluence**. To revoke, remove the connection there, then revoke Buckle in Atlassian under **Account settings** > **Connected apps**.


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