How to connect AimTell to Hermes Agent
Connect AimTell to Hermes with ClawLink: paste your AimTell key once and 15 tools work from chat. No MCP server to run, nothing stored on your machine.
AimTellAPI KEYMCPAimTell is a web push notification platform for managing websites, subscribers, campaigns, segments, and delivery analytics.. Once connected, Hermes Agent can read and act on AimTell from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent AimTell 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 AimTell setup: pair once in the browser and your always-on Hermes agent can act on AimTell for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect Hermes to AimTell.
1Install 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 AimTell
Paste your API key in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with AimTell?"
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 testThen connect AimTell in the ClawLink dashboard — paste your AimTell API key once.
Verify the connection by asking Hermes:
Pull the relevant data from AimTell, summarize it in plain English, and point out anything that needs attention.
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 loginlogin opens the same browser approval and stores a credential locally. Once AimTell is connected in the dashboard, that agent calls the same 15 AimTell tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
AimTell MCP for Hermes
Looking for a AimTell MCP server for Hermes Agent? ClawLink connects AimTell to Hermes Agent and exposes 15 AimTell tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw AimTell integration works the same way.
What the Hermes Agent AimTell integration can do
15 AimTell tools are ready for Hermes Agent once the account is connected. The 13 below are the ones people reach for most; your agent can call all 15.
13 of 15 AimTell tools for Hermes
| Tool | What it does |
|---|---|
Get analytics over time aimtell_get_analytics_over_time | Return a daily AimTell metric over a date range for all websites or one website |
Get campaign results aimtell_get_campaign_results | Return daily send, delivery, bounce, click, conversion, and available revenue results for a |
List campaigns aimtell_list_campaigns | Return one page of manual, event-triggered, RSS, or API push campaigns for an AimTell website |
List notification logs aimtell_list_notification_logs | Return one page from AimTell's sampled notification log for the last seven days, optionally |
List segments aimtell_list_segments | Return all audience segments for an AimTell website, including the IDs and definitions used for |
List subscribers aimtell_list_subscribers | Return one page of subscribers for an AimTell website, optionally filtered by segment or |
List websites aimtell_list_websites | Return one page of websites available to the connected AimTell account, including site IDs |
Create manual campaign aimtell_create_manual_campaign | Create a manual push campaign as a draft only; this tool never schedules or sends it |
Create segment aimtell_create_segment | Create a named audience segment for a website from an AimTell segment definition |
Set subscriber attributes aimtell_set_subscriber_attributes | Set custom attributes on one subscriber identified by subscriber UID, user alias, or email |
Update manual campaign aimtell_update_manual_campaign | Update the content or targeting of an unscheduled, unsent, non-A/B manual campaign draft |
Update segment aimtell_update_segment | Change the name or audience definition of an existing AimTell segment |
Send push notification aimtell_send_push_notification | Immediately send a one-off push notification to exactly one explicitly selected audience: |
Try it: find the AimTell tool you need
Browse the 13 AimTell tools
Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from AimTell, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from AimTell, summarize it in plain English, and point out anything that needs attention.
List the relevant items in AimTell, group them by priority, and recommend what Hermes should do next.
List the relevant items in AimTell, group them by priority, and recommend what Hermes 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want AimTell working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the AimTell API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected AimTell 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 AimTell. | 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 AimTell actions to the runtime in a format your agent can reliably use. | 15 tools for AimTell are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes AimTell 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 AimTell in the browser, and the 15 tools above work from chat. There is no SDK and no config file, and the AimTell 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
Hermes paired but still can't use AimTell
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 AimTell 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 AimTell tools
AimTell 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 AimTell 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.
AimTell 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 AimTell has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a Hermes Agent AimTell integration?
Yes. ClawLink is the fastest way to connect Hermes to AimTell: link your AimTell account once in the browser and Hermes Agent can call the AimTell API through 15 ready-made tools — no custom code or token handling.
How do I connect AimTell 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 AimTell in the dashboard and Hermes can use it from the next message — no config files, and the AimTell key you paste is stored server-side instead of in your environment.
How long does it take to connect AimTell to Hermes Agent?
About two minutes. Sign in, click Connect next to AimTell in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.
Why use ClawLink instead of wiring AimTell up myself?
The alternative to ClawLink is usually manual API key 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 AimTell working from chat.
Hermes paired but still can't use AimTell
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.
