# How to connect Confluence to Hermes Agent (no API keys) > Connect Confluence to Hermes with ClawLink in one click — 69 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup. Web version: https://claw-link.dev/hermes/confluence Most guides for giving Hermes Agent Confluence access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical Confluence setup: pair once in the browser and your always-on Hermes agent can act on Confluence for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself. **Start here — paste this into Hermes to set up ClawLink:** > Set up ClawLink for Hermes and tell me when it's ready. > 1. Install the plugin: `hermes plugins install ClawLink-HQ/hermes-plugin --enable` > 2. Start pairing with `hermes clawlink begin`. It prints an approval link, so show me the link and stop, don't wait. > 3. I'll approve it in my browser, then reply "approved". > 4. When I say approved, finish setup: `hermes clawlink finish` > 5. Then run `hermes clawlink test` and tell me whether ClawLink is ready. ## Setup It takes three steps to connect Hermes to Confluence. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Confluence** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask Hermes Agent in plain English. **Alternative for any agent (no plugin needed):** if the Hermes Agent plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect confluence # connect Confluence (browser OAuth) npx -y @useclawlink/cli actions confluence # list available actions npx -y @useclawlink/cli run confluence --input '' # execute (add --confirm for writes) ``` ### Install by command The prompt above walks Hermes through this. By hand, it is four commands and a browser approval: ```bash hermes plugins install ClawLink-HQ/hermes-plugin --enable hermes clawlink begin # prints an approval link — open it and approve hermes clawlink finish # after approving in the browser hermes clawlink test ``` Then connect Confluence in the [ClawLink dashboard](https://claw-link.dev/dashboard) — a one-click OAuth approval, no API keys. Verify the connection by asking Hermes: > Search Confluence for what I need, summarize the results, and tell me the next best action. ### Using a different agent? The Hermes 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: ```bash npx -y @useclawlink/cli login ``` `login` 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](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Confluence MCP for Hermes Looking for a Confluence MCP server for Hermes Agent? ClawLink connects Confluence to Hermes Agent and exposes 69 Confluence tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using OpenClaw instead? The [OpenClaw Confluence integration](https://claw-link.dev/openclaw/confluence) works the same way. ## What the Hermes Agent Confluence integration can do 69 Confluence tools are ready for Hermes Agent 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 Hermes | 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 | ## Example prompts **Cql Search** > Search Confluence for what I need, summarize the results, and tell me the next best action. **Create Blogpost** > Create it in Confluence for me, then confirm the important fields before you finish. **Create Page** > Create it in Confluence for me, then confirm the important fields before you finish. **Create Space** > 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 Hermes Agent. 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 Hermes Agent 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](https://claw-link.dev/hub/composio-alternatives) comparison. ### Hermes paired but still can't use Confluence Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`. ### 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. ### Is there a Hermes Agent Confluence integration? Yes. ClawLink is the fastest way to connect Hermes to Confluence: link your Confluence account once in the browser and Hermes Agent can call the Confluence API through 69 ready-made tools — no custom code or token handling. ### How do I connect Confluence to Hermes with ClawLink? Install the plugin with `hermes plugins install ClawLink-HQ/hermes-plugin --enable`, then pair once: run `hermes clawlink begin`, approve the link in your browser, and run `hermes clawlink finish`. Connect Confluence in the dashboard and Hermes can use it from the next message — no config files or API keys to manage. ### How long does it take to connect Confluence to Hermes Agent? About two minutes. Sign in, click Connect next to Confluence in the dashboard, authenticate, and Hermes Agent 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Confluence working from chat. ### Hermes paired but still can't use Confluence Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`. ## Related - [DocuSign tools](https://claw-link.dev/hermes/docusign) — Send, sign, and manage agreements and envelopes - [Trello tools](https://claw-link.dev/hermes/trello) — Manage boards, lists, and cards - [Moco](https://claw-link.dev/hermes/moco) — MOCO is a business management software offering project management, time tracking, and invoicing solutions.