# How to connect Sendspark to OpenClaw (paste one key, 9 tools) > Connect Sendspark to OpenClaw with ClawLink: paste your Sendspark key once and 9 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/sendspark The usual route to Sendspark 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 Sendspark setup: install one ClawHub skill, connect Sendspark in the browser, and OpenClaw can call real Sendspark 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 Sendspark. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Sendspark** — 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 sendspark # connect Sendspark (browser OAuth) npx -y @useclawlink/cli actions sendspark # list available actions npx -y @useclawlink/cli run sendspark --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 Sendspark in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Sendspark API key once. Verify the connection by asking OpenClaw: > Use Sendspark to api health status and walk me through the result in plain English. ### 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 Sendspark is connected in the dashboard, that agent calls the same 9 Sendspark 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). ## Sendspark MCP for OpenClaw Looking for a Sendspark MCP server for OpenClaw? ClawLink connects Sendspark to OpenClaw and exposes 9 Sendspark 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 Sendspark integration](https://claw-link.dev/hermes/sendspark) works the same way. ## What the OpenClaw Sendspark integration can do 9 Sendspark tools are ready for OpenClaw once the account is connected. The 8 below are the ones people reach for most; your agent can call all 9. ### 8 of 9 Sendspark tools for OpenClaw | Tool | What it does | |---|---| | **API health status** `sendspark_api_health_status` | Check the health status of the Sendspark API | | **Get dynamic campaign by ID** `sendspark_get_dynamic_campaign_by_id` | Retrieve details of a specific dynamic video campaign | | **Get workspace prospect data by email** `sendspark_get_workspace_prospect_data_by_email` | Retrieve prospect data by email in a dynamic campaign | | **List dynamic video campaigns** `sendspark_list_dynamic_video_campaigns` | List all dynamic video campaigns in a workspace | | **List webhooks** `sendspark_list_webhooks` | Retrieves all configured webhooks for a Sendspark workspace | | **Add multiple prospects to dynamic campaign** `sendspark_add_multiple_prospects_to_dynamic_campaign` | Add multiple prospects to a dynamic campaign in bulk | | **Add prospect to dynamic video campaign** `sendspark_add_prospect_to_dynamic_video_campaign` | Add a prospect to a dynamic video campaign | | **Create dynamic video campaign2** `sendspark_create_dynamic_video_campaign2` | Create a dynamic video campaign in a workspace | ## Example prompts **Api Health Status** > Use Sendspark to api health status and walk me through the result in plain English. **Get Dynamic Campaign By Id** > Pull the relevant data from Sendspark, summarize it in plain English, and point out anything that needs attention. **Get Workspace Prospect Data By Email** > Pull the relevant data from Sendspark, summarize it in plain English, and point out anything that needs attention. **List Dynamic Video Campaigns** > List the relevant items in Sendspark, group them by priority, and recommend what OpenClaw should do next. ## 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 Sendspark working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Sendspark API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Sendspark 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 Sendspark. | 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 Sendspark actions to the runtime in a format your agent can reliably use. | 9 tools for Sendspark are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Sendspark 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 Sendspark in the browser, and the 9 tools above work from chat. There is no SDK and no config file, and the Sendspark 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 Sendspark skill but can't call the tools The ClawHub skill teaches OpenClaw about Sendspark, but the calls run through the ClawLink plugin and your connected account. Make sure Sendspark 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 Sendspark 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 Sendspark tools Sendspark 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 Sendspark 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. ### Sendspark 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 Sendspark has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Sendspark integration? Yes. ClawLink is the fastest way to connect OpenClaw to Sendspark: link your Sendspark account once in the browser and OpenClaw can call the Sendspark API through 9 ready-made tools — no custom code or token handling. ### How do I add Sendspark to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Sendspark skill from ClawHub, then you click Connect in the dashboard to authorize Sendspark. OpenClaw calls the tools from the next message — no config files, and the Sendspark key you paste is stored server-side instead of in your environment. ### How long does it take to connect Sendspark to OpenClaw? About two minutes. Sign in, click Connect next to Sendspark in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Sendspark 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 Sendspark working from chat. ### OpenClaw installed the Sendspark skill but can't call the tools The ClawHub skill teaches OpenClaw about Sendspark, but the calls run through the ClawLink plugin and your connected account. Make sure Sendspark 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 - [ActiveCampaign tools](https://claw-link.dev/openclaw/activecampaign) — Marketing automation, CRM, and email marketing - [Connect Benchmark Email](https://claw-link.dev/openclaw/benchmark-email) — Benchmark Email is a comprehensive email marketing platform offering tools for creating, sending, and analyzing email campaigns. - [Connect Mailchimp](https://claw-link.dev/openclaw/mailchimp) — Create email campaigns and manage audiences