Confluence connector

Mirror selected Confluence spaces and pages into a Workspace, through Atlassian OAuth and the ctxpipe Forge app.

The Confluence connector mirrors the Confluence spaces and pages that you select into a Workspace repository. ctxpipe does not read the whole site. You choose what agents can use.

ctxpipe connects to the Confluence site through Atlassian OAuth and the ctxpipe Forge app. When pages or spaces change, the Forge app tells ctxpipe, and ctxpipe updates the mirror.

On a self-hosted deployment, the operator provides the Atlassian OAuth app and the Forge setup first. See Self-host Confluence & Atlassian.

ctxpipe / Confluence connector

OAuth reads. Forge notifies.

Rail A / Account and API access

Actor

User

Signs in via Atlassian OAuth from ctxpipe

Atlassian OAuth

Account and permission grant

Confirms account, discovers sites, grants API access to selected site

ctxpipe stores

Linked account and site

OAuth token stored, site linked, awaiting Forge confirmation

Rail B / Site app and change events

Actor

Confluence admin

Installs ctxpipe Forge app into the Confluence site

ctxpipe Forge app

Runs inside Confluence site

Sends install status and page or space change events to ctxpipe

ctxpipe receives

Site events

Install confirmed, change events flowing, sync triggered

Converged state

ctxpipe Confluence Connector - active

Site linked via OAuthForge installed and events flowingSpaces selected for syncChanges auto-captured

GitHub sync repo - ingestion - knowledge graph

git-nativeauto-syncedagent-ready

OAuth

Gives ctxpipe permission to read Confluence content via Atlassian APIs.

Forge

Lets the Confluence site notify ctxpipe when content changes.

Why both

OAuth reads. Forge watches. Neither alone is enough.

OAuth grants read access. Forge confirms installation and sends change events. Together they let ctxpipe sync selected Confluence content into a GitHub-backed source.

Data flow

Confluence connector - data flow

ctxpipe

Source

Confluence Cloud

Spaces and pages

Change events

OAuth reads / Forge events

Connector

ctxpipe Confluence Connector

Reads selected pages via OAuth

Receives change events via Forge

Converts pages to repo-backed files

Writes Markdown

Sync target

GitHub Repository

confluence/<spaceKey>/

sources/confluence/<name>.md

Git history / visible / reviewable

Repository ingestion

Ingestion

ctxpipe Ingestion

Search index

Knowledge graph

Retrieval stores

Context retrieval

Interface

ctxpipe MCP

ctxpipe read tools

Consumers

Agents

Cursor / Claude Code / Codex / custom

Content movement

Control / access signal (OAuth, Forge)

Selected Confluence content moves into a team-controlled GitHub repository before ctxpipe ingests it for search, graph context, and MCP tools.

Before you start

You need:

permission to authorize Atlassian OAuth for the Confluence site;
permission to install the ctxpipe Forge app on the site, or an Atlassian admin who can install it.

Not sure whether you have the right access?

Open admin.atlassian.com, choose the Confluence site, and check whether you can open Connected apps and install apps. Atlassian requires organization admin or site admin access for this. If you cannot, ask an Atlassian admin to install the Forge app. See Atlassian Connected apps.

Connect Confluence

Start from Connectors

Open Connectors, choose Add connection, then Atlassian Confluence. The setup wizard tracks each task until the connector is ready.

Add Confluence connection from the ctxpipe Connectors page

Link your Atlassian account

Link your Atlassian account with OAuth. This tells ctxpipe which Atlassian cloud site you connect. If the account is already linked to another ctxpipe organization, the wizard asks you to confirm or cancel.

Link Atlassian account step in the ctxpipe Confluence setup wizard

Install the Forge app

Install the ctxpipe Forge app on the same Atlassian site. The Forge app lets ctxpipe read the content that you select, and tells ctxpipe about changes.

Install the ctxpipe Forge app in Atlassian Confluence

Add to Workspaces

Select the Workspaces, then select the spaces and pages in the tree. For each space, select all pages or only some. Keep the scope intentional:

start with the spaces that your engineering team uses;
leave out old or sensitive areas that agents must not rely on;
prefer the authoritative docs to duplicates and abandoned pages.

Choose Add to Workspaces, then merge the pull request that adds sources/confluence/<name>.md. See Add a tool to a Workspace.

Source file

For each space, pages is all or a list of page ids:

---
provider: confluence
connection: con_example
spaces:
  - key: ARCH
    pages: all
  - key: OPS
    pages: ["12345", "67890"]
---

Files in the repository

Mirrored pages are under confluence/<spaceKey>/, in the page tree of the space. A page is <slug>--<pageId>.md, or <slug>--<pageId>/index.md when it has child pages. Attachments and embedded media are under confluence/<spaceKey>/_assets/<pageId>/. Each asset can be up to 25 MiB, and each page up to 100 MiB in total. A file that is too large or not safe stays a link to Confluence. ctxpipe never writes Atlassian download URLs to git.

For problems, see Troubleshooting.

Confluence connector - data flow

On this page