Pushover is a service that enables real-time notifications to your devices through simple API integration.
Pushover is a service that enables real-time notifications to your devices through simple API integration. On Nagent, Pushover is exposed as a fully-configurable notifications integration that any agent can call — 29 actions, and API key authentication. No code is required to wire Pushover into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Pushover to automate the kinds of tasks notifications teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Pushover into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Pushover, with input parameters and output schema. Drop these into any step of an agent built in Helix.
PUSHOVER_CANCEL_RECEIPT_RETRIESTool to cancel further retries for an emergency-priority message before its expiry. Use when you no longer want Pushover to keep attempting delivery of an urgent notification.
Input parameters
Your Pushover application API token
The receipt ID returned when the message was first sent
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PUSHOVER_CANCEL_RETRIES_BY_TAGTool to cancel retries for all active emergency-priority Pushover messages matching a specific tag. Use after sending emergency messages when you want to stop further retries for a given tag.
Input parameters
Tag assigned to messages when originally sent; identifies which receipts to cancel.
Application API token for authentication.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PUSHOVER_CLIENT_ACK_DELETE_UP_TO_IDTool to delete/acknowledge device messages up to a specific message ID. Use when you want to clear all messages up to a known ID; call after retrieving the latest message ID.
Input parameters
User session secret obtained at login; required for Open Client actions.
Highest message ID previously seen; all messages up to and including this ID are deleted.
The unique device ID returned during Device Registration.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PUSHOVER_CLIENT_FETCH_MESSAGESTool to download pending messages for a registered device. Use after device registration to retrieve messages queued server-side.
Input parameters
User session secret obtained after login, required to authenticate the client.
Unique identifier of the registered device to fetch messages for.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PUSHOVER_CLIENT_LOGINTool to authenticate a Pushover user by email and password. Use when you need to obtain a user key and session secret. Include twofa code if prompted by a prior HTTP 412 response.
Input parameters
Pushover account e-mail; case-sensitive
Two-factor authentication code; include only after prior HTTP 412 response
Pushover account password; case-sensitive
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PUSHOVER_CLIENT_REALTIME_WEBSOCKETTool to establish a secure WebSocket connection for real-time message notifications. Use after obtaining device ID and secret to receive instant push events.
Input parameters
Your user session secret for login
Maximum time in seconds to listen for events before closing
Your Pushover client device ID for login
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PUSHOVER_CLIENT_REGISTER_DEVICETool to register an Open Client desktop device. Use when you have a session secret from users/login to obtain a device ID.
Input parameters
Must be 'O' (capital letter O) for Open Client.
Short device name; allowed characters are letters, numbers, underscore, hyphen; max length 25.
User session secret obtained from users/login; must be included.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PUSHOVER_GET_APP_ICON_IMAGETool to fetch an application icon PNG by icon identifier. Use when you need to retrieve and cache the Pushover app icon image.
Input parameters
Icon identifier string (from message object's 'icon' field).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PUSHOVER_GET_APP_LIMITSTool to retrieve the current monthly message limit, remaining messages, and reset time for a Pushover application. Use when monitoring your monthly quota before sending messages.
Input parameters
Your Pushover application API token.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PUSHOVER_GET_APP_TOKENTool to fetch stored Pushover application API token. Use when supplying credentials to other Pushover actions securely.
Input parameters
Optional override for the Pushover application API token. If provided, this value will be returned.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PUSHOVER_GET_RECEIPT_STATUSTool to poll the status of an emergency-priority notification receipt. Use after sending an emergency notification to check its delivery and acknowledgment. Use when you have the `receipt` from an emergency-priority message and need to track its retries and acknowledgment status.
Input parameters
Your application API token for Pushover.
30-character alphanumeric receipt returned when sending an emergency-priority message.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PUSHOVER_GET_TEAM_API_TOKENTool to fetch stored Pushover for Teams API token. Use when supplying team credentials to other Pushover Teams actions securely.
Input parameters
Optional override for the Pushover team API token. If provided, this value will be returned.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PUSHOVER_GLANCES_UPDATETool to update a user's Glances widget data without sending a notification. Use after preparing glance data fields: title, text, subtext, count, or percent.
Input parameters
Main line of data (max 100 characters).
The recipient user's Pushover user key.
Count value for smaller screens; may be negative.
Short label/description (max 100 characters).
Your application's API token.
Restrict update to a specific device's widget; omit to update all widgets.
Percent/progress value (0-100 inclusive).
Second line of data (max 100 characters).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PUSHOVER_GROUP_ADD_USERTool to add an existing Pushover user to a delivery group. Use when you need to include a user in a group by their user key.
Input parameters
Optional memo or note for the user (up to 200 characters).
The Pushover user key of the existing user to add.
Your Pushover application API token owning the group.
Device name to restrict messages for this user; leave blank to target all devices.
Delivery group key identifying the target group.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PUSHOVER_GROUP_CREATETool to create a new Delivery Group. Use when you need to group multiple recipients under one group key before sending notifications.
Input parameters
The new group's name.
Your Pushover application API token.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PUSHOVER_GROUP_DISABLE_USERTool to temporarily disable deliveries to a user or specific device within a Pushover group. Use when suspending notifications for a user (or device) in an active group.
Input parameters
The Pushover user key to disable within the group.
Your Pushover application API token.
Specific device name for the user's membership; if omitted, disables all devices for that user.
The delivery group's key (path parameter).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PUSHOVER_GROUP_ENABLE_USERTool to re-enable deliveries to a previously disabled user (or specific device) within a Pushover group. Use after disabling a user's or device's notifications to restore delivery.
Input parameters
Pushover user key to re-enable deliveries for.
Your application API token associated with the group.
Optional device name to match; if omitted, all disabled memberships for the user are re-enabled.
Unique key for the Pushover delivery group.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PUSHOVER_GROUP_GETTool to retrieve details for a Delivery Group. Use when you need to fetch a group's name and member list.
Input parameters
Your Pushover application API token owning the group.
Delivery group key identifying the target group.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PUSHOVER_GROUP_LISTTool to list all Delivery Groups. Use when you need to retrieve your account's delivery groups after obtaining a valid API token.
Input parameters
Your Pushover application API token.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PUSHOVER_GROUP_REMOVE_USERTool to remove a user (or optionally a specific device) from a Pushover delivery group. Use when you need to revoke a user's membership so they stop receiving group notifications.
Input parameters
The Pushover user key to remove from the group.
Your Pushover application API token.
Specific device name for the user's membership; if omitted, removes the user from all devices.
The delivery group's key (path parameter).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PUSHOVER_GROUP_RENAMETool to rename an existing Delivery Group. Use after confirming the group_key to update a group's name.
Input parameters
The new name to assign to the delivery group. Only one group name may exist per account.
Your Pushover application API token for authentication.
The unique key of the delivery group to rename (used in the URL path).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PUSHOVER_LICENSE_ASSIGNTool to assign a pre-paid license credit to a Pushover user by key or email. Use when you need to allocate a license and optionally restrict to a specific platform.
Input parameters
Platform to restrict license to: 'Android', 'iOS', or 'Desktop'; leave blank to assign for first installed platform.
Pushover user key; required if email is not supplied.
User's e-mail address; required if user is not supplied.
Your application's API token.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PUSHOVER_LICENSE_CHECK_CREDITSTool to retrieve remaining license credits for a Pushover application. Use when monitoring your licensing quota before assigning new licenses.
Input parameters
Your Pushover application API token for licensing API.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PUSHOVER_SEND_MESSAGETool to send a push notification with optional title, URL, priority, sound, attachments, and filters.
Input parameters
Time to live in seconds; ignored for emergency priority.
Supplementary URL shown with the message.
Set to 1 to enable HTML parsing; mutually exclusive with monospace.
(Emergency only) comma-separated tags stored with the receipt.
User or group key(s). Up to 50 comma-separated alphanumeric keys (each 30 chars).
(Emergency only) seconds between retries; minimum 30.
Name of a supported sound (blank for user default).
Message title (max 250 chars). Defaults to the application name.
Your Pushover application API token (30 alphanumeric characters).
One device name or comma-separated names; ignored for multiple users or non-team groups.
(Emergency only) total seconds to keep retrying; max 10800.
Notification body text (up to 1024 UTF-8 characters).
(Emergency only) URL called when the user acknowledges.
Message priority: -2 (lowest), -1 (low), 0 (normal), 1 (high), 2 (emergency).
Set to 1 to use monospace font; mutually exclusive with html.
Unix epoch time to display instead of current time.
Title for the supplementary URL.
Binary image attachment (max 5MB).
MIME type of the base64 attachment (e.g., 'image/jpeg').
Base64-encoded image data; requires 'attachment_type'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PUSHOVER_STORE_TEAM_API_TOKENTool to securely store a Pushover for Teams API token. Use after obtaining a team API token to enable subsequent Teams actions.
Input parameters
Pushover for Teams API token to store for future actions.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PUSHOVER_SUBSCRIPTION_FLOWTool to validate and return a Pushover subscription code. Use when Pushover does not support programmatic subscription creation and you need to confirm your code before redirecting users.
Input parameters
The subscription code obtained from Pushover's web-based subscription flow. Must be URL-safe (no whitespace).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PUSHOVER_TEAMS_ADD_USERTool to add a user to a Pushover for Teams organization. Use when inviting a user with optional admin rights, instant login link, or custom delivery group.
Input parameters
User’s full name
'true' to add the user as a team administrator
User’s email address
Delivery Group name; if it doesn’t exist, it will be created; default is the auto-updating Team Delivery Group
Team API token (not application token)
'true' to include an Instant Login link in the welcome e-mail (valid 7 days)
Explicit password to assign; if omitted or blank, a random password will be generated and e-mailed
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PUSHOVER_TEAMS_REMOVE_USERTool to remove a user from a Pushover for Teams organization. Use when you need to revoke a user's access after confirming their email should be removed from the team.
Input parameters
E-mail address of the user to remove from the team.
Team API token (not an application token).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PUSHOVER_VALIDATE_USER_OR_GROUPTool to validate a Pushover user or group key for deliverability. Use before sending notifications to ensure the key (and optional device) is valid and has active devices.
Input parameters
The user's or group's identifier (key) to validate.
Your Pushover application API token.
Device name to validate against that user; if omitted, validation succeeds when at least one active device exists.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 70 agents privately built on Nagent that already use Pushover.
Build on Nagent
Connect Pushover to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Pushover, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Pushover is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Pushover is connected, you configure its 29 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Pushover steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Pushover event fires, the agent kicks off automatically.
Every Pushover action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Pushover ships with 29 pre-built notifications actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Pushover together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Pushover-based workflows tailored to your business.