Pushover integration

What it does

The Pushover integration lets your agency push notifications to a client's or operator's phone, tablet, or desktop from any TaskJuice workflow. Connect a Pushover application once and your workflows can send notifications, validate that a user key still resolves, list the catalog of available sounds, poll a receipt to see whether an emergency-priority message was acknowledged, and cancel an emergency-priority retry loop in flight. Pushover is action-only on this platform: the provider does not push inbound webhooks to the application owner, so any "react to a Pushover notification" workflow is driven from the originating system rather than from Pushover itself.

Connect a Pushover account

1. Open your workspace in TaskJuice and navigate to Connections.
2. Choose Pushover and click Connect.
3. In a new tab, sign in to Pushover at https://pushover.net and open https://pushover.net/apps/build. Register a new application for this workspace and copy the application API token from the application page.
4. Return to https://pushover.net and copy the user key shown at the top of the dashboard. Group keys created at https://pushover.net/groups work in the same field if you want to fan out to multiple recipients.
5. Paste the application API token into the Application API Token field and the user key into the User or Group Key field.
6. Save the connection.

Both values are sent inside the request body of every Pushover API call, so the connection stores them once and your workflows do not have to re-supply them per send. To rotate either value later, regenerate it in Pushover, update the connection in TaskJuice, and the next run picks it up.

Triggers

Pushover does not push event webhooks to the application owner, so this integration ships no triggers. Workflows that need to react to a Pushover notification should be driven from the originating system (the alerting source, the monitoring tool, the CRM) and use the Send Notification action below.

Actions

• pushover/send-notification sends a push notification to a user or group with optional priority, sound, supplementary URL, base64 attachment, HTML or monospace formatting, time-to-live, and the emergency-priority retry, expire, callback, and tags parameters.
• pushover/validate-user verifies that a user or group key is valid for the configured application and returns the device names registered to it.
• pushover/list-sounds returns the catalog of built-in notification sounds the application can request.
• pushover/get-receipt fetches the delivery and acknowledgement state of an emergency-priority (priority=2) message by receipt identifier.
• pushover/cancel-receipt stops further retries of an emergency-priority message by receipt identifier.

Known limitations

• Free Pushover applications are limited to 10,000 messages per month, Team applications to 25,000 per month. Pushover returns the current quota in the X-Limit-App-Limit, X-Limit-App-Remaining, and X-Limit-App-Reset response headers. When the monthly quota is exhausted, requests return HTTP 429 and the integration classifies them as retryable so the next workflow run picks up after the reset timestamp.
• Pushover allows polling a single receipt no faster than once every five seconds. Workflows that watch a receipt should schedule on a five-second-or-greater interval, otherwise the request returns an error.
• Emergency-priority messages require retry (minimum 30 seconds) and expire (maximum 10,800 seconds, three hours) and are capped at fifty total retries.
• Pushover does not expose an outbound webhook for the application owner, so reacting to Pushover-side events is not supported. Reaching a recipient still works through the Send Notification action.
• Attachments are capped at 5 MB after base64 decoding. Larger images need to be resized upstream.