# How to connect Spondyr to OpenClaw (paste one key, 21 tools) > Connect Spondyr to OpenClaw with ClawLink: paste your Spondyr key once and 21 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/spondyr The usual route to Spondyr 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 Spondyr setup: install one ClawHub skill, connect Spondyr in the browser, and OpenClaw can call real Spondyr 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 Spondyr. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Spondyr** — 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 spondyr # connect Spondyr (browser OAuth) npx -y @useclawlink/cli actions spondyr # list available actions npx -y @useclawlink/cli run spondyr --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 Spondyr in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Spondyr API key once. Verify the connection by asking OpenClaw: > Use Spondyr to conditions list 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 Spondyr is connected in the dashboard, that agent calls the same 21 Spondyr 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). ## Spondyr MCP for OpenClaw Looking for a Spondyr MCP server for OpenClaw? ClawLink connects Spondyr to OpenClaw and exposes 21 Spondyr 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 Spondyr integration](https://claw-link.dev/hermes/spondyr) works the same way. ## What the OpenClaw Spondyr integration can do 21 Spondyr tools are ready for OpenClaw once the account is connected. The 19 below are the ones people reach for most; your agent can call all 21. ### 19 of 21 Spondyr tools for OpenClaw | Tool | What it does | |---|---| | **Conditions list** `spondyr_conditions_list` | List all conditions for a transaction type | | **Get event types** `spondyr_get_event_types` | Retrieves all event types associated with a specific transaction type in Spondyr | | **Get spondyr status** `spondyr_get_spondyr_status` | Retrieve the status of a previously generated correspondence | | **Get transaction types** `spondyr_get_transaction_types` | Retrieve a list of available transaction types | | **Recipient get** `spondyr_recipient_get` | Retrieve details of a specific recipient | | **Recipients list** `spondyr_recipients_list` | List all recipients for a transaction type | | **Search filter get** `spondyr_search_filter_get` | Retrieves details of a specific search filter in Spondyr by name and transaction type | | **Search filters list** `spondyr_search_filters_list` | List all search filters for a transaction type | | **Search spondyrs** `spondyr_search_spondyrs` | Search for generated correspondence (spondyrs) by multiple criteria including batch ID, event | | **Template get** `spondyr_template_get` | Retrieve detailed configuration for a specific correspondence template | | **Templates list** `spondyr_templates_list` | List all templates configured for a transaction type | | **Transaction type get** `spondyr_transaction_type_get` | Retrieve details of a specific transaction type | | **Create condition** `spondyr_create_condition` | Create a condition rule for template selection in Spondyr | | **Create transaction type** `spondyr_create_transaction_type` | Create a new transaction type | | **Deliver spondyr** `spondyr_deliver_spondyr` | Trigger delivery of previously generated correspondence to recipients | | **Event type update** `spondyr_event_type_update` | Update an existing event type name within a transaction type | | **Search filter create** `spondyr_search_filter_create` | Create a new search filter for a transaction type in Spondyr | | **Sso stub** `spondyr_sso_stub` | Create a one-time SSO user stub in Spondyr | | **Transaction type update** `spondyr_transaction_type_update` | Updates an existing transaction type's name and/or JSON schema in Spondyr | ## Example prompts **Conditions List** > Use Spondyr to conditions list and walk me through the result in plain English. **Get Event Types** > Pull the relevant data from Spondyr, summarize it in plain English, and point out anything that needs attention. **Get Spondyr Status** > Pull the relevant data from Spondyr, summarize it in plain English, and point out anything that needs attention. **Get Transaction Types** > Pull the relevant data from Spondyr, 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 Spondyr working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Spondyr API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Spondyr 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 Spondyr. | 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 Spondyr actions to the runtime in a format your agent can reliably use. | 21 tools for Spondyr are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Spondyr 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 Spondyr in the browser, and the 21 tools above work from chat. There is no SDK and no config file, and the Spondyr 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 Spondyr skill but can't call the tools The ClawHub skill teaches OpenClaw about Spondyr, but the calls run through the ClawLink plugin and your connected account. Make sure Spondyr 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 Spondyr 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 Spondyr tools Spondyr 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 Spondyr 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. ### Spondyr 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 Spondyr has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Spondyr integration? Yes. ClawLink is the fastest way to connect OpenClaw to Spondyr: link your Spondyr account once in the browser and OpenClaw can call the Spondyr API through 21 ready-made tools — no custom code or token handling. ### How do I add Spondyr to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Spondyr skill from ClawHub, then you click Connect in the dashboard to authorize Spondyr. OpenClaw calls the tools from the next message — no config files, and the Spondyr key you paste is stored server-side instead of in your environment. ### How long does it take to connect Spondyr to OpenClaw? About two minutes. Sign in, click Connect next to Spondyr in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Spondyr 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 Spondyr working from chat. ### OpenClaw installed the Spondyr skill but can't call the tools The ClawHub skill teaches OpenClaw about Spondyr, but the calls run through the ClawLink plugin and your connected account. Make sure Spondyr 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 - [Benchmark Email tools](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