# How to connect ClickSend to OpenClaw (paste one key, 166 tools) > Connect ClickSend to OpenClaw with ClawLink: paste your ClickSend key once and 166 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/clicksend The usual route to ClickSend 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 ClickSend setup: install one ClawHub skill, connect ClickSend in the browser, and OpenClaw can call real ClickSend 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 ClickSend. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect ClickSend** — 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 clicksend # connect ClickSend (browser OAuth) npx -y @useclawlink/cli actions clicksend # list available actions npx -y @useclawlink/cli run clicksend --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 ClickSend in the [ClawLink dashboard](https://claw-link.dev/dashboard) — enter your ClickSend account details once. Verify the connection by asking OpenClaw: > Use ClickSend to account useage by subaccount get 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 ClickSend is connected in the dashboard, that agent calls the same 166 ClickSend 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). ## ClickSend MCP for OpenClaw Looking for a ClickSend MCP server for OpenClaw? ClawLink connects ClickSend to OpenClaw and exposes 166 ClickSend 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 ClickSend integration](https://claw-link.dev/hermes/clicksend) works the same way. ## What the OpenClaw ClickSend integration can do 166 ClickSend tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 166. ### 30 of 166 ClickSend tools for OpenClaw | Tool | What it does | |---|---| | **Account useage by subaccount get** `clicksend_account_useage_by_subaccount_get` | Retrieve detailed account usage statistics grouped by subaccount for a specific month and year | | **Calculate post letters price** `clicksend_calculate_post_letters_price` | Calculate the price for sending physical post letters via ClickSend without actually sending | | **Calculate sms campaigns price** `clicksend_calculate_sms_campaigns_price` | Calculate the price for an SMS campaign before sending | | **Create email addresses6** `clicksend_create_email_addresses6` | Retrieve list of allowed email addresses for sending transactional emails | | **Create post letters detect address** `clicksend_create_post_letters_detect_address` | Detect and convert addresses to standard format from PDF or address string | | **Create post return addresses3** `clicksend_create_post_return_addresses3` | Retrieve a list of all post return addresses from ClickSend account with pagination | | **Create sms email sms3** `clicksend_create_sms_email_sms3` | Retrieve a specific allowed email address for SMS email-to-SMS by its ID | | **Email campaign get** `clicksend_email_campaign_get` | Retrieve details of a specific email campaign by its ID | | **Email delivery receipt automation get** `clicksend_email_delivery_receipt_automation_get` | Retrieves the configuration details of a specific email delivery receipt automation rule by its | | **Email template get** `clicksend_email_template_get` | Retrieve a specific user email template by its template ID | | **Export post letters history export** `clicksend_export_post_letters_history_export` | Export post letter history to a downloadable CSV file | | **Fax delivery receipt automation get** `clicksend_fax_delivery_receipt_automation_get` | Retrieve a specific fax delivery receipt automation rule by its ID | | **Fax receipts by message ID get** `clicksend_fax_receipts_by_message_id_get` | Retrieve a single fax delivery receipt using the message identifier | | **Get account** `clicksend_get_account` | Retrieve authenticated user's account information | | **Get automations email receipts** `clicksend_get_automations_email_receipts` | Retrieve all email delivery receipt automation rules configured in your ClickSend account | | **Get automations fax inbound** `clicksend_get_automations_fax_inbound` | Retrieve all inbound fax automation rules configured in your ClickSend account | | **Get automations fax receipts** `clicksend_get_automations_fax_receipts` | Retrieve all fax delivery receipt automation rules configured in your ClickSend account | | **Get automations sms inbound** `clicksend_get_automations_sms_inbound` | Retrieve all inbound SMS automation rules configured in your ClickSend account | | **Get automations sms receipts** `clicksend_get_automations_sms_receipts` | Retrieve all SMS delivery receipt automation rules configured in your ClickSend account | | **Get automations voice receipts** `clicksend_get_automations_voice_receipts` | Retrieve all voice delivery receipt automation rules configured in your ClickSend account | | **Get contact suggestions** `clicksend_get_contact_suggestions` | Retrieves contact suggestions from your ClickSend account based on recent messaging activity | | **Get countries** `clicksend_get_countries` | Retrieve all available country codes that ClickSend supports | | **Get delivery issues** `clicksend_get_delivery_issues` | Retrieve all delivery issues from your ClickSend account | | **Get email master templates** `clicksend_get_email_master_templates` | Retrieve all master email templates | | **Get email master templates categories** `clicksend_get_email_master_templates_categories` | Retrieve all master email template categories | | **Get email templates** `clicksend_get_email_templates` | Retrieve all user email templates | | **Get fax receipts** `clicksend_get_fax_receipts` | Retrieve fax delivery receipts from your ClickSend account | | **Get lists** `clicksend_get_lists` | Retrieve all contact lists from ClickSend account with pagination support | | **Get lists contacts** `clicksend_get_lists_contacts` | Retrieve all contacts from a specific contact list in your ClickSend account with pagination | | **Get lists contacts2** `clicksend_get_lists_contacts2` | Retrieve a specific contact from a contact list in your ClickSend account | ## Example prompts **Account Useage By Subaccount Get** > Use ClickSend to account useage by subaccount get and walk me through the result in plain English. **Calculate Post Letters Price** > Use ClickSend to calculate post letters price and walk me through the result in plain English. **Calculate Sms Campaigns Price** > Use ClickSend to calculate sms campaigns price and walk me through the result in plain English. **Create Email Addresses6** > Create it in ClickSend for me, then confirm the important fields before you finish. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual credential 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 ClickSend working from chat. | | Manual | ClawLink | |---|---|---| | **Setup flow** | Collect and store the right ClickSend credentials yourself, then keep the account mapping and request format correct. | ClawLink keeps the setup in one hosted flow so non-technical users can link ClickSend without custom integration screens. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for ClickSend. | 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 ClickSend actions to the runtime in a format your agent can reliably use. | 166 tools for ClickSend are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes ClickSend 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 ClickSend in the browser, and the 166 tools above work from chat. There is no SDK and no config file, and the ClickSend 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 ClickSend skill but can't call the tools The ClawHub skill teaches OpenClaw about ClickSend, but the calls run through the ClawLink plugin and your connected account. Make sure ClickSend 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 ClickSend 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 ClickSend tools ClickSend 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 ClickSend 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. ### ClickSend 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. ### The setup form accepts credentials but calls still fail Re-enter the credentials carefully and verify the account-level permissions for ClickSend. Basic and token-based integrations tend to fail on formatting mistakes or limited account roles. ### Is there a OpenClaw ClickSend integration? Yes. ClawLink is the fastest way to connect OpenClaw to ClickSend: link your ClickSend account once in the browser and OpenClaw can call the ClickSend API through 166 ready-made tools — no custom code or token handling. ### How do I add ClickSend to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink ClickSend skill from ClawHub, then you click Connect in the dashboard to authorize ClickSend. OpenClaw calls the tools from the next message — no config files, and the ClickSend key you paste is stored server-side instead of in your environment. ### How long does it take to connect ClickSend to OpenClaw? About two minutes. Sign in, click Connect next to ClickSend in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring ClickSend up myself? The alternative to ClawLink is usually manual credential 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 ClickSend working from chat. ### OpenClaw installed the ClickSend skill but can't call the tools The ClawHub skill teaches OpenClaw about ClickSend, but the calls run through the ClawLink plugin and your connected account. Make sure ClickSend 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 tools](https://claw-link.dev/openclaw/mailchimp) — Create email campaigns and manage audiences