How to connect Dripcel to OpenClaw
Connect Dripcel to OpenClaw with ClawLink: paste your Dripcel key once and 18 tools work from chat. No MCP server to run, nothing stored on your machine.
DripcelAPI KEYMCPDripcel is a platform for automated SMS and Email marketing, campaign compliance, and data-driven lead generation.. Once connected, OpenClaw can read and act on Dripcel from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Dripcel 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 Dripcel setup: install one ClawHub skill, connect Dripcel in the browser, and OpenClaw can call real Dripcel 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 Dripcel.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Dripcel
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Dripcel?"
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:
openclaw plugins install clawhub:clawlink-pluginThen 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 Dripcel in the ClawLink dashboard — paste your Dripcel API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Dripcel, 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:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Dripcel is connected in the dashboard, that agent calls the same 18 Dripcel tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Dripcel MCP for OpenClaw
Looking for a Dripcel MCP server for OpenClaw? ClawLink connects Dripcel to OpenClaw and exposes 18 Dripcel tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Dripcel integration works the same way.
What the OpenClaw Dripcel integration can do
18 Dripcel 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 18.
16 of 18 Dripcel tools for OpenClaw
| Tool | What it does |
|---|---|
Get balance dripcel_get_balance | Retrieves the current credit balance for your Dripcel organization account |
Get campaigns dripcel_get_campaigns | Retrieves a list of campaigns from Dripcel |
Get contact dripcel_get_contact | Retrieve a single contact by their cell number (MSISDN) |
Get deliveries dripcel_get_deliveries | Retrieve SMS/email delivery records from Dripcel |
Get email templates dripcel_get_email_templates | Retrieves all email templates from your Dripcel account |
Get sales dripcel_get_sales | Retrieve a list of all sales |
List tags dripcel_list_tags | Retrieve all tags in your Dripcel organization |
Post compliance send dripcel_post_compliance_send | Check if phone numbers are allowed to receive SMS messages based on opt-out status and campaign |
Post replies search dripcel_post_replies_search | Search for SMS/message replies with flexible filtering by ID, campaign, phone number, reply |
Search send logs dripcel_search_send_logs | Search for SMS send logs with flexible filtering by ID, phone number, campaign, delivery |
Create contacts dripcel_create_contacts | Upload a list of new contacts to Dripcel in bulk |
Opt out contact dripcel_opt_out_contact | Opt out a contact from multiple campaigns at once |
Put contact tag add dripcel_put_contact_tag_add | Add one or more tags to a contact identified by phone number |
Send bulk email dripcel_send_bulk_email | Send bulk emails to multiple recipients using a template |
Send sms dripcel_send_sms | Send a single SMS to a contact |
Upsert contacts dripcel_upsert_contacts | Upload contacts in bulk, creating new contacts or updating existing ones |
Try it: find the Dripcel tool you need
Browse the 16 Dripcel tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from Dripcel, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Dripcel, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Dripcel, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Dripcel, 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 Dripcel working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Dripcel API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Dripcel 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 Dripcel. | 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 Dripcel actions to the runtime in a format your agent can reliably use. | 18 tools for Dripcel are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Dripcel 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 Dripcel in the browser, and the 18 tools above work from chat. There is no SDK and no config file, and the Dripcel key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Dripcel skill but can't call the tools
The ClawHub skill teaches OpenClaw about Dripcel, but the calls run through the ClawLink plugin and your connected account. Make sure Dripcel 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 Dripcel 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 Dripcel tools
Dripcel 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 Dripcel 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.
Dripcel 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 Dripcel has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Dripcel integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Dripcel: link your Dripcel account once in the browser and OpenClaw can call the Dripcel API through 18 ready-made tools — no custom code or token handling.
How do I add Dripcel to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Dripcel skill from ClawHub, then you click Connect in the dashboard to authorize Dripcel. OpenClaw calls the tools from the next message — no config files, and the Dripcel key you paste is stored server-side instead of in your environment.
How long does it take to connect Dripcel to OpenClaw?
About two minutes. Sign in, click Connect next to Dripcel in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Dripcel 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 Dripcel working from chat.
OpenClaw installed the Dripcel skill but can't call the tools
The ClawHub skill teaches OpenClaw about Dripcel, but the calls run through the ClawLink plugin and your connected account. Make sure Dripcel 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.
