Explore 3 workflow actions for Pushover, including account permissions and operation limits.
1 read action2 write actions
WORKFLOW ACTIONS
What you can configure.
Choose an action in the workflow builder, connect an account, and map its inputs. These actions are available in the catalog; your account access and a successful test determine whether they work for your setup.
Send message
Write
Send one notification to the connection's verified user or group.
Permissions and limits
Account permissions
Application token and an active recipient device
Operation limits
A successful response confirms queueing by Pushover, not delivery to a device. Emergency priority requires retry and expire fields and is not offered here. A lost response remains uncertain and is not automatically resent.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Send to recipient
Write
Send one notification to an explicitly supplied user or group key.
Permissions and limits
Account permissions
Application token and an active recipient device
Operation limits
A successful response confirms queueing by Pushover, not delivery to a device. Emergency priority requires retry and expire fields and is not offered here. A lost response remains uncertain and is not automatically resent.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Validate recipient
Read
Check a user or group key without sending a message.
Permissions and limits
Account permissions
Application token and a valid recipient key
Operation limits
A valid recipient has at least one active device. No notification is sent.
SETUP
Start with a controlled test.
01Connect the intended account
Use the account and permissions required for your process. Review the connection check before configuring a workflow action.
02Review inputs and access
Select a listed operation and map its required inputs. Use test records and add a human approval before writes that need review.
03Confirm the result
Inspect step outputs and confirm the result in Pushover. A saved workflow is not a completed provider action.
