# How to connect Pushbullet to Hermes Agent (no API keys) > Connect Pushbullet to Hermes with ClawLink in one click — hosted OAuth, no API keys, no manual setup. Run real actions straight from chat. Web version: https://claw-link.dev/hermes/pushbullet Most guides for giving Hermes Agent Pushbullet 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 Pushbullet setup: pair once in the browser and your always-on Hermes agent can act on Pushbullet for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself. ## Pushbullet MCP for Hermes Looking for a Pushbullet MCP server for Hermes Agent? ClawLink connects Pushbullet to Hermes Agent and exposes 0 Pushbullet tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using OpenClaw instead? The [OpenClaw Pushbullet integration](https://claw-link.dev/openclaw/pushbullet) works the same way. **Start here — paste this into Hermes to set up ClawLink:** > 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 with `hermes clawlink begin`. It prints an approval link, so show me the link and stop, don't wait. > 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 Pushbullet. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Pushbullet** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask Hermes Agent in plain English. **Alternative for any agent (no plugin needed):** if the Hermes Agent plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect pushbullet # connect Pushbullet (browser OAuth) npx -y @useclawlink/cli actions pushbullet # list available actions npx -y @useclawlink/cli run pushbullet --input '' # execute (add --confirm for writes) ``` ## What the Hermes Agent Pushbullet integration can do - **Communication** — tools appear after Pushbullet is connected. ## Example prompts No example prompts are available yet. ## 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 Pushbullet working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Pushbullet API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Pushbullet 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 Pushbullet. | 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 Pushbullet actions to the runtime in a format your agent can reliably use. | 0 tools for Pushbullet are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Pushbullet 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 Pushbullet in the browser, and the connected Pushbullet account works from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### Hermes paired but still can't use Pushbullet 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 Pushbullet 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 Pushbullet tools Pushbullet 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 Pushbullet 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. ### Pushbullet 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 Pushbullet has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a Hermes Agent Pushbullet integration? Yes. ClawLink is the fastest way to connect Hermes to Pushbullet: link your Pushbullet account once in the browser and Hermes Agent can call the Pushbullet API through ready-made tools — no custom code or token handling. ### How do I connect Pushbullet 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 Pushbullet 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 Pushbullet to Hermes Agent? About two minutes. Sign in, click Connect next to Pushbullet in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Pushbullet 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 Pushbullet working from chat. ### Hermes paired but still can't use Pushbullet 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 - [Slack tools](https://claw-link.dev/hermes/slack) — Post messages and browse Slack channels - [Connect Postmark](https://claw-link.dev/hermes/postmark) — Transactional email delivery and analytics - [Resend tools](https://claw-link.dev/hermes/resend) — Send transactional and marketing emails