Run Shortcut
pushcut.execute
ActionChat & messagingconnection required
Calls the Pushcut API with the connection's credentials.
Run a Shortcut or set a HomeKit scene on a Pushcut Automation Server, now or after a delay.
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
7 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 |
|---|---|---|---|---|---|
shortcut Name of the Shortcut to run on the Automation Server. | string | No | — | — | My Shortcut |
homekit Name of the HomeKit scene to set instead of running a Shortcut. | string | No | — | — | Downstairs Lights On |
input Value passed as the input to the Shortcut. | string | No | — | — | — |
timeout How long to wait for the result, in seconds, or the word nowait to return as soon as the request is accepted. | string | No | — | — | nowait |
delay Run the action this far out instead of now, as a duration such as 10s, 15m or 6h. | string | No | — | — | 10s |
identifier Identifier for a delayed request, so a later call can overwrite it or pushcut.cancel_execution can cancel it. | string | No | — | — | MyIdentifier |
server_id Automation Server to run on; overrides the connection's default. | string | No | — | — | — |
- At least one of shortcut, homekit must be set.
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"delay": "10s",
"homekit": "Downstairs Lights On",
"identifier": "MyIdentifier",
"shortcut": "My Shortcut",
"timeout": "nowait"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
shortcut The Shortcut that was asked to run, if any. | string | — |
homekit The HomeKit scene that was asked to run, if any. | string | — |
identifier The identifier a delayed request was filed under. | string | — |
serverId The Automation Server the request was sent to. | string | — |
result The Automation Server's response body, as returned. | object | — |
{
"homekit": "",
"identifier": "",
"result": {},
"serverId": "",
"shortcut": ""
}See Run Shortcut 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.