How to connect Laposta to Hermes Agent
Connect Laposta to Hermes with ClawLink: paste your Laposta key once and 25 tools work from chat. No MCP server to run, nothing stored on your machine.
LapostaAPI KEYMCPDutch newsletter app (email marketing) that makes it exceptionally easy to send professional newsletters.. Once connected, Hermes Agent can read and act on Laposta from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent Laposta 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 Laposta setup: pair once in the browser and your always-on Hermes agent can act on Laposta 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 Laposta.
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 Laposta
Paste your API key in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with Laposta?"
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 Laposta in the ClawLink dashboard — paste your Laposta API key once.
Verify the connection by asking Hermes:
Use Laposta to campaign get all and walk me through the result in plain English.
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 Laposta is connected in the dashboard, that agent calls the same 25 Laposta tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Laposta MCP for Hermes
Looking for a Laposta MCP server for Hermes Agent? ClawLink connects Laposta to Hermes Agent and exposes 25 Laposta tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Laposta integration works the same way.
What the Hermes Agent Laposta integration can do
25 Laposta tools are ready for Hermes Agent once the account is connected. The 21 below are the ones people reach for most; your agent can call all 25.
21 of 25 Laposta tools for Hermes
| Tool | What it does |
|---|---|
Campaign get all laposta_campaign_get_all | Retrieve all email campaigns from your Laposta account |
Field get laposta_field_get | Retrieve specific field details by field_id |
Field get all laposta_field_get_all | Retrieve all fields for a specific list in Laposta |
Get segment laposta_get_segment | Retrieve specific segment details by segment_id |
List get laposta_list_get | Retrieve specific list details by list_id |
List get all laposta_list_get_all | Retrieve all mailing lists from your Laposta account |
Member get laposta_member_get | Retrieve specific member details by member_id or email |
Member get all laposta_member_get_all | Retrieve all members from a specified Laposta mailing list |
Report get all laposta_report_get_all | Retrieve performance metrics for all campaigns |
Segment get all laposta_segment_get_all | Retrieve all segments from a mailing list |
Webhook get laposta_webhook_get | Retrieve specific webhook details by webhook_id |
Webhook get all laposta_webhook_get_all | Retrieve all webhooks for a specific list |
Field create laposta_field_create | Create a custom field for a mailing list to define subscriber attributes |
Field update laposta_field_update | Modify field configuration in a Laposta list |
List create laposta_list_create | Create a new mailing list in Laposta to manage email subscribers |
List update laposta_list_update | Modify list properties such as name, remarks, or notification emails |
Member create laposta_member_create | Add a new subscriber relationship to a list with custom fields and tracking info |
Member update laposta_member_update | Modify member data, status, or custom fields in a Laposta list |
Webhook create laposta_webhook_create | Register a new webhook for list events in Laposta |
Webhook update laposta_webhook_update | Modify webhook configuration including URL, event type, or blocked status |
List clear members laposta_list_clear_members | Clear all active members from a list |
Try it: find the Laposta tool you need
Browse the 21 Laposta tools
Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.
Example prompts
Use Laposta to campaign get all and walk me through the result in plain English.
Use Laposta to field get and walk me through the result in plain English.
Use Laposta to field get all and walk me through the result in plain English.
Pull the relevant data from Laposta, 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Laposta working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Laposta API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Laposta 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 Laposta. | 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 Laposta actions to the runtime in a format your agent can reliably use. | 25 tools for Laposta are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Laposta 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 Laposta in the browser, and the 25 tools above work from chat. There is no SDK and no config file, and the Laposta 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 Laposta
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 Laposta 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 Laposta tools
Laposta 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 Laposta 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.
Laposta 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 Laposta 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 Laposta integration?
Yes. ClawLink is the fastest way to connect Hermes to Laposta: link your Laposta account once in the browser and Hermes Agent can call the Laposta API through 25 ready-made tools — no custom code or token handling.
How do I connect Laposta 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 Laposta in the dashboard and Hermes can use it from the next message — no config files, and the Laposta key you paste is stored server-side instead of in your environment.
How long does it take to connect Laposta to Hermes Agent?
About two minutes. Sign in, click Connect next to Laposta in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.
Why use ClawLink instead of wiring Laposta 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 Laposta working from chat.
Hermes paired but still can't use Laposta
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.
