# How to connect Sendfox to OpenClaw (paste one key, 17 tools) > Connect Sendfox to OpenClaw with ClawLink: paste your Sendfox key once and 17 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/sendfox The usual route to Sendfox 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 Sendfox setup: install one ClawHub skill, connect Sendfox in the browser, and OpenClaw can call real Sendfox 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 Sendfox. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Sendfox** — 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 sendfox # connect Sendfox (browser OAuth) npx -y @useclawlink/cli actions sendfox # list available actions npx -y @useclawlink/cli run sendfox --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 Sendfox in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Sendfox API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Sendfox, 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 Sendfox is connected in the dashboard, that agent calls the same 17 Sendfox 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). ## Sendfox MCP for OpenClaw Looking for a Sendfox MCP server for OpenClaw? ClawLink connects Sendfox to OpenClaw and exposes 17 Sendfox 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 Sendfox integration](https://claw-link.dev/hermes/sendfox) works the same way. ## What the OpenClaw Sendfox integration can do 17 Sendfox tools are ready for OpenClaw once the account is connected. The 16 below are the ones people reach for most; your agent can call all 17. ### 16 of 17 Sendfox tools for OpenClaw | Tool | What it does | |---|---| | **Get automations** `sendfox_get_automations` | Retrieve a list of automations | | **Get campaign by ID** `sendfox_get_campaign_by_id` | Retrieve details for a specific campaign by its ID from SendFox | | **Get campaigns** `sendfox_get_campaigns` | Retrieve a paginated list of email campaigns from SendFox | | **Get contact by ID** `sendfox_get_contact_by_id` | Retrieves a contact's details by their unique ID from SendFox | | **Get contact fields** `sendfox_get_contact_fields` | Retrieves all contact fields available in the SendFox account | | **Get contacts** `sendfox_get_contacts` | Retrieve a paginated list of contacts | | **Get contacts in list** `sendfox_get_contacts_in_list` | Retrieve contacts in a specific list | | **Get current user** `sendfox_get_current_user` | Retrieve information about the authenticated user from SendFox | | **Get forms** `sendfox_get_forms` | Retrieve a paginated list of forms from SendFox | | **Get list by ID** `sendfox_get_list_by_id` | Retrieves details of a specific contact list by its ID from SendFox | | **Get lists** `sendfox_get_lists` | Retrieve all contact lists from your SendFox account with pagination support | | **List contact fields** `sendfox_list_contact_fields` | List all custom contact fields defined by the user | | **List unsubscribed contacts** `sendfox_list_unsubscribed_contacts` | Retrieve a paginated list of contacts who have unsubscribed | | **Post create contact** `sendfox_post_create_contact` | Create a new contact (subscriber) in your SendFox account | | **Post create list** `sendfox_post_create_list` | Create a new contact list in your SendFox account | | **Patch unsubscribe contact** `sendfox_patch_unsubscribe_contact` | Unsubscribe a contact from all email communications in your SendFox account | ## Example prompts **Get Automations** > Pull the relevant data from Sendfox, summarize it in plain English, and point out anything that needs attention. **Get Campaign By Id** > Pull the relevant data from Sendfox, summarize it in plain English, and point out anything that needs attention. **Get Campaigns** > Pull the relevant data from Sendfox, summarize it in plain English, and point out anything that needs attention. **Get Contact By Id** > Pull the relevant data from Sendfox, 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 Sendfox working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Sendfox API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Sendfox 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 Sendfox. | 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 Sendfox actions to the runtime in a format your agent can reliably use. | 17 tools for Sendfox are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Sendfox 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 Sendfox in the browser, and the 17 tools above work from chat. There is no SDK and no config file, and the Sendfox 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 Sendfox skill but can't call the tools The ClawHub skill teaches OpenClaw about Sendfox, but the calls run through the ClawLink plugin and your connected account. Make sure Sendfox 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 Sendfox 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 Sendfox tools Sendfox 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 Sendfox 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. ### Sendfox 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 Sendfox has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Sendfox integration? Yes. ClawLink is the fastest way to connect OpenClaw to Sendfox: link your Sendfox account once in the browser and OpenClaw can call the Sendfox API through 17 ready-made tools — no custom code or token handling. ### How do I add Sendfox to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Sendfox skill from ClawHub, then you click Connect in the dashboard to authorize Sendfox. OpenClaw calls the tools from the next message — no config files, and the Sendfox key you paste is stored server-side instead of in your environment. ### How long does it take to connect Sendfox to OpenClaw? About two minutes. Sign in, click Connect next to Sendfox in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Sendfox 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 Sendfox working from chat. ### OpenClaw installed the Sendfox skill but can't call the tools The ClawHub skill teaches OpenClaw about Sendfox, but the calls run through the ClawLink plugin and your connected account. Make sure Sendfox 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 - [Connect ActiveCampaign](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. - [OpenClaw Mailchimp integration](https://claw-link.dev/openclaw/mailchimp) — Create email campaigns and manage audiences