How to connect Confluence to OpenClaw
Connect Confluence to OpenClaw with ClawLink in one click — 69 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup.
ConfluenceOAUTH2MCPCreate and organize team documentation. Once connected, OpenClaw can read and act on Confluence from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Confluence access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Confluence setup: install one ClawHub skill, connect Confluence in the browser, and OpenClaw can call real Confluence actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into OpenClaw, or open the Confluence skill on ClawHub.
Before installing anything, inspect the ClawHub skill metadata and setup requirements.
If the skill asks you to install a third-party package or CLI, verify its source, maintainer, and package contents before running the install command.
Install the skill "Confluence" (hith3sh/confluence-workspace) from ClawHub only after those checks pass.
Skill page: https://clawhub.ai/hith3sh/confluence-workspace
Keep the work scoped to this skill only.
After install, help me finish setup from verified skill metadata.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.Setup
It takes three steps to connect OpenClaw to Confluence.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Confluence
One-click OAuth in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Confluence?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Confluence in the ClawLink dashboard — a one-click OAuth approval, no API keys.
Verify the connection by asking OpenClaw:
Search Confluence for what I need, summarize the results, and tell me the next best action.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Confluence is connected in the dashboard, that agent calls the same 69 Confluence tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Confluence MCP for OpenClaw
Looking for a Confluence MCP server for OpenClaw? ClawLink connects Confluence to OpenClaw and exposes 69 Confluence tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Confluence integration works the same way.
What the OpenClaw Confluence integration can do
69 Confluence tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 69.
30 of 69 Confluence tools for OpenClaw
| Tool | What it does |
|---|---|
Cql search confluence_cql_search | Searches for content in Confluence using Confluence Query Language (CQL). |
Create blogpost confluence_create_blogpost | Create a new Confluence blog post. |
Create page confluence_create_page | Create a new Confluence page in a specified space. |
Create space confluence_create_space | Create a new Confluence space. |
Get attachment labels confluence_get_attachment_labels | Get labels for a Confluence attachment. |
Get blog posts confluence_get_blog_posts | List blog posts in a Confluence space. |
Get current user confluence_get_current_user | Get the currently connected Confluence user. |
Get page by ID confluence_get_page_by_id | Get a Confluence page by ID. |
Get pages confluence_get_pages | List pages in a Confluence space. |
Get spaces confluence_get_spaces | List Confluence spaces. |
Update page confluence_update_page | Update an existing Confluence page. |
Download attachment confluence_download_attachment | Downloads an attachment from a Confluence page and returns a publicly accessible S3 URL |
Find text selections confluence_find_text_selections | Finds text occurrences in a Confluence page's content to help with inline comment creation |
Get attachments confluence_get_attachments | Retrieve attachments of a Confluence page |
Get audit logs confluence_get_audit_logs | Retrieve Confluence audit records |
Get blog posts for label confluence_get_blog_posts_for_label | List all blog posts under a specific label |
Get blogpost by ID confluence_get_blogpost_by_id | Retrieve a specific Confluence blog post by its ID |
Get blogpost labels confluence_get_blogpost_labels | Retrieve labels of a specific Confluence blog post by ID |
Get blogpost like count confluence_get_blogpost_like_count | Get like count for a Confluence blog post |
Get blogpost operations confluence_get_blogpost_operations | Retrieve permitted operations for a Confluence blog post |
Get blogpost version details confluence_get_blogpost_version_details | Retrieve details for a specific version of a blog post |
Get blogpost versions confluence_get_blogpost_versions | Retrieve all versions of a specific blog post |
Get child pages confluence_get_child_pages | List all direct child pages of a given Confluence page |
Get content properties for blog post confluence_get_content_properties_for_blog_post | Retrieve all content properties on a blog post |
Get content properties for page confluence_get_content_properties_for_page | Retrieve all content properties on a page |
Get content restrictions confluence_get_content_restrictions | Retrieve restrictions on a Confluence content item |
Get inline comments for blog post confluence_get_inline_comments_for_blog_post | Retrieve inline comments for a Confluence blog post |
Get labels confluence_get_labels | Retrieve all labels in a Confluence site; use for label discovery when you need to list or page |
Get labels for page confluence_get_labels_for_page | Retrieve labels of a specific Confluence page by ID |
Get labels for space confluence_get_labels_for_space | List labels on a space |
Try it: find the Confluence tool you need
Browse the 30 Confluence tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Search Confluence for what I need, summarize the results, and tell me the next best action.
Create it in Confluence for me, then confirm the important fields before you finish.
Create it in Confluence for me, then confirm the important fields before you finish.
Create it in Confluence for me, then confirm the important fields before you finish.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Confluence working from chat.
| Manual | ClawLink | |
|---|---|---|
| Connection flow | Register a Confluence app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Confluence through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Confluence. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Confluence actions to the runtime in a format your agent can reliably use. | 69 tools for Confluence are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Confluence to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Confluence in the browser, and the 69 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Confluence skill but can't call the tools
The ClawHub skill teaches OpenClaw about Confluence, but the calls run through the ClawLink plugin and your connected account. Make sure Confluence is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect Confluence from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Confluence tools
Confluence tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Confluence call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Confluence returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
OAuth finished in the browser but the account is still missing
Try reconnecting Confluence and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.
FAQ
Is there a OpenClaw Confluence integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Confluence: link your Confluence account once in the browser and OpenClaw can call the Confluence API through 69 ready-made tools — no custom code or token handling.
How do I add Confluence to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Confluence skill from ClawHub, then you click Connect in the dashboard to authorize Confluence. OpenClaw calls the tools from the next message — no config files or API keys to manage.
How long does it take to connect Confluence to OpenClaw?
About two minutes. Sign in, click Connect next to Confluence in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Confluence up myself?
The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Confluence working from chat.
OpenClaw installed the Confluence skill but can't call the tools
The ClawHub skill teaches OpenClaw about Confluence, but the calls run through the ClawLink plugin and your connected account. Make sure Confluence is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
