Pushover
Pushover node reference - all 11 operations, the credential it needs, and a worked example.
Pushover push notifications (Messaging). 11 operations: send a message with every documented option (priority, sound, device, URL, HTML or monospace, timestamp, TTL, base64 image attachment, and the emergency retry/expire/callback/tags set — a group key in the recipient field broadcasts); emergency receipts (get status, cancel retries, cancel by tag); validate a user or group key; list notification sounds; update a glance widget; read the app's monthly message quota; licensing (check credits, assign a license); and subscription migration.
Credential: Pushover - see Credentials.
Permissions
Pushover has no scope system and no consent screen. Every operation below is authorised by the same application API token, created at pushover.net/apps - what it may do is fixed by Pushover, not chosen by you, so there is no box to tick and a refusal is never a missing grant. A 4xx here means the token or the user/group key is wrong (the response's errors array names which); a 429 means the application's monthly message quota is exhausted, which is a limit rather than a permission. The one genuinely different credential in Pushover's API is the separate Team API Token, which the Teams endpoints require - those are not implemented, precisely because this credential cannot authenticate them.
Operations (11)
Messages
| Operation | What it does |
|---|---|
sendMessage | Send message |
Emergency receipts
| Operation | What it does |
|---|---|
getReceipt | Get receipt status |
cancelEmergencyRetries | Cancel emergency retries |
cancelEmergencyByTag | Cancel emergency messages by tag |
Users & sounds
| Operation | What it does |
|---|---|
validateUser | Validate user or group key |
listSounds | List notification sounds |
Glances
| Operation | What it does |
|---|---|
updateGlance | Update glance widget |
Application
| Operation | What it does |
|---|---|
getAppLimits | Get monthly message limits |
Licensing
| Operation | What it does |
|---|---|
checkLicenseCredits | Check license credits |
assignLicense | Assign a license |
Subscriptions
| Operation | What it does |
|---|---|
migrateSubscription | Migrate user to a subscription |
Example
Page someone until they acknowledge, rather than hoping they saw it
A normal push notification is fire-and-forget: if the on-call engineer's phone is face-down, the alert is missed. Priority 2 is Pushover's emergency level — it re-alerts on a schedule until a human acknowledges it, and hands back a receipt you can poll or cancel.
Set Operation to sendMessage, then fill in:
| Field | Value | Notes |
|---|---|---|
userKey | {{ vars.oncallPushoverKey }} | The user or group key to alert |
message | {{ myTrigger.workflowName }} failed: {{ myTrigger.error }} | The body |
title | Pipory run failed | Shown as the notification heading |
priority | 2 | Emergency: re-alerts until acknowledged. retry and expire are required at this priority |
retry | 60 | Seconds between re-alerts; Pushover's floor is 30 |
expire | 3600 | Give up after this many seconds |
Sets {{page.receipt}} — poll it with getReceipt to see whether anyone acknowledged, or stop the re-alerts early with cancelEmergencyRetries.