Pushover
MessagingSend push notifications to phones, tablets, and desktops through Pushover, with emergency-priority alerts that repeat until a recipient acknowledges them.
What This Integration Enables
An agent can push critical system alerts to on-call staff using emergency priority that retries until acknowledged, and deliver order, deployment, or job-completion updates to a team's devices in real time. It can validate a recipient's user or group key and active devices before sending, and monitor the application's monthly message quota to stay under the sending cap. When an emergency alert is sent, the agent receives a receipt id that Get Receipt uses to poll acknowledgement and Cancel Emergency Retry uses to stop the repeats once the situation is handled.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Emergency page that persists until seen
A production alert fires and the on-call engineer must respond. The agent sends a Send Notification at emergency priority with a retry interval and expiry, so Pushover repeats the alert until it is acknowledged. It polls Get Receipt to confirm the alert was seen, and once the incident is handled elsewhere, Cancel Emergency Retry stops the repeats.
Validated deployment updates
A deployment finishes and the team wants a real-time update. The agent first calls Validate User/Group to confirm the recipient key resolves to at least one active device, then sends the update with Send Notification. Validating first avoids firing an important message into a key that cannot receive it.
Quota-aware alerting with a gate
A workflow is about to raise an emergency page during a noisy incident window. Because an emergency alert repeats until acknowledged and can wake people, the agent checks Get Limits, then stops at the human-in-the-loop step to confirm the escalation before it pages.
Human-in-Loop Highlight
An emergency-priority Pushover alert is not a normal notification. It repeats until a recipient acknowledges it, bypasses quiet hours, and is built to wake someone up. Before the agent raises an emergency page, it pauses and routes the decision to an operator: "This will page the on-call group at emergency priority and repeat until acknowledged. Confirm the escalation, or send at high priority instead?" This is FlowRunner's human-in-the-loop pattern, where the agent pauses on its own, states exactly how loud the alert will be, and resumes when the human answers. Routine and high-priority notifications send without interruption. An alert engineered to wake people gets a human decision first.
Agent Capabilities
6 actionsNotifications
2- Send Notification Sends a push notification to a user or group, with an optional title, priority from lowest to emergency, sound, supplementary URL, and device targeting. At emergency priority it requires retry and expiry settings and returns a receipt id for acknowledgement tracking.
- Validate User/Group Verifies that a user or group key is valid and has at least one active device, optionally checking a specific device. Used to confirm a recipient before sending.
Emergency
2- Get Receipt Retrieves the acknowledgement status of an emergency notification using its receipt id, reporting whether, when, and by which device it was acknowledged. Used to track whether an emergency alert was seen.
- Cancel Emergency Retry Stops an emergency notification from continuing to repeat, using its receipt id. Used once an alert has been handled so recipients stop being re-notified.
Account
2- Get Sounds Lists the notification sounds available to the application, including custom ones. Used to discover valid sound values beyond the built-in set.
- Get Limits Returns the application's monthly quota, remaining messages, and the reset timestamp. Used to monitor how close the application is to its sending cap.
Start building with Pushover
$100 in credits. No card required. Connect in minutes.