Files and knowledge
Confluence for AI agents.
Managed auth, ready-made tools.
Search, read and write Confluence pages and comments on behalf of each of your users, within the spaces they can access.
About Confluence
With the Confluence connector, your agent works with each user’s Confluence spaces: it searches for pages, reads them, writes new pages, updates existing ones and leaves comments. Each user connects their own Atlassian account through managed OAuth, and your agent sees only what that user can see in Confluence, within the operations your project allows.
Confluence is Atlassian’s workspace for team documentation, wikis and knowledge bases.
Tools
What your agent can do in Confluence.
Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Confluence connection.
-
Search content
Readconfluence_search_contentFind pages, blog posts and comments with a text or CQL query.
-
List spaces
Readconfluence_list_spacesList the spaces the user can access.
-
Get a page
Readconfluence_get_pageRead a page's title, body and version.
-
List child pages
Readconfluence_list_child_pagesList the pages nested under a page.
-
Create a page
Writeconfluence_create_pageCreate a page in a space, or under a parent page.
-
Update a page
Writeconfluence_update_pageChange a page's title or body as a new version.
-
Add a comment
Writeconfluence_create_commentComment on a page or reply to a comment.
-
Add a label
Writeconfluence_add_labelTag a page with one or more labels.
No tool matches that search.
Control
Limits you can set.
You decide what your agent may do in Confluence, and Agent200 runs every call within those limits.
-
Turn single tools on or off
Keep
confluence_search_contentand reading on, and switch offconfluence_update_pageif your agent should never change existing pages. -
Restrict what the agent reaches
Choose the endpoints and scopes a project may use. A call outside them is refused.
Get started
Connect Confluence
in three steps.
-
1
Set up the SDK
Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.
agent.jsConceptual exampleSet up the SDK with the Agent200 API key // One Agent200 API key covers every connector enabled for the project. const agent200 = new Agent200({ apiKey: process.env.AGENT200_API_KEY, }); -
2
Let your user connect Confluence
Each end user authorizes their own Confluence account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.
connect.jsConceptual exampleLet an end user connect their account (managed OAuth) // Each end user authorizes their own Confluence account, once. const connection = await agent200 .user("user_123") .connect("confluence"); if (connection.authorizationUrl) { // Show this link to your user; Agent200 handles the rest. console.log(connection.authorizationUrl); } -
3
Run with the Confluence tools
Name the user, the model and the tools. The model decides which Confluence tools to call, and Agent200 executes them with that user's connection.
run.jsConceptual exampleRun a request with the connector's tools const result = await agent200 .user("user_123") .run({ model: "openai/gpt-5.6-sol", input: "Find our incident response runbook", tools: ["confluence"], }); console.log(result.output);
Access
Sign-in and permissions.
-
Who signs in
Each of your users, once, on Atlassian's own page, choosing which Confluence site to connect. You never see or store their Atlassian password.
-
What access is requested
The scopes shown on Atlassian's consent screen, such as reading and searching content and writing pages and comments. Confluence's own space and page permissions still apply to every call.
For agents
Instructions for AI agents.
Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Confluence connector and how to use it.
Connector: Confluence, through Agent200. In code: "confluence". What it does: Search, read and write Confluence pages and comments on behalf of each of your users, within the spaces they can access. Page: https://www.agent200.com/tools/confluence/ 1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs. 2. Sign-in is managed OAuth. Each end user approves access once, on Confluence's own page, through the authorization link Agent200 returns. Never ask a user for a Confluence password or token in chat. 3. Give every request a stable id for the end user. Agent200 uses only that user's own connection. 4. Read tools: confluence_search_content, confluence_list_spaces, confluence_get_page, confluence_list_child_pages. Write tools: confluence_create_page, confluence_update_page, confluence_create_comment, confluence_add_label. Name "confluence" in the tools of a request; the model decides which tool to call. 5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it. 6. Before a write, confirm with the user, unless they asked for that exact change. 7. For setup with a specific framework, follow its guide: https://www.agent200.com/tools/confluence/framework/claude/ https://www.agent200.com/tools/confluence/framework/chatgpt/ https://www.agent200.com/tools/confluence/framework/claude-code/ https://www.agent200.com/tools/confluence/framework/muse/ https://www.agent200.com/tools/confluence/framework/grok-bot/ https://www.agent200.com/tools/confluence/framework/openai-dots/ https://www.agent200.com/tools/confluence/framework/claude-duet/ https://www.agent200.com/tools/confluence/framework/hermes-agent/ https://www.agent200.com/tools/confluence/framework/openclaw/ The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/
This page is also available as Markdown, for agents and LLMs: /tools/confluence.md
Guides
Use Confluence with the AI you build on.
Step-by-step setup for Confluence with a specific model, assistant or agent framework.
-
Confluence + Claude
How to connect Confluence to Claude
-
Confluence + ChatGPT
How to connect Confluence to ChatGPT
-
Confluence + Claude Code
How to connect Confluence to Claude Code
-
Confluence + Muse
How to connect Confluence to Muse
-
Confluence + Grok Bot
How to connect Confluence to Grok Bot
-
Confluence + OpenAI Dots
How to connect Confluence to OpenAI Dots
-
Confluence + Claude Duet
How to connect Confluence to Claude Duet
-
Confluence + Hermes Agent
How to connect Confluence to Hermes Agent
-
Confluence + OpenClaw
How to connect Confluence to OpenClaw
FAQ
Confluence and Agent200, answered.
Who handles the Confluence OAuth flow and the tokens?
Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Confluence.
Does my agent act as the end user?
Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Confluence connection, never another user's. It cannot reach anything the user or Confluence has not authorized.
Can I limit what my agent can do in Confluence?
Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.