Skip to content
Guide
Connectors

Confluence Connector

Connect Confluence Cloud or Confluence Server / Data Center to a LlamaCloud project by signing in with Atlassian or with an API token, and sync a Confluence space's pages and attachments into a project folder.

The Confluence connector syncs one whole space into a connected folder: every current page, plus the files attached to them. There are two ways to connect it:

CardWorks withSigns in as
ConfluenceConfluence CloudYou, through an Atlassian sign-in popup
Confluence KeysConfluence Cloud, or Server / Data CenterAn API token (Cloud) or personal access token (Server / Data Center)

Atlassian’s sign-in doesn’t reach Server / Data Center, so for a self-hosted Confluence the token is the only option.

  1. On Files → Connections, click Add connection, pick Confluence, and click Authorize.
  2. Sign in to Atlassian in the popup, choose your site, and accept.

The connection asks for read-only access to pages, attachments, and spaces, and can read the spaces your account can open.

The token’s own permissions decide which spaces the connection can see, so use an account that can read the spaces you want to sync.

Confluence Cloud: create an API token at id.atlassian.com/manage-profile/security/api-tokens.

Server / Data Center: create a personal access token from your profile, under Settings → Personal Access Tokens.

Then on Files → Connections, click Add connection, pick Confluence Keys, and fill in:

FieldCloudServer / Data Center
Confluence site URLhttps://your-team.atlassian.net/wiki, including /wikiYour base URL, e.g. https://confluence.example.com
Atlassian account emailThe email of the account that made the tokenLeave empty
API tokenThe API tokenThe personal access token

Whether you fill in the email is how the connector tells Cloud and Server / Data Center apart, so leave it empty for a personal access token.

Click Connect. LlamaCloud asks the site who the token belongs to before saving. The site URL has to start with https:// (or http://) and resolve to a public address, so a Server / Data Center instance that’s only reachable on your internal network can’t be connected.

Create a folder from a Confluence connection

Section titled “Create a folder from a Confluence connection”

From Files → New folder → Connected folder, pick your Confluence connection and choose a Space from the list. Archived spaces aren’t listed.

If the list can’t load, or the account can see more than 200 spaces, you get a Space key box instead. The key is in any page URL from that space, right after /spaces/: in …/wiki/spaces/ENG/pages/… it’s ENG.

A folder always syncs a whole space. You can’t pick individual pages or a page tree.

What the Confluence connector puts in your folder

Section titled “What the Confluence connector puts in your folder”
  • Each page becomes an HTML file, with the images embedded in it included inline.
  • Each attachment comes through as its own file, alongside the page.
  • Blog posts aren’t synced, only pages.

Every sync lists the whole space and compares it with what’s in the folder. Edited pages and attachments are downloaded again, and deleted ones are removed. A big space takes longer per sync even when little has changed.

MessageWhat to check
”Confluence rejected this token”The token is wrong or revoked, the email doesn’t match the account that made it, or you filled in an email for a Server / Data Center token.
”No Confluence API answered at …”The site URL points at a page instead of the site. For Cloud, it should end in /wiki.
”Confluence URL must resolve to a public address”The site is on a private network.
”confluence space … not found”The space key is wrong, or the connection’s account can’t see that space.
Note for AI agents: this documentation is built for programmatic access. - Overview of all docs: https://developers.llamaindex.ai/llms.txt - Any page is available as raw Markdown by appending index.md to its URL — e.g. https://developers.llamaindex.ai/llamaparse/parse/getting_started/index.md - Agent-friendly REST search APIs live under https://developers.llamaindex.ai/api/ — search (BM25 full-text), grep (regex), read (fetch a page), and list (browse the doc tree). See https://developers.llamaindex.ai/llms.txt for parameters. - A hosted documentation MCP server is available at https://developers.llamaindex.ai/mcp. If you support MCP, you can ask the user to install it for browsing these docs directly (an alternative to the REST API). Setup: https://developers.llamaindex.ai/for-agents/mcp/ - Other LlamaIndex tooling for agents — the LlamaParse Platform MCP server, agent skills and plugins, and the n8n node — is mapped at https://developers.llamaindex.ai/for-agents/