Cancel Notification
pushcut.cancel_notification
ActionChat & messagingconnection required
Calls the Pushcut API with the connection's credentials.
Remove or cancel a notification that was already submitted, by the id pushcut.send_notification returned.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Pushcut
- Secret shape
- the API key, or {"api_key": "…"}
- Config it needs
- server_id
- Resolved by
- config.connection_id, else node.connection_id
Configuration
3 fields, 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 |
|---|---|---|---|---|---|
notification_id Id of the submitted notification to cancel. | string | Yes | — | — | 1snurqjF5vLxoUq09Q358 |
devices Names of the devices to act on; leave empty for every active device. | array | No | — | array of string | ["Simon's iPhone"] |
only_scheduled Cancel only notifications that have not been delivered yet. | boolean | No | false | — | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"devices": [
"Simon's iPhone"
],
"notification_id": "1snurqjF5vLxoUq09Q358",
"only_scheduled": false
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
id The notification id that was cancelled. | string | — |
cancelled True when Pushcut accepted the cancellation. | boolean | — |
devices The devices the cancellation was limited to. | array | — |
onlyScheduled True when delivered notifications were deliberately left alone. | boolean | — |
{
"cancelled": false,
"devices": [],
"id": "",
"onlyScheduled": false
}See Cancel Notification run in a workflow.
In a technical demo we add the Pushcut connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.