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, and react when a recipient acknowledges an emergency alert. Connect a Pushover application once and your workflows can send notifications, run on-call rotations through delivery groups, update Glances widgets, track and cancel emergency-priority alerts, check your monthly message quota, and manage Pushover for Teams members and licenses.

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/emergency-acknowledged fires when a recipient acknowledges an emergency-priority (priority 2) notification. The run receives the message's receipt, the acknowledging user key, the device name, and the acknowledgement time.

Pushover has no webhook settings page. It calls back the URL set on each emergency message instead, so you wire this trigger up once per sending workflow:

1. Create a workflow that starts with Emergency Notification Acknowledged and publish it.
2. Copy the trigger's ingress URL from the trigger panel.
3. In the workflow that sends the alert, set the Send Notification action's priority to 2 and paste the ingress URL into the Acknowledgement callback URL field.

Every acknowledged message that carries that URL starts a run. Use the receipt value to match the acknowledgement to the alert that produced it. Pushover does not sign these callbacks, so the ingress URL itself is the credential: treat it as a secret and rotate it if it leaks.

Actions

Notifications and emergency alerts:

• pushover/send-notification sends a push notification to a user or group with optional priority, sound (picked from your application's sounds), supplementary URL, base64 attachment, HTML or monospace formatting, time to live, and the emergency-priority retry, expire, callback, and tags parameters.
• pushover/get-receipt fetches the delivery and acknowledgement state of an emergency-priority message by receipt.
• pushover/cancel-receipt stops further retries of one emergency-priority message by receipt.
• pushover/cancel-receipts-by-tag stops retries of every active emergency-priority message sent with a given tag, for example once an incident is resolved.
• pushover/update-glance updates a user's Glances widget (watch complication or home screen widget) with a title, text, count, or percentage, without sending a notification.

Delivery groups:

• pushover/list-groups lists your delivery groups.
• pushover/get-group returns a group's name and members.
• pushover/create-group creates a delivery group and returns its key.
• pushover/rename-group renames a group.
• pushover/add-user-to-group adds a user, or one of their devices, to a group.
• pushover/remove-user-from-group removes a user or device from a group.
• pushover/disable-user-in-group pauses delivery to a member, for example when they go off shift.
• pushover/enable-user-in-group resumes delivery to a paused member.

Account, licensing, and teams:

• pushover/validate-user checks that a user or group key is valid and returns its devices.
• pushover/list-sounds returns the built-in and custom sounds your application can use.
• pushover/get-limits returns your monthly message limit, the messages remaining, and the reset time.
• pushover/get-license-credits returns how many prepaid license credits you have left.
• pushover/assign-license spends a license credit on a user key or email address.
• pushover/get-team returns your Pushover for Teams members and their devices.
• pushover/add-user-to-team invites a person to your team by email.
• pushover/remove-user-from-team removes a person from your team.
• pushover/revoke-team-invitation withdraws a pending team invitation.
• pushover/migrate-subscription converts a user key into a subscription user key for an application that uses Pushover subscriptions.

Known limitations

• Free Pushover applications are limited to 10,000 messages per month and Team applications to 25,000 per month. When the monthly quota is exhausted, Pushover returns HTTP 429 and the integration treats it as retryable. Use Get Message Limits to check the remaining quota before a large send.
• Pushover allows polling a single receipt no faster than once every five seconds. Prefer the Emergency Notification Acknowledged trigger over polling Get Receipt.
• Emergency-priority messages require retry (minimum 30 seconds) and expire (maximum 10,800 seconds, three hours) and are capped at fifty retries.
• Emergency Notification Acknowledged only fires for messages sent with a callback URL. Acknowledgements of messages sent without one are not reported.
• Team actions need a Pushover for Teams account, and Assign License needs prepaid license credits. Both return an error on a standard account.
• Attachments are capped at 5 MB after base64 decoding. Larger images need to be resized upstream.