How to connect Reply to OpenClaw
Connect Reply to OpenClaw with ClawLink: paste your Reply key once and 21 tools work from chat. No MCP server to run, nothing stored on your machine.
ReplyAPI KEYMCPReply.io is a sales engagement platform that automates multichannel outreach, enabling users to create and manage email campaigns, track replies, and monitor performance directly within their platform.. Once connected, OpenClaw can read and act on Reply from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Reply 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 Reply setup: install one ClawHub skill, connect Reply in the browser, and OpenClaw can call real Reply 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 Reply.
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 Reply
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Reply?"
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 Reply in the ClawLink dashboard — paste your Reply API key once.
Verify the connection by asking OpenClaw:
Use Reply to generate ulid 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:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Reply is connected in the dashboard, that agent calls the same 21 Reply tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Reply MCP for OpenClaw
Looking for a Reply MCP server for OpenClaw? ClawLink connects Reply to OpenClaw and exposes 21 Reply tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Reply integration works the same way.
What the OpenClaw Reply integration can do
21 Reply tools are ready for OpenClaw once the account is connected. The 17 below are the ones people reach for most; your agent can call all 21.
17 of 21 Reply tools for OpenClaw
| Tool | What it does |
|---|---|
Generate ulid reply_generate_ulid | Generate ULID |
Get all lists reply_get_all_lists | Retrieve all available people lists |
Get blacklist all reply_get_blacklist_all | Retrieve the full list of blacklisted domains and emails |
Get campaign schedules all reply_get_campaign_schedules_all | Retrieves all campaign schedules from Reply.io, including the default schedule and any |
Get campaigns for contact reply_get_campaigns_for_contact | Retrieve campaigns a contact belongs to by contact ID |
Get contacts in list by ID reply_get_contacts_in_list_by_id | Retrieve contacts in a specific personal list |
Get list by ID reply_get_list_by_id | Return a specific people list by its ID |
Get templates list reply_get_templates_list | Retrieves all email templates from Reply.io, including user-created, team-shared |
List campaigns reply_list_campaigns | List all campaigns (sequences) |
List contacts basic reply_list_contacts_basic | List contacts |
List email accounts reply_list_email_accounts | List all email accounts |
Search contacts reply_search_contacts | Search contacts by email |
Create list reply_create_list | Add a new personal list on the People page |
Mark contact as finished reply_mark_contact_as_finished | Marks a contact (by email) or all contacts under a domain as finished in all Reply.io campaigns |
Mark contact as replied reply_mark_contact_as_replied | Mark a contact as replied in all campaigns by email or domain |
Move contacts to lists reply_move_contacts_to_lists | Move one or more contacts to specified lists |
Remove domain from blacklist reply_remove_domain_from_blacklist | Remove the specified domain from the blacklist |
Try it: find the Reply tool you need
Browse the 17 Reply tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Reply to generate ulid and walk me through the result in plain English.
Pull the relevant data from Reply, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Reply, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Reply, 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 Reply working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Reply API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Reply 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 Reply. | 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 Reply actions to the runtime in a format your agent can reliably use. | 21 tools for Reply are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Reply 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 Reply in the browser, and the 21 tools above work from chat. There is no SDK and no config file, and the Reply 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 Reply skill but can't call the tools
The ClawHub skill teaches OpenClaw about Reply, but the calls run through the ClawLink plugin and your connected account. Make sure Reply 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 Reply 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 Reply tools
Reply 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 Reply 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.
Reply 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 Reply 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 Reply integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Reply: link your Reply account once in the browser and OpenClaw can call the Reply API through 21 ready-made tools — no custom code or token handling.
How do I add Reply to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Reply skill from ClawHub, then you click Connect in the dashboard to authorize Reply. OpenClaw calls the tools from the next message — no config files, and the Reply key you paste is stored server-side instead of in your environment.
How long does it take to connect Reply to OpenClaw?
About two minutes. Sign in, click Connect next to Reply in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Reply 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 Reply working from chat.
OpenClaw installed the Reply skill but can't call the tools
The ClawHub skill teaches OpenClaw about Reply, but the calls run through the ClawLink plugin and your connected account. Make sure Reply 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.
