# How to connect Supportbee to OpenClaw (paste one key, 41 tools) > Connect Supportbee to OpenClaw with ClawLink: paste your Supportbee key once and 41 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/supportbee The usual route to Supportbee 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 Supportbee setup: install one ClawHub skill, connect Supportbee in the browser, and OpenClaw can call real Supportbee actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to Supportbee. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Supportbee** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw 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 supportbee # connect Supportbee (browser OAuth) npx -y @useclawlink/cli actions supportbee # list available actions npx -y @useclawlink/cli run supportbee --input '' # execute (add --confirm for writes) ``` ### 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: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then 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 Supportbee in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Supportbee API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Supportbee, summarize it in plain English, and point out anything that needs attention. ### 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: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Supportbee is connected in the dashboard, that agent calls the same 41 Supportbee 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). ## Supportbee MCP for OpenClaw Looking for a Supportbee MCP server for OpenClaw? ClawLink connects Supportbee to OpenClaw and exposes 41 Supportbee 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 Hermes instead? The [Hermes Supportbee integration](https://claw-link.dev/hermes/supportbee) works the same way. ## What the OpenClaw Supportbee integration can do 41 Supportbee 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 41. ### 30 of 41 Supportbee tools for OpenClaw | Tool | What it does | |---|---| | **Fetch emails** `supportbee_fetch_emails` | Retrieve all forwarding email addresses configured for the company | | **Fetch labels** `supportbee_fetch_labels` | Retrieve all custom labels | | **Fetch snippets** `supportbee_fetch_snippets` | Fetches saved response snippets (canned responses/templates) from SupportBee | | **Fetch teams** `supportbee_fetch_teams` | Retrieves all teams in the SupportBee account | | **Get avg first response time report** `supportbee_get_avg_first_response_time_report` | Retrieve average first response time data points over time | | **Get replies count report** `supportbee_get_replies_count_report` | Retrieves replies count report data for the company | | **Get ticket** `supportbee_get_ticket` | Retrieve a specific SupportBee ticket by its ID | | **Get tickets count report** `supportbee_get_tickets_count_report` | Get ticket count data points over time | | **List ticket comments** `supportbee_list_ticket_comments` | Retrieves all internal comments (private agent notes) for a specific ticket | | **List ticket replies** `supportbee_list_ticket_replies` | Lists all replies on a specific support ticket in SupportBee | | **List tickets** `supportbee_list_tickets` | List tickets from SupportBee | | **List users** `supportbee_list_users` | Retrieves all users and customer groups in your SupportBee company | | **Search tickets** `supportbee_search_tickets` | Search SupportBee tickets | | **Show ticket reply** `supportbee_show_ticket_reply` | Fetch a specific reply for a SupportBee ticket | | **Show user or customer group** `supportbee_show_user_or_customer_group` | Retrieves details of a SupportBee user (agent/admin) or customer group by their ID | | **Add label to ticket** `supportbee_add_label_to_ticket` | Add a label to a ticket | | **Archive ticket** `supportbee_archive_ticket` | Archive a SupportBee ticket by its ID | | **Assign ticket to team** `supportbee_assign_ticket_to_team` | Assigns a ticket to a team in SupportBee | | **Create comment** `supportbee_create_comment` | Creates an internal comment on a ticket in SupportBee | | **Create consequence** `supportbee_create_consequence` | Creates a new consequence for rules automation in SupportBee | | **Create email** `supportbee_create_email` | Create a new forwarding email address for the company in SupportBee | | **Create filter** `supportbee_create_filter` | Creates a filter in SupportBee by linking a rule with a consequence | | **Create rule** `supportbee_create_rule` | Creates a new automation rule in SupportBee to automatically process tickets based on conditions | | **Create snippet** `supportbee_create_snippet` | Create a reusable snippet (canned response) in SupportBee | | **Create ticket** `supportbee_create_ticket` | Creates a new support ticket in SupportBee with a subject, content, and requester details | | **Create ticket reply** `supportbee_create_ticket_reply` | Create a reply to a support ticket in SupportBee | | **Create user or customer group** `supportbee_create_user_or_customer_group` | Invites a new user to your SupportBee account | | **Mark ticket as answered** `supportbee_mark_ticket_as_answered` | Marks a SupportBee ticket as answered by adding the 'answered' status | | **Mark ticket as spam** `supportbee_mark_ticket_as_spam` | Mark a SupportBee ticket as spam | | **Unarchive ticket** `supportbee_unarchive_ticket` | Unarchive a SupportBee ticket by its ID | ## Example prompts **Fetch Emails** > Pull the relevant data from Supportbee, summarize it in plain English, and point out anything that needs attention. **Fetch Labels** > Pull the relevant data from Supportbee, summarize it in plain English, and point out anything that needs attention. **Fetch Snippets** > Pull the relevant data from Supportbee, summarize it in plain English, and point out anything that needs attention. **Fetch Teams** > Pull the relevant data from Supportbee, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key 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 Supportbee working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Supportbee API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Supportbee account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Supportbee. | 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 Supportbee actions to the runtime in a format your agent can reliably use. | 41 tools for Supportbee are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Supportbee 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 Supportbee in the browser, and the 41 tools above work from chat. There is no SDK and no config file, and the Supportbee key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Supportbee skill but can't call the tools The ClawHub skill teaches OpenClaw about Supportbee, but the calls run through the ClawLink plugin and your connected account. Make sure Supportbee 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 Supportbee 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 Supportbee tools Supportbee 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 Supportbee 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. ### Supportbee 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. ### API key setup works but results look incomplete Double-check that the API key for Supportbee has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Supportbee integration? Yes. ClawLink is the fastest way to connect OpenClaw to Supportbee: link your Supportbee account once in the browser and OpenClaw can call the Supportbee API through 41 ready-made tools — no custom code or token handling. ### How do I add Supportbee to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Supportbee skill from ClawHub, then you click Connect in the dashboard to authorize Supportbee. OpenClaw calls the tools from the next message — no config files, and the Supportbee key you paste is stored server-side instead of in your environment. ### How long does it take to connect Supportbee to OpenClaw? About two minutes. Sign in, click Connect next to Supportbee in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Supportbee up myself? The alternative to ClawLink is usually manual API key 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 Supportbee working from chat. ### OpenClaw installed the Supportbee skill but can't call the tools The ClawHub skill teaches OpenClaw about Supportbee, but the calls run through the ClawLink plugin and your connected account. Make sure Supportbee 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. ## Related - [OpenClaw ActiveCampaign integration](https://claw-link.dev/openclaw/activecampaign) — Marketing automation, CRM, and email marketing - [OpenClaw Benchmark Email integration](https://claw-link.dev/openclaw/benchmark-email) — Benchmark Email is a comprehensive email marketing platform offering tools for creating, sending, and analyzing email campaigns. - [Mailchimp](https://claw-link.dev/openclaw/mailchimp) — Create email campaigns and manage audiences