How to connect Pushbullet to OpenClaw
Connect Pushbullet to OpenClaw with ClawLink: paste your Pushbullet key once and 15 tools work from chat. No MCP server to run, nothing stored on your machine.
PushbulletAPI KEYMCPPush notifications, links, and files across devices. Once connected, OpenClaw can read and act on Pushbullet from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Pushbullet access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Pushbullet setup: install one ClawHub skill, connect Pushbullet in the browser, and OpenClaw can call real Pushbullet actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into OpenClaw, or open the Pushbullet skill on ClawHub.
Before installing anything, inspect the ClawHub skill metadata and setup requirements.
If the skill asks you to install a third-party package or CLI, verify its source, maintainer, and package contents before running the install command.
Install the skill "Pushbullet" (hith3sh/pushbullet) from ClawHub only after those checks pass.
Skill page: https://clawhub.ai/hith3sh/pushbullet
Keep the work scoped to this skill only.
After install, help me finish setup from verified skill metadata.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.Setup
It takes three steps to connect OpenClaw to Pushbullet.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Pushbullet
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Pushbullet?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Pushbullet in the ClawLink dashboard — paste your Pushbullet API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Pushbullet, summarize it in plain English, and point out anything that needs attention.
Using a different agent?
The OpenClaw 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 Pushbullet is connected in the dashboard, that agent calls the same 15 Pushbullet tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Pushbullet MCP for OpenClaw
Looking for a Pushbullet MCP server for OpenClaw? ClawLink connects Pushbullet to OpenClaw and exposes 15 Pushbullet tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Pushbullet integration works the same way.
What the OpenClaw Pushbullet integration can do
15 Pushbullet tools are ready for OpenClaw once the account is connected. The 11 below are the ones people reach for most; your agent can call all 15.
11 of 15 Pushbullet tools for OpenClaw
| Tool | What it does |
|---|---|
Get user pushbullet_get_user | Retrieve the currently authenticated user's profile |
List chats pushbullet_list_chats | List all chat objects for the current user |
List devices pushbullet_list_devices | List all registered devices for the current user |
List pushes pushbullet_list_pushes | List pushes with optional filtering and pagination |
Create chat pushbullet_create_chat | Create a new chat with the specified email address |
Create device pushbullet_create_device | Register a new device under the current user's account |
Create push pushbullet_create_push | Send a new push (note, link, or file) to a device, user, channel, or client |
Update chat pushbullet_update_chat | Mute or unmute an existing chat |
Update device pushbullet_update_device | Update metadata for a device by its identifier |
Update push pushbullet_update_push | Update a push (dismiss or modify list items) by its identifier |
Upload request pushbullet_upload_request | Obtain a signed upload URL for a file before pushing |
Try it: find the Pushbullet tool you need
Browse the 11 Pushbullet tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from Pushbullet, summarize it in plain English, and point out anything that needs attention.
List the relevant items in Pushbullet, group them by priority, and recommend what OpenClaw should do next.
List the relevant items in Pushbullet, group them by priority, and recommend what OpenClaw should do next.
List the relevant items in Pushbullet, group them by priority, and recommend what OpenClaw 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 OpenClaw. 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. | 15 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 OpenClaw users instead. You install the plugin once, connect Pushbullet in the browser, and the 15 tools above work from chat. There is no SDK and no config file, and the Pushbullet 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
OpenClaw installed the Pushbullet skill but can't call the tools
The ClawHub skill teaches OpenClaw about Pushbullet, but the calls run through the ClawLink plugin and your connected account. Make sure Pushbullet is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
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.
FAQ
Is there a OpenClaw Pushbullet integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Pushbullet: link your Pushbullet account once in the browser and OpenClaw can call the Pushbullet API through 15 ready-made tools — no custom code or token handling.
How do I add Pushbullet to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Pushbullet skill from ClawHub, then you click Connect in the dashboard to authorize Pushbullet. OpenClaw calls the tools from the next message — no config files, and the Pushbullet key you paste is stored server-side instead of in your environment.
How long does it take to connect Pushbullet to OpenClaw?
About two minutes. Sign in, click Connect next to Pushbullet in the dashboard, authenticate, and OpenClaw 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 OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Pushbullet working from chat.
OpenClaw installed the Pushbullet skill but can't call the tools
The ClawHub skill teaches OpenClaw about Pushbullet, but the calls run through the ClawLink plugin and your connected account. Make sure Pushbullet is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
