Validate Recipient
pushover.validate_user
ActionChat & messagingconnection required
Calls the Pushover API with the connection's credentials.
Check that a user or group key is valid and has at least one active device, before a workflow tries to notify it.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Pushover
- Secret shape
- the application API token, or {"token": "…"}
- Config it needs
- user_key
- Resolved by
- config.connection_id, else node.connection_id
Configuration
2 fields, none required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
user Recipient user or group key; overrides the connection's default recipient. | string | No | — | — | uQiRzpo4DXghDmr9QzzfQu27cmVRsG |
device Name of one device to deliver to, or several separated by commas. Leave blank to reach every device on the account. | string | No | — | — | iphone |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"device": "iphone",
"user": "uQiRzpo4DXghDmr9QzzfQu27cmVRsG"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
valid True when Pushover recognised the key. | boolean | — |
devices Names of the devices registered to the key. | array | — |
licenses Platforms the account is licensed for. | array | — |
group 1 when the key is a delivery group, 0 when a user. | number | — |
request Pushover's unique id for this API request. | string | — |
{
"devices": [],
"group": 0,
"licenses": [],
"request": "",
"valid": false
}See Validate Recipient run in a workflow.
In a technical demo we add the Pushover connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.