How to connect Engage Platform to OpenClaw
Connect Engage Platform to OpenClaw with ClawLink: paste your Engage Platform key once and 18 tools work from chat. No MCP server to run, nothing stored on your machine.
Engage PlatformAPI KEYMCPEngage Platform provides customer data, account, list, event, batch, and transactional messaging APIs for customer engagement workflows.. Once connected, OpenClaw can read and act on Engage Platform from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Engage Platform 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 Engage Platform setup: install one ClawHub skill, connect Engage Platform in the browser, and OpenClaw can call real Engage Platform 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 Engage Platform.
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 Engage Platform
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Engage Platform?"
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 Engage Platform in the ClawLink dashboard — paste your Engage Platform API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Engage Platform, 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 Engage Platform is connected in the dashboard, that agent calls the same 18 Engage Platform tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Engage Platform MCP for OpenClaw
Looking for a Engage Platform MCP server for OpenClaw? ClawLink connects Engage Platform to OpenClaw and exposes 18 Engage Platform tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Engage Platform integration works the same way.
What the OpenClaw Engage Platform integration can do
18 Engage Platform 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 Engage Platform tools for OpenClaw
| Tool | What it does |
|---|---|
Get list engage_platform_get_list | Retrieve an Engage list by its internal list ID |
Get user engage_platform_get_user | Retrieve one Engage customer or account by its caller-supplied application UID, not Engage's |
List account members engage_platform_list_account_members | List customers belonging to one Engage account identified by its application UID |
List lists engage_platform_list_lists | Return one cursor-controlled page of active Engage user lists |
List users engage_platform_list_users | Return one cursor-controlled page of Engage customers and accounts, optionally filtered by |
Add user to accounts engage_platform_add_user_to_accounts | Add a customer to one or more Engage accounts, optionally assigning a role in each account |
Add user to lists engage_platform_add_user_to_lists | Add and subscribe an existing user to one or more Engage lists |
Create list engage_platform_create_list | Create an Engage user list and return its Engage list ID for subscription tools |
Create user engage_platform_create_user | Create an Engage customer or account with a caller-chosen application UID |
Set account member role engage_platform_set_account_member_role | Set or replace a customer's role in one Engage account membership |
Set list subscription engage_platform_set_list_subscription | Subscribe, resubscribe, or unsubscribe an existing user on one Engage list |
Update list engage_platform_update_list | Update supplied settings on an existing Engage list without changing unspecified fields |
Upsert user engage_platform_upsert_user | Update profile or custom attributes for an application UID, creating the user if it does not |
Archive list engage_platform_archive_list | Archive a list so it disappears from list results and cannot receive new subscribers |
Remove list subscriber engage_platform_remove_list_subscriber | Completely remove one user's membership from one Engage list |
Track user event engage_platform_track_user_event | Append an immutable event to a user's Engage activity history |
Try it: find the Engage Platform tool you need
Browse the 16 Engage Platform 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 Engage Platform, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Engage Platform, summarize it in plain English, and point out anything that needs attention.
List the relevant items in Engage Platform, group them by priority, and recommend what OpenClaw should do next.
List the relevant items in Engage Platform, group them by priority, and recommend what OpenClaw should do next.
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 Engage Platform working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Engage Platform API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Engage Platform 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 Engage Platform. | 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 Engage Platform actions to the runtime in a format your agent can reliably use. | 18 tools for Engage Platform are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Engage Platform 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 Engage Platform in the browser, and the 18 tools above work from chat. There is no SDK and no config file, and the Engage Platform 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 Engage Platform skill but can't call the tools
The ClawHub skill teaches OpenClaw about Engage Platform, but the calls run through the ClawLink plugin and your connected account. Make sure Engage Platform 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 Engage Platform 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 Engage Platform tools
Engage Platform 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 Engage Platform 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.
Engage Platform 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 Engage Platform 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 Engage Platform integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Engage Platform: link your Engage Platform account once in the browser and OpenClaw can call the Engage Platform API through 18 ready-made tools — no custom code or token handling.
How do I add Engage Platform to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Engage Platform skill from ClawHub, then you click Connect in the dashboard to authorize Engage Platform. OpenClaw calls the tools from the next message — no config files, and the Engage Platform key you paste is stored server-side instead of in your environment.
How long does it take to connect Engage Platform to OpenClaw?
About two minutes. Sign in, click Connect next to Engage Platform in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Engage Platform 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 Engage Platform working from chat.
OpenClaw installed the Engage Platform skill but can't call the tools
The ClawHub skill teaches OpenClaw about Engage Platform, but the calls run through the ClawLink plugin and your connected account. Make sure Engage Platform 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.
