How to connect Cardly to Hermes Agent
Connect Cardly to Hermes with ClawLink: paste your Cardly key once and 29 tools work from chat. No MCP server to run, nothing stored on your machine.
CardlyAPI KEYMCPCardly helps businesses create great engagement with customers by getting out of inboxes and into mailboxes.. Once connected, Hermes Agent can read and act on Cardly from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent Cardly 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 Cardly setup: pair once in the browser and your always-on Hermes agent can act on Cardly 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 Cardly.
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 Cardly
Paste your API key in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with Cardly?"
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 Cardly in the ClawLink dashboard — paste your Cardly API key once.
Verify the connection by asking Hermes:
Use Cardly to echo request 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 Cardly is connected in the dashboard, that agent calls the same 29 Cardly tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Cardly MCP for Hermes
Looking for a Cardly MCP server for Hermes Agent? ClawLink connects Cardly to Hermes Agent and exposes 29 Cardly tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Cardly integration works the same way.
What the Hermes Agent Cardly integration can do
29 Cardly tools are ready for Hermes Agent once the account is connected. The 24 below are the ones people reach for most; your agent can call all 29.
24 of 29 Cardly tools for Hermes
| Tool | What it does |
|---|---|
Echo request cardly_echo_request | Echo all request parameters, body, and headers for debugging purposes |
Generate preview cardly_generate_preview | Generate a low-quality, watermarked preview document for a card |
Get artwork cardly_get_artwork | Retrieve information on a specific piece of artwork by its unique ID |
Get webhook cardly_get_webhook | Get details on an existing webhook |
List artwork cardly_list_artwork | Retrieve the currently available artwork for your organisation |
List contact lists cardly_list_contact_lists | Retrieve all active contact lists for your organization |
List credit history cardly_list_credit_history | Retrieves the account's credit transaction history showing all credits and debits |
List doodles cardly_list_doodles | Retrieve your currently available doodles from Cardly |
List fonts cardly_list_fonts | List available fonts for handwriting and text personalization in Cardly cards |
List gift credit history cardly_list_gift_credit_history | Lists gift credit history records for your organization with pagination and optional time-based |
List invitations cardly_list_invitations | Retrieve active invitations for your organisation with optional filters |
List media cardly_list_media | Retrieve the currently available media sizes for product artwork |
List orders cardly_list_orders | Retrieves a paginated list of orders placed by your organization |
List templates cardly_list_templates | Retrieve your currently available templates from Cardly |
List users cardly_list_users | Retrieve all users associated with your account |
List webhooks cardly_list_webhooks | Retrieves all webhooks configured for your organization, including their status, target URLs |
List writing styles cardly_list_writing_styles | List available writing styles |
Retrieve account balance cardly_retrieve_account_balance | Retrieve the current account and gift credit balances for your organisation |
Retrieve order cardly_retrieve_order | Retrieves detailed information about a specific order by its ID |
Retrieve user cardly_retrieve_user | Retrieves detailed information about a specific user account by ID |
Create contact list cardly_create_contact_list | Add a new contact list |
Create invitation cardly_create_invitation | Send an invitation to use your organisation portal |
Create webhook cardly_create_webhook | Create a new webhook subscription |
Update webhook cardly_update_webhook | Update a webhook’s settings, including target URL and events |
Try it: find the Cardly tool you need
Browse the 24 Cardly tools
Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.
Example prompts
Use Cardly to echo request and walk me through the result in plain English.
Use Cardly to generate preview and walk me through the result in plain English.
Pull the relevant data from Cardly, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Cardly, 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 Cardly working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Cardly API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Cardly 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 Cardly. | 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 Cardly actions to the runtime in a format your agent can reliably use. | 29 tools for Cardly are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Cardly 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 Cardly in the browser, and the 29 tools above work from chat. There is no SDK and no config file, and the Cardly 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 Cardly
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 Cardly 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 Cardly tools
Cardly 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 Cardly 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.
Cardly 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 Cardly 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 Cardly integration?
Yes. ClawLink is the fastest way to connect Hermes to Cardly: link your Cardly account once in the browser and Hermes Agent can call the Cardly API through 29 ready-made tools — no custom code or token handling.
How do I connect Cardly 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 Cardly in the dashboard and Hermes can use it from the next message — no config files, and the Cardly key you paste is stored server-side instead of in your environment.
How long does it take to connect Cardly to Hermes Agent?
About two minutes. Sign in, click Connect next to Cardly in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.
Why use ClawLink instead of wiring Cardly 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 Cardly working from chat.
Hermes paired but still can't use Cardly
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.
