How to connect Omnisend to OpenClaw
Connect Omnisend to OpenClaw with ClawLink in one click — 43 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup.
OmnisendOAUTH2MCPEmail and SMS marketing for e-commerce. Once connected, OpenClaw can read and act on Omnisend from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Omnisend 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 Omnisend setup: install one ClawHub skill, connect Omnisend in the browser, and OpenClaw can call real Omnisend actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into OpenClaw, or open the Omnisend skill on ClawHub.
Before installing anything, inspect the ClawHub skill metadata and setup requirements.
If the skill asks you to install a third-party package or CLI, verify its source, maintainer, and package contents before running the install command.
Install the skill "Omnisend" (hith3sh/omnisend-marketing) from ClawHub only after those checks pass.
Skill page: https://clawhub.ai/hith3sh/omnisend-marketing
Keep the work scoped to this skill only.
After install, help me finish setup from verified skill metadata.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.Setup
It takes three steps to connect OpenClaw to Omnisend.
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 Omnisend
One-click OAuth in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Omnisend?"
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 Omnisend in the ClawLink dashboard — a one-click OAuth approval, no API keys.
Verify the connection by asking OpenClaw:
Create it in Omnisend for me, then confirm the important fields before you finish.
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 Omnisend is connected in the dashboard, that agent calls the same 43 Omnisend tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Omnisend MCP for OpenClaw
Looking for a Omnisend MCP server for OpenClaw? ClawLink connects Omnisend to OpenClaw and exposes 43 Omnisend tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Omnisend integration works the same way.
What the OpenClaw Omnisend integration can do
43 Omnisend 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 43.
30 of 43 Omnisend tools for OpenClaw
| Tool | What it does |
|---|---|
Create batch omnisend_create_batch | Create an Omnisend batch operation |
Create cart omnisend_create_cart | Create an Omnisend cart |
Create category omnisend_create_category | Create an Omnisend category |
Create or update contact omnisend_create_or_update_contact | Create or update an Omnisend contact |
Create order omnisend_create_order | Create an Omnisend order |
Create product omnisend_create_product | Create an Omnisend product |
Get batch information omnisend_get_batch_information | Get Omnisend batch information |
Get batches omnisend_get_batches | List Omnisend batches |
Get brand omnisend_get_brand | Get Omnisend brand info |
Get cart omnisend_get_cart | Get an Omnisend cart |
Get category omnisend_get_category | Get an Omnisend category |
Get contact omnisend_get_contact | Get an Omnisend contact |
Get order omnisend_get_order | Get an Omnisend order |
Get product omnisend_get_product | Get an Omnisend product |
List campaigns omnisend_list_campaigns | List Omnisend campaigns |
Get batch item omnisend_get_batch_item | Retrieve a specific item within a batch by batchID and itemID |
Get batch items omnisend_get_batch_items | Retrieve processed items of a specific batch by ID |
Get product category omnisend_get_product_category | Retrieve a specific product category by ID |
List carts omnisend_list_carts | Retrieve a paginated list of carts with optional filtering |
List categories omnisend_list_categories | Retrieve a paginated list of product categories |
List contacts omnisend_list_contacts | Retrieve a paginated list of contacts with optional filtering |
List events omnisend_list_events | Retrieve all custom events created in Omnisend app |
List product categories omnisend_list_product_categories | Retrieve a paginated list of product categories from the Omnisend catalog |
List products omnisend_list_products | Retrieve a paginated list of products |
Add cart product omnisend_add_cart_product | Add a product to a cart in Omnisend (v3 API) |
Create product category omnisend_create_product_category | Create a new product category in the Omnisend catalog |
Replace cart omnisend_replace_cart | Replace an existing cart in Omnisend using the v3 API |
Replace cart product omnisend_replace_cart_product | Replace a product in a cart using Omnisend v3 API |
Replace category omnisend_replace_category | Replace a category's title by ID |
Replace order omnisend_replace_order | Completely replace an existing order in Omnisend |
Try it: find the Omnisend tool you need
Browse the 30 Omnisend tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Create it in Omnisend for me, then confirm the important fields before you finish.
Create it in Omnisend for me, then confirm the important fields before you finish.
Create it in Omnisend for me, then confirm the important fields before you finish.
Create it in Omnisend for me, then confirm the important fields before you finish.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual OAuth app 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 Omnisend working from chat.
| Manual | ClawLink | |
|---|---|---|
| Connection flow | Register a Omnisend app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Omnisend through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Omnisend. | 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 Omnisend actions to the runtime in a format your agent can reliably use. | 43 tools for Omnisend are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Omnisend 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 Omnisend in the browser, and the 43 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Omnisend skill but can't call the tools
The ClawHub skill teaches OpenClaw about Omnisend, but the calls run through the ClawLink plugin and your connected account. Make sure Omnisend 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 Omnisend 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 Omnisend tools
Omnisend 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 Omnisend 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.
Omnisend 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.
OAuth finished in the browser but the account is still missing
Try reconnecting Omnisend and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.
FAQ
Is there a OpenClaw Omnisend integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Omnisend: link your Omnisend account once in the browser and OpenClaw can call the Omnisend API through 43 ready-made tools — no custom code or token handling.
How do I add Omnisend to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Omnisend skill from ClawHub, then you click Connect in the dashboard to authorize Omnisend. OpenClaw calls the tools from the next message — no config files or API keys to manage.
How long does it take to connect Omnisend to OpenClaw?
About two minutes. Sign in, click Connect next to Omnisend in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Omnisend up myself?
The alternative to ClawLink is usually manual OAuth app 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 Omnisend working from chat.
OpenClaw installed the Omnisend skill but can't call the tools
The ClawHub skill teaches OpenClaw about Omnisend, but the calls run through the ClawLink plugin and your connected account. Make sure Omnisend 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.
