--- title: "Pushover Integration" description: "Send push notifications to phones, tablets, and desktops through Pushover, with emergency-priority alerts that repeat until a recipient acknowledges them." url: https://flowrunner.ai/integrations/pushover date_modified: 2026-08-01T02:40:32-07:00 --- # Pushover [Messaging](https://flowrunner.ai/integrations/category/communication-messaging) Send push notifications to phones, tablets, and desktops through Pushover, with emergency-priority alerts that repeat until a recipient acknowledges them. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 6 actions · Custom auth · available [Pushover website](https://pushover.net/) · [Platform Documentation](https://pushover.net/api) · Capability data verified 2026-08-12 1. A critical system event needs to page on-call staff 2. Agent builds the message and selects the recipient key 3. Agent confirms the recipient with Validate User/Group 4. Agent confirms retry and expiry settings for the priority level 5. Agent sends the alert with Send Notification 6. Agent polls acknowledgement with Get Receipt 7. An emergency-priority page that repeats until acknowledged waits for approval ## 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 **Alerts get missed**: A critical notification arrives quietly and goes unseen for hours **No acknowledgement loop**: Nobody knows whether the on-call engineer actually saw the alert **Quota surprises**: The application hits its monthly cap without warning ### With FlowRunner **Priority that persists**: Emergency alerts repeat until a person acknowledges them **Acknowledgement tracked**: Get Receipt confirms whether and when the alert was seen **Quota watched in flow**: Get Limits reports remaining messages before the cap is hit ## 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 processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 6 actions ### Notifications 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. ## Frequently Asked Questions ### What can FlowRunner do with Pushover? FlowRunner agents can run Send Notification, Validate User/Group, and Get Receipt in Pushover, plus 3 more actions. ### Does connecting Pushover to FlowRunner require OAuth? Pushover uses a custom authentication method to connect to FlowRunner. ### Can Pushover trigger a FlowRunner workflow automatically? Pushover doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Pushover?** This integration exposes Pushover to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/pushover. Site index: https://flowrunner.ai/llms.txt