Cancel Retries By Tag
pushover.cancel_receipts_by_tag
ActionChat & messagingconnection required
Calls the Pushover API with the connection's credentials.
Stop every still-repeating emergency notification that was sent with a given tag, in one call.
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
1 field, 1 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 |
|---|---|---|---|---|---|
tag The tag the emergency messages were sent with. | string | Yes | — | — | incident-42 |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"tag": "incident-42"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
tag The tag whose repeats were cancelled. | string | — |
cancelled True when Pushover accepted the cancellation. | boolean | — |
request Pushover's unique id for this API request. | string | — |
{
"cancelled": false,
"request": "",
"tag": ""
}See Cancel Retries By Tag 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.