Pushover
Push notifications to phones, tablets and desktops with a priority, a sound and emergency retries that repeat until someone acknowledges them.
OCNORA ships 8 typed Pushover operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.
Before you connect Pushover
- Authentication
- API key
- Credential
- the application API token, or {"token": "…"}
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
What you can do with Pushover
Operations, grouped by what they do to your data.
Create and send 1
Read and search 4
Update 1
Delete and cancel 2
A sample Pushover workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Pushover trigger is needed.
- 2Get Message Limitspushover.get_limitsRead this month's message quota for the application: the limit, how many sends remain, and when the counter resets.
- 3Cancel Emergency Retriespushover.cancel_receiptStop an emergency-priority notification from repeating, without waiting for someone to acknowledge it.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Operations 8
- Cancel Emergency RetriesStop an emergency-priority notification from repeating, without waiting for someone to acknowledge it.pushover.cancel_receipt
- Cancel Retries By TagStop every still-repeating emergency notification that was sent with a given tag, in one call.pushover.cancel_receipts_by_tag
- Get Message LimitsRead this month's message quota for the application: the limit, how many sends remain, and when the counter resets.pushover.get_limits
- Get Emergency ReceiptRead whether an emergency-priority notification has been acknowledged, by whom, and whether it has expired.pushover.get_receipt
- List SoundsList the sound names this Pushover application may use, including any custom sounds uploaded to it.pushover.list_sounds
- Update GlanceUpdate the Pushover Glance widget on a user's watch or lock screen with a short line of text, a count or a percentage.pushover.send_glance
- Send NotificationPush a notification to a Pushover user or group, choosing its priority, sound and how long it stays on the device.pushover.send_message
- Validate RecipientCheck that a user or group key is valid and has at least one active device, before a workflow tries to notify it.pushover.validate_user
Pushover questions
- How does OCNORA authenticate with Pushover?
- With a stored API key credential, shaped the application API token, or {"token": "…"}. A connection test can check it when you add it.
- What can I automate with Pushover?
- 8 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Pushover operation I need is not listed?
- Where Pushover has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use Pushover?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Pushover calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
More in Chat & messaging
See your first Pushover workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.