Pushover (with Encryption) icon

Pushover (with Encryption)

Send Pushover notifications with optional client-side AES-256-CBC + HMAC-SHA256 field encryption

Send Message

AI-generated

Summary

Sends a Pushover notification to a user or group via POST /1/messages.json, optionally encrypting the message, title, URL and URL title client-side (gzip + AES-256-CBC + HMAC-SHA256, base64) before sending. Runs once per input item.

Inputs

  • User or Group Key (required) — Pushover recipient key, sent as user.
  • Message (required) — Notification body (Pushover limit is 1024 UTF-8 chars of plaintext).
  • Priority — -2 silent, -1 quiet, 0 normal (default), 1 high, 2 emergency.
  • Retry (Seconds) — Shown and required only for Emergency priority; minimum 30. How often Pushover re-sends until acknowledged.
  • Expire (Seconds) — Shown and required only for Emergency priority; max 10800, default 1800. How long retries continue.
  • Encrypt Fields — Which of message, title, url, url_title to encrypt. All four are selected by default. Requires a 64-hex-character Encryption Key in the credential, otherwise the node errors. Empty string fields in this list are dropped from the request. If at least one field is encrypted, encrypted=1 is added. Deselect all to send plaintext.
  • Optional Fields — Collection of: Attachment (name of the input binary property, default data, uploaded as a file), Device (comma-separated device names), HTML Formatting (sent as html=1 when true), Sound (loaded from Pushover's sounds list), Timestamp (a date or Unix seconds, converted to Unix seconds), Title, TTL (seconds before auto-delete), URL, URL Title.

Output shape

One output item per input item, containing the Pushover API JSON response (typically status and request id).

The node needs the pushoverWithEncryptionApi credential. With Continue On Fail enabled, a failed item yields {error: message} instead of stopping the workflow. An invalid Timestamp, a missing or invalid encryption key, or a missing binary property raises an error for that item. Encrypted content can only be read by a Pushover client configured with the same key.

Examples

Example 1: Send an encrypted alert with a plaintext title for lockscreen preview

Set User Key and Message. In Encrypt Fields, deselect Title. Add Optional Field Title, e.g. "Server alert". The credential must contain a 64-hex encryption key.

Example 2: Page on-call with an emergency notification

Priority = Emergency (2), Retry = 60, Expire = 3600. Deselect all Encrypt Fields if no encryption key is configured.

Example 3: Send a screenshot from a previous node

Add Optional Field Attachment (Binary) with Input Binary Field = data, and set Message text.

Links

Discussion