First-party app

Pushbullet

Name: Pushbullet
Author: w6w

Send push notifications, links, files and SMS across devices via Pushbullet.

stable CommunicationProductivity

About

Pushbullet ships in the w6w first-party pack. It declares 24 actions, 3 health checks, and the host runs its code in a sandbox that never sees the credential.

App id: io.w6w.pushbullet
Version: 0.1.0
Author: w6w
Licence: MIT
Categories: Communication · Productivity

Overview

Pushbullet bridges phones, browsers and desktops: a note, link or file pushed from a workflow shows up as a native notification on every device signed into the account, or on one device, or to another person’s email, or to every subscriber of a broadcast channel.

This app covers Pushbullet’s full HTTP API: sending and managing pushes (notes, links and files), registering and managing devices, one-to-one chats, broadcast channels and subscriptions, and SMS/MMS sent through an Android device’s own number. Health checks track the account’s live API rate-limit headroom — genuinely readable from response headers, unlike most vendors in this pack — alongside honest declarations for the two things Pushbullet does not expose: a public status page, and remaining monthly push allowance.

Build with Pushbullet

Three routes to the same 24 actions. The Workflow tab is generated from Pushbullet's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.

Actions Workflow Code MCP

Create Channel

channel-create

Create a broadcast channel that other users can subscribe to.

Get Channel Info

channel-info-get

Get public information about a channel by its tag, including recent pushes.

Create Chat

chat-create

Create a chat with another user or email address, or return the existing one.

Delete Chat

chat-delete

Delete a chat.

List Chats

chat-list

List chats belonging to the current user, most recently modified first.

Update Chat

chat-update

Mute or unmute a chat.

Create Device

device-create

Delete Device

device-delete

Delete a device.

List Devices

device-list

List devices belonging to the current user, most recently modified first.

Update Device

device-update

Update an existing device's display or registration fields.

Create Push

push-create

Send a note, link or file push to a device, an email address, a channel's subscribers, or an OAuth client's users — or broadcast to all of the account's devices.

Delete Push

push-delete

Delete a single push.

Delete All Pushes

push-delete-all

Delete every push belonging to the current user. Runs asynchronously on Pushbullet's side — pushes are removed shortly after this call returns, not immediately.

List Pushes

push-list

List push history, most recently modified first.

Update Push

push-update

Mark a push as dismissed (or not), hiding its notification where possible.

Create Subscription

subscription-create

Subscribe to a channel by its tag.

Delete Subscription

subscription-delete

Unsubscribe from a channel.

List Subscriptions

subscription-list

List channel subscriptions belonging to the current user, most recently modified first.

Update Subscription

subscription-update

Mute or unmute a channel subscription.

Send Text (SMS/MMS)

text-create

Send an SMS to one phone number, or an MMS group message to several, through an Android device with SMS permissions granted.

Delete Text

text-delete

Delete a text, canceling it if it has not already been sent.

Update Text

text-update

Update a queued text message. Has no effect if it has already been sent.

Request File Upload

upload-request

Request an authorized URL to upload a file to. POST the file's bytes as multipart/form-data to the returned upload URL yourself, then use the returned file URL in Create Push or Send Text.

Get Current User

user-get

Get the profile of the account this connection belongs to.

A workflow step names the app and the action, and the editor fills in the connection when you pick one. This is the Step shape from the workflow spec, carrying Pushbullet's real ids.

{
  "manifestVersion": "2",
  "name": "pushbullet-example",
  "steps": [
    {
      "id": "channel-create",
      "uses": {
        "app": "io.w6w.pushbullet",
        "action": "channel-create",
        "connection": "conn_YOUR_CONNECTION_ID"
      },
      "with": {
        "tag": "<tag>"
      }
    }
  ]
}

Here are some of the things you can do

Create Channel
perform
channel-create
Get Channel Info
read
channel-info-get
Create Chat
perform
chat-create
List Chats
read
chat-list
Update Chat
perform
chat-update

+19 more actions available

Every app-specific value here is a blank you have to fill in. An app action is reached through the connection that authenticates it, so the address is a connection id, not the app id — and connections belong to your account, so a public page cannot know yours. Create one for Pushbullet, then fill in the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the parameters that action declares. The call itself is real — the shape is transcribed from the studio's own snippet builder, which prints the same kind of blanks — but nothing in it is specific to Pushbullet. The Workflow tab is where this app's real ids are.

JS SDK CLI

Install

npm yarn pnpm deno

npm install @w6w/sdk

yarn add @w6w/sdk

pnpm add @w6w/sdk

deno add npm:@w6w/sdk

Code

import { W6wClient, isActionRun } from "@w6w/sdk";

// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();

const envelope = await client.run({
  urn: "conn_YOUR_CONNECTION_ID",
  action: "channel-create",
  payload: {
    tag: "<value>",
    // name: "<value>",
    // description: "<value>",
    // imageUrl: "<value>",
    // websiteUrl: "<value>",
    // feedUrl: "<value>",
    // feedFilters: "<value>",
    // subscribe: "<value>",
  },
});

if (isActionRun(envelope)) console.log(envelope.value);

Install the CLI

npm install -g @w6w/cli

CLI

w6w run conn_YOUR_CONNECTION_ID --action channel-create --payload '{"tag":"<value>"}'

Give an AI agent Pushbullet — without giving it Pushbullet's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.

One tool call

{
  "name": "w6w_invoke",
  "arguments": {
    "ref": "app:io.w6w.pushbullet#channel-create",
    "input": {
      "tag": "<tag>"
    }
  }
}

Every tool names its target with a single ref. The app: form above doesn't name a connection at all — the host resolves which of the caller's Pushbullet connections to sign with, and refuses rather than guesses when the answer is ambiguous.

What the agent gets

Credentials it can't read

The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.

A tool surface scoped to the caller

Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.

A durable workflow in one call

Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.

Health-aware discovery

Pushbullet's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.

The MCP surface is part of the hosted platform. Pushbullet itself is MIT, and the runtime that executes it is source-available (FSL).

Request MCP access

Health checks

Pushbullet declares its own checks, so its health is a property of the app rather than something the host guesses at.

service

Pushbullet platform status

quota

API rate-limit headroom

Remaining request budget read from X-Ratelimit-Remaining/-Limit/-Reset on GET /v2/users/me.