How to connect Omnisend to Hermes Agent (no API keys)

Most guides for giving Hermes Agent Omnisend access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical Omnisend setup: pair once in the browser and your always-on Hermes agent can act on Omnisend for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.

Copy this prompt into Hermes to install the plugin and pair your account.

Prompt for Hermes

Set up ClawLink for Hermes and tell me when it's ready.

1. Install the plugin:
hermes plugins install ClawLink-HQ/hermes-plugin --enable

2. Start pairing. It prints an approval link, so show me the link and stop, don't wait:
hermes clawlink begin

3. I'll approve it in my browser, then reply "approved".

4. When I say approved, finish setup:
hermes clawlink finish

5. Then run `hermes clawlink test` and tell me whether ClawLink is ready.

Setup

It takes three steps to connect Hermes to Omnisend.

1
Install and pair
Install the ClawLink plugin, then pair Hermes with a one-time browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable
2
Connect Omnisend
One-click OAuth in the dashboard.
3
Use it from chat
Ask Hermes Agent: "What can you do with Omnisend?"

Install by command

The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:

hermes plugins install ClawLink-HQ/hermes-plugin --enable
hermes clawlink begin    # prints an approval link — open it and approve
hermes clawlink finish   # after approving in the browser
hermes clawlink test

Then connect Omnisend in the ClawLink dashboard — a one-click OAuth approval, no API keys.

Verify the connection by asking Hermes:

Create it in Omnisend for me, then confirm the important fields before you finish.

Using a different agent?

The Hermes 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 login

login 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 Hermes

Looking for a Omnisend MCP server for Hermes Agent? ClawLink connects Omnisend to Hermes Agent and exposes 43 Omnisend tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Omnisend integration works the same way.

What the Hermes Agent Omnisend integration can do

43 Omnisend tools are ready for Hermes Agent 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 Hermes

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 Hermes 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.

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 Hermes Agent. 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 Hermes Agent 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

Hermes paired but still can't use Omnisend

Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.

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 Hermes Agent Omnisend integration?

Yes. ClawLink is the fastest way to connect Hermes to Omnisend: link your Omnisend account once in the browser and Hermes Agent can call the Omnisend API through 43 ready-made tools — no custom code or token handling.

How do I connect Omnisend to Hermes with ClawLink?

Install the plugin with hermes plugins install ClawLink-HQ/hermes-plugin --enable, then pair once: run hermes clawlink begin, approve the link in your browser, and run hermes clawlink finish. Connect Omnisend in the dashboard and Hermes can use it from the next message — no config files or API keys to manage.

How long does it take to connect Omnisend to Hermes Agent?

About two minutes. Sign in, click Connect next to Omnisend in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.

Why use ClawLink instead of wiring Omnisend up myself?

Hermes paired but still can't use Omnisend

How to connect Omnisend to Hermes Agent

Setup

Install and pair

Connect Omnisend

Use it from chat