How to connect Webpushr to Hermes Agent
Connect Webpushr to Hermes with ClawLink: paste your Webpushr key once and 6 tools work from chat. No MCP server to run, nothing stored on your machine.
WebpushrAPI KEYMCPWebpushr enables websites to send push notification campaigns to all subscribers, segments, custom audiences, or individual subscribers and monitor campaign delivery.. Once connected, Hermes Agent can read and act on Webpushr from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent Webpushr 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 Webpushr setup: pair once in the browser and your always-on Hermes agent can act on Webpushr 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 Webpushr.
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 Webpushr
Paste your API key in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with Webpushr?"
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 Webpushr in the ClawLink dashboard — paste your Webpushr API key once.
Verify the connection by asking Hermes:
Pull the relevant data from Webpushr, 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 Webpushr is connected in the dashboard, that agent calls the same 6 Webpushr tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Webpushr MCP for Hermes
Looking for a Webpushr MCP server for Hermes Agent? ClawLink connects Webpushr to Hermes Agent and exposes 6 Webpushr tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Webpushr integration works the same way.
What the Hermes Agent Webpushr integration can do
6 Webpushr tools are ready for Hermes Agent once the account is connected.
All 6 Webpushr tools for Hermes
| Tool | What it does |
|---|---|
Get notification status webpushr_get_notification_status | Get delivery and engagement counts for a Webpushr notification campaign using its campaign ID |
Get subscriber count webpushr_get_subscriber_count | Return lifetime and currently active subscriber counts for the connected Webpushr site |
Send notification to all webpushr_send_notification_to_all | Create or schedule a push notification campaign for every subscriber of the connected Webpushr |
Send notification to attributes webpushr_send_notification_to_attributes | Create or schedule a push notification campaign for subscribers matching any supplied custom |
Send notification to segments webpushr_send_notification_to_segments | Create or schedule a push notification campaign for subscribers in one or more Webpushr segments |
Send notification to subscriber webpushr_send_notification_to_subscriber | Send or schedule a push notification to one Webpushr subscriber ID |
Try it: find the Webpushr tool you need
Browse the 6 Webpushr 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 Webpushr, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Webpushr, summarize it in plain English, and point out anything that needs attention.
Use Webpushr to send notification to all for me and draft the message before sending.
Use Webpushr to send notification to attributes for me and draft the message before sending.
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 Webpushr working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Webpushr API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Webpushr 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 Webpushr. | 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 Webpushr actions to the runtime in a format your agent can reliably use. | 6 tools for Webpushr are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Webpushr 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 Webpushr in the browser, and the 6 tools above work from chat. There is no SDK and no config file, and the Webpushr 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 Webpushr
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 Webpushr 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 Webpushr tools
Webpushr 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 Webpushr 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.
Webpushr 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 Webpushr 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 Webpushr integration?
Yes. ClawLink is the fastest way to connect Hermes to Webpushr: link your Webpushr account once in the browser and Hermes Agent can call the Webpushr API through 6 ready-made tools — no custom code or token handling.
How do I connect Webpushr 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 Webpushr in the dashboard and Hermes can use it from the next message — no config files, and the Webpushr key you paste is stored server-side instead of in your environment.
How long does it take to connect Webpushr to Hermes Agent?
About two minutes. Sign in, click Connect next to Webpushr in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.
Why use ClawLink instead of wiring Webpushr 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 Webpushr working from chat.
Hermes paired but still can't use Webpushr
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.
Related
GitHub tools
Manage repositories, issues, pull requests, and workflows
PagerDuty tools
Manage incidents, on-call schedules, and services
Connect SafetyCulture
SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.