# How to connect Unisender to OpenClaw (paste one key, 33 tools) > Connect Unisender to OpenClaw with ClawLink: paste your Unisender key once and 33 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/unisender The usual route to Unisender 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 Unisender setup: install one ClawHub skill, connect Unisender in the browser, and OpenClaw can call real Unisender 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 Unisender. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Unisender** — 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 unisender # connect Unisender (browser OAuth) npx -y @useclawlink/cli actions unisender # list available actions npx -y @useclawlink/cli run unisender --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 Unisender in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Unisender API key once. Verify the connection by asking OpenClaw: > Use Unisender to check email 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 Unisender is connected in the dashboard, that agent calls the same 33 Unisender 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). ## Unisender MCP for OpenClaw Looking for a Unisender MCP server for OpenClaw? ClawLink connects Unisender to OpenClaw and exposes 33 Unisender 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 Unisender integration](https://claw-link.dev/hermes/unisender) works the same way. ## What the OpenClaw Unisender integration can do 33 Unisender tools are ready for OpenClaw once the account is connected. The 28 below are the ones people reach for most; your agent can call all 33. ### 28 of 33 Unisender tools for OpenClaw | Tool | What it does | |---|---| | **Check email** `unisender_check_email` | Check the delivery status of emails sent via sendEmail method | | **Export contacts** `unisender_export_contacts` | Export contact data from UniSender lists for synchronization | | **Get campaign status** `unisender_get_campaign_status` | Check the current status of a campaign in UniSender | | **Get campaigns** `unisender_get_campaigns` | Retrieve list of campaigns from Unisender within a specified date range | | **Get contact** `unisender_get_contact` | Get information about a single contact from UniSender | | **Get contact field values** `unisender_get_contact_field_values` | Retrieve custom field values for a specific contact identified by email address | | **Get fields** `unisender_get_fields` | Retrieve all custom user-defined fields for contact personalization and data management | | **Get lists** `unisender_get_lists` | Retrieve all existing mailing lists associated with the account | | **Get messages** `unisender_get_messages` | Retrieve list of all messages with body and attachments | | **Get sender domain list** `unisender_get_sender_domain_list` | Retrieve information about sender domains and their DKIM status | | **Get tags** `unisender_get_tags` | Retrieve all custom tags/labels for contact segmentation | | **Get template** `unisender_get_template` | Retrieve detailed information about a specific email template by its ID | | **Get templates** `unisender_get_templates` | Retrieve list of all templates with full content including body | | **Is contact in lists** `unisender_is_contact_in_lists` | Check if a contact exists in specified mailing lists based on and/or conditions | | **List messages** `unisender_list_messages` | List all messages without body and attachments | | **List templates** `unisender_list_templates` | List email templates without body content | | **Create email template** `unisender_create_email_template` | Create a new email template for mass campaigns in UniSender | | **Create field** `unisender_create_field` | Create a new custom field for contact data in UniSender | | **Create list** `unisender_create_list` | Create a new contact list for organizing thematic email campaigns in UniSender | | **Create subscriber note** `unisender_create_subscriber_note` | Create a note for a subscriber contact in UniSender | | **Exclude** `unisender_exclude` | Remove contacts from specified lists or all lists in UniSender | | **Import contacts** `unisender_import_contacts` | Bulk import contacts to UniSender with maximum 500 contacts per call | | **Subscribe** `unisender_subscribe` | Add contacts to one or multiple mailing lists with optional tags and field values | | **Unsubscribe** `unisender_unsubscribe` | Unsubscribe contacts from mailing lists in UniSender | | **Update email template** `unisender_update_email_template` | Update an existing email template for mass campaigns | | **Update field** `unisender_update_field` | Modify parameters of an existing custom field in UniSender | | **Update list** `unisender_update_list` | Update the parameters of an existing contact list in UniSender | | **Update subscriber note** `unisender_update_subscriber_note` | Update the content of an existing subscriber note in UniSender | ## Example prompts **Check Email** > Use Unisender to check email and walk me through the result in plain English. **Export Contacts** > Use Unisender to export contacts and walk me through the result in plain English. **Get Campaign Status** > Pull the relevant data from Unisender, summarize it in plain English, and point out anything that needs attention. **Get Campaigns** > Pull the relevant data from Unisender, 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 Unisender working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Unisender API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Unisender 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 Unisender. | 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 Unisender actions to the runtime in a format your agent can reliably use. | 33 tools for Unisender are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Unisender 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 Unisender in the browser, and the 33 tools above work from chat. There is no SDK and no config file, and the Unisender 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 Unisender skill but can't call the tools The ClawHub skill teaches OpenClaw about Unisender, but the calls run through the ClawLink plugin and your connected account. Make sure Unisender 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 Unisender 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 Unisender tools Unisender 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 Unisender 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. ### Unisender 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 Unisender has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Unisender integration? Yes. ClawLink is the fastest way to connect OpenClaw to Unisender: link your Unisender account once in the browser and OpenClaw can call the Unisender API through 33 ready-made tools — no custom code or token handling. ### How do I add Unisender to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Unisender skill from ClawHub, then you click Connect in the dashboard to authorize Unisender. OpenClaw calls the tools from the next message — no config files, and the Unisender key you paste is stored server-side instead of in your environment. ### How long does it take to connect Unisender to OpenClaw? About two minutes. Sign in, click Connect next to Unisender in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Unisender 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 Unisender working from chat. ### OpenClaw installed the Unisender skill but can't call the tools The ClawHub skill teaches OpenClaw about Unisender, but the calls run through the ClawLink plugin and your connected account. Make sure Unisender 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