How to connect Slackbot to Hermes Agent
Connect Slackbot to Hermes with ClawLink in one click — 85 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup.
SlackbotOAUTH2MCPAutomate Slack workspace actions with bot-specific capabilities. Once connected, Hermes Agent can read and act on Slackbot from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent Slackbot 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 Slackbot setup: pair once in the browser and your always-on Hermes agent can act on Slackbot for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into Hermes to install the plugin and pair your account.
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. It prints an approval link, so show me the link and stop, don't wait:
hermes clawlink begin
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 Slackbot.
1Install and pair
Install the ClawLink plugin, then pair Hermes with a one-time browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable- 2
Connect Slackbot
One-click OAuth in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with Slackbot?"
Install by command
The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:
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 testThen connect Slackbot in the ClawLink dashboard — a one-click OAuth approval, no API keys.
Verify the connection by asking Hermes:
Use Slackbot to download file and walk me through the result in plain English.
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:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Slackbot is connected in the dashboard, that agent calls the same 85 Slackbot tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Slackbot MCP for Hermes
Looking for a Slackbot MCP server for Hermes Agent? ClawLink connects Slackbot to Hermes Agent and exposes 85 Slackbot tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Slackbot integration works the same way.
What the Hermes Agent Slackbot integration can do
85 Slackbot 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 85.
30 of 85 Slackbot tools for Hermes
| Tool | What it does |
|---|---|
Download file slackbot_download_file | Download Slack file content and convert it to a publicly accessible URL |
Fetch conversation history slackbot_fetch_conversation_history | Fetches a chronological list of messages and events from a specified Slack conversation |
Fetch item reactions slackbot_fetch_item_reactions | Fetches reactions for a Slack message, file, or file comment |
Fetch message thread from a conversation slackbot_fetch_message_thread_from_a_conversation | Retrieves replies to a specific parent message in a Slack conversation, using the channel ID |
Fetch team info slackbot_fetch_team_info | Fetches comprehensive metadata about the current Slack team, or a specified team if the |
Find channels slackbot_find_channels | Find channels in a Slack workspace by any criteria - name, topic, purpose, or description |
Find user by email address slackbot_find_user_by_email_address | Retrieves the Slack user object for an active user by their registered email address; requires |
Find users slackbot_find_users | Find users in a Slack workspace by any criteria - email, name, display name, or other text |
Get bot user slackbot_get_bot_user | Fetches information for a specified, existing Slack bot user; will not work for regular user |
Get call info slackbot_get_call_info | Retrieves a point-in-time snapshot of a specific Slack call's information |
Get reminder slackbot_get_reminder | Retrieves detailed information for an existing Slack reminder specified by its ID; this is a |
Get remote file slackbot_get_remote_file | Retrieve information about a remote file added to Slack via the files.remote API |
Get team profile slackbot_get_team_profile | Retrieves all profile field definitions for a Slack team, optionally filtered by visibility, to |
Get user dnd status slackbot_get_user_dnd_status | Retrieves a user's current Do Not Disturb status |
Get user presence slackbot_get_user_presence | Retrieves a Slack user's current real-time presence (e.g., 'active', 'away') to determine their |
List all channels slackbot_list_all_channels | Lists conversations available to the user with various filters and search options |
List all users slackbot_list_all_users | Retrieves a paginated list of all users with profile details, status, and team memberships in a |
List conversations slackbot_list_conversations | List conversations (channels/DMs) accessible to a specified user (or the authenticated user if |
List custom emojis slackbot_list_custom_emojis | Retrieves all custom emojis for the Slack workspace (image URLs or aliases), not standard |
List files with filters in slack slackbot_list_files_with_filters_in_slack | Lists files and their metadata within a Slack workspace, filterable by user, channel |
List pinned items slackbot_list_pinned_items | Retrieves all messages and files pinned to a specified channel; the caller must have access to |
List reminders slackbot_list_reminders | Lists all reminders with their details for the authenticated Slack user; returns an empty array |
List remote files slackbot_list_remote_files | Retrieve information about a team's remote files |
List user group members slackbot_list_user_group_members | Retrieves a list of all user IDs within a specified Slack user group, with an option to include |
List user groups slackbot_list_user_groups | Lists user groups in a Slack workspace, including user-created and default groups; results for |
List user reactions slackbot_list_user_reactions | Lists all reactions added by a specific user to messages, files, or file comments in Slack |
Lookup canvas sections slackbot_lookup_canvas_sections | Looks up section IDs in a Slack Canvas for use with targeted edit operations |
Retrieve conversation information slackbot_retrieve_conversation_information | Retrieves metadata for a Slack conversation by ID (e.g., name, purpose, creation date, with |
Retrieve conversation members list slackbot_retrieve_conversation_members_list | Retrieves a paginated list of active member IDs (not names, emails, or presence) for a |
Retrieve current user dnd status slackbot_retrieve_current_user_dnd_status | Retrieves a Slack user's current Do Not Disturb (DND) status to determine their availability |
Try it: find the Slackbot tool you need
Browse the 30 Slackbot tools
Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.
Example prompts
Use Slackbot to download file and walk me through the result in plain English.
Pull the relevant data from Slackbot, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Slackbot, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Slackbot, summarize it in plain English, and point out anything that needs attention.
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 Slackbot working from chat.
| Manual | ClawLink | |
|---|---|---|
| Connection flow | Register a Slackbot app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Slackbot 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 Slackbot. | 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 Slackbot actions to the runtime in a format your agent can reliably use. | 85 tools for Slackbot are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Slackbot 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 Slackbot in the browser, and the 85 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
Hermes paired but still can't use Slackbot
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 Slackbot 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 Slackbot tools
Slackbot 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 Slackbot 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.
Slackbot 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 Slackbot 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 Hermes Agent Slackbot integration?
Yes. ClawLink is the fastest way to connect Hermes to Slackbot: link your Slackbot account once in the browser and Hermes Agent can call the Slackbot API through 85 ready-made tools — no custom code or token handling.
How do I connect Slackbot 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 Slackbot 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 Slackbot to Hermes Agent?
About two minutes. Sign in, click Connect next to Slackbot in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.
Why use ClawLink instead of wiring Slackbot 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 Slackbot working from chat.
Hermes paired but still can't use Slackbot
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.
