# How to connect Blooio to OpenClaw (paste one key, 26 tools) > Connect Blooio to OpenClaw with ClawLink: paste your Blooio key once and 26 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/blooio The usual route to Blooio 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 Blooio setup: install one ClawHub skill, connect Blooio in the browser, and OpenClaw can call real Blooio 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 Blooio. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Blooio** — 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 blooio # connect Blooio (browser OAuth) npx -y @useclawlink/cli actions blooio # list available actions npx -y @useclawlink/cli run blooio --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 Blooio in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Blooio API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Blooio, 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 Blooio is connected in the dashboard, that agent calls the same 26 Blooio 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). ## Blooio MCP for OpenClaw Looking for a Blooio MCP server for OpenClaw? ClawLink connects Blooio to OpenClaw and exposes 26 Blooio 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 Blooio integration](https://claw-link.dev/hermes/blooio) works the same way. ## What the OpenClaw Blooio integration can do 26 Blooio tools are ready for OpenClaw once the account is connected. The 24 below are the ones people reach for most; your agent can call all 26. ### 24 of 26 Blooio tools for OpenClaw | Tool | What it does | |---|---| | **Get account** `blooio_get_account` | Return the authenticated organization, assigned devices, and message usage without exposing the | | **Get chat** `blooio_get_chat` | Return detailed counts, participant context, and latest-message metadata for one conversation | | **Get contact** `blooio_get_contact` | Return one contact by E.164 phone number or email, including its current tags | | **Get contact capabilities** `blooio_get_contact_capabilities` | Check whether a contact can receive iMessage, SMS, or FaceTime before choosing a communication | | **Get group** `blooio_get_group` | Return one messaging group by its grp_ identifier | | **Get message** `blooio_get_message` | Return one message with content, reactions, delivery status, protocol, errors, and inline-reply | | **Get poll results** `blooio_get_poll_results` | Return a poll's definition, option vote counts, and total votes | | **Get risk summary** `blooio_get_risk_summary` | Return the cached fleet risk rollup | | **List chats** `blooio_list_chats` | Search and page through conversations, ordered by recent activity or oldest activity | | **List contacts** `blooio_list_contacts` | Search and page through organization contacts by identifier or name | | **List group members** `blooio_list_group_members` | Page through the members recorded for a messaging group | | **List groups** `blooio_list_groups` | Search and page through messaging groups by name | | **List messages** `blooio_list_messages` | Page through messages in one chat with direction, time-window, and ordering filters | | **List numbers** `blooio_list_numbers` | List sender phone numbers assigned to the connected API key and their availability state | | **Add contact tags** `blooio_add_contact_tags` | Add or reactivate one or more free-form tags on a contact | | **Create contact** `blooio_create_contact` | Create a contact from an E.164 phone number or email address, optionally assigning a name | | **Create group** `blooio_create_group` | Create a messaging group, optionally linking an existing iMessage chat and recording its | | **Set message reaction** `blooio_set_message_reaction` | Add or remove a classic tapback or emoji reaction on a specific or relative message in a chat | | **Update contact** `blooio_update_contact` | Set or clear the display name of an existing contact | | **Update group** `blooio_update_group` | Rename a group and, when linked, synchronize the new name to its iMessage chat | | **Mark chat read** `blooio_mark_chat_read` | Mark every message in a chat as read and irreversibly send an externally visible read receipt | | **Remove contact tags** `blooio_remove_contact_tags` | Soft-delete one or more exact tags from a contact sequentially; if a later removal fails | | **Send message** `blooio_send_message` | Irreversibly send one or multiple text, attachment, multipart, or inline-reply messages | | **Send poll** `blooio_send_poll` | Irreversibly send an interactive native iMessage poll to a chat | ## Example prompts **Get Account** > Pull the relevant data from Blooio, summarize it in plain English, and point out anything that needs attention. **Get Chat** > Pull the relevant data from Blooio, summarize it in plain English, and point out anything that needs attention. **Get Contact** > Pull the relevant data from Blooio, summarize it in plain English, and point out anything that needs attention. **Get Contact Capabilities** > Pull the relevant data from Blooio, 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 Blooio working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Blooio API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Blooio 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 Blooio. | 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 Blooio actions to the runtime in a format your agent can reliably use. | 26 tools for Blooio are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Blooio 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 Blooio in the browser, and the 26 tools above work from chat. There is no SDK and no config file, and the Blooio 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 Blooio skill but can't call the tools The ClawHub skill teaches OpenClaw about Blooio, but the calls run through the ClawLink plugin and your connected account. Make sure Blooio 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 Blooio 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 Blooio tools Blooio 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 Blooio 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. ### Blooio 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 Blooio has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Blooio integration? Yes. ClawLink is the fastest way to connect OpenClaw to Blooio: link your Blooio account once in the browser and OpenClaw can call the Blooio API through 26 ready-made tools — no custom code or token handling. ### How do I add Blooio to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Blooio skill from ClawHub, then you click Connect in the dashboard to authorize Blooio. OpenClaw calls the tools from the next message — no config files, and the Blooio key you paste is stored server-side instead of in your environment. ### How long does it take to connect Blooio to OpenClaw? About two minutes. Sign in, click Connect next to Blooio in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Blooio 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 Blooio working from chat. ### OpenClaw installed the Blooio skill but can't call the tools The ClawHub skill teaches OpenClaw about Blooio, but the calls run through the ClawLink plugin and your connected account. Make sure Blooio 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 SendGrid integration](https://claw-link.dev/openclaw/sendgrid) — Deliver transactional and marketing emails - [Connect Dialpad](https://claw-link.dev/openclaw/dialpad) — Business phone, messaging, and video conferencing - [OpenClaw Discord Bot integration](https://claw-link.dev/openclaw/discord-bot) — Automate Discord server actions with bot-specific permissions