Pushover
Send push notifications to phones, tablets and desktops through Pushover — including emergency-priority messages that retry until acknowledged.
About
Pushover ships in the w6w first-party pack. It declares 4 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.pushover- Version
- 0.1.2
- Author
- w6w
- Licence
- MIT
- Categories
- Communication · Monitoring & Observability
Overview
Pushover sends push notifications to phones, tablets and desktops through Pushover’s small four-endpoint API, including emergency-priority messages that repeat until someone acknowledges them or a set time expires. A single connection pairs an application token with a recipient’s user or group key, so sending a notification is a one-step call rather than a per-message credential lookup — though a different recipient can still be named per call when needed.
Message text, title and link fields are checked against Pushover’s own length limits before sending, so a workflow finds out at the boundary rather than having its text silently truncated. Emergency-priority messages are validated locally too — the required retry interval and expiry are enforced together, so a misconfigured emergency alert fails with a clear reason instead of being silently ignored by Pushover.
Quota is read live from Pushover’s own limits endpoint rather than declared unknown, since Pushover publishes the real numbers: a monthly allowance shared by every application on the account, with sending disabled entirely once it’s exhausted rather than merely throttled.
Build with Pushover
Three routes to the same 4 actions. The Workflow tab is generated from Pushover'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.
Get Message Limits
limits-get Get the monthly message allowance, how much of it is left, and when it resets. The allowance belongs to the account and is shared across all of its applications.
Send Message
message-send Send a push notification. Emergency priority repeats until acknowledged and requires Retry and Expire.
List Sounds
sounds-list List the notification sounds available to this application, including any custom sounds uploaded to the account that owns it.
Validate User Key
user-validate Check that a user or group key is valid and has at least one active device, and list those devices.
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 Pushover's real ids.
{
"manifestVersion": "2",
"name": "pushover-example",
"steps": [
{
"id": "message-send",
"uses": {
"app": "io.w6w.pushover",
"action": "message-send",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"message": "<message>"
}
}
]
}Here are some of the things you can do
-
Send Message
performmessage-send -
Get Message Limits
readlimits-get -
List Sounds
searchsounds-list -
Validate User Key
readuser-validate
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 Pushover, 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 Pushover. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { 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: "message-send",
payload: {
message: "<value>",
// title: "<value>",
// userOverride: "<value>",
// device: "<value>",
// priority: "<value>",
// retry: "<value>",
// expire: "<value>",
// sound: "<value>",
// url: "<value>",
// urlTitle: "<value>",
// html: "<value>",
// timestamp: "<value>",
// ttl: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action message-send --payload '{"message":"<value>"}'Give an AI agent Pushover — without giving it Pushover'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.pushover#message-send",
"input": {
"message": "<message>"
}
}
}
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 Pushover 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
Pushover'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. Pushover itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Pushover declares its own checks, so its health is a property of the app rather than something the host guesses at.
Pushover platform status
Monthly message allowance
Reads GET /1/apps/limits.json. Pushover meters messages per month per account — 10,000 free, 25,000 for a Team — shared by every application on the account.