Online Action

trigger.pushcut_event

TriggerChat & messagingconnection requiredruns in-engine

Registers a Pushcut subscription for one named online action on publish and starts one run per delivery, keyed on Pushcut's own event id.

Start a run when a Pushcut online action is triggered from an iOS device.

Ask about Pushcut All Pushcut nodes Provider API docs ↗

Connection

Required: Yes — the node will not save without one
Auth type: API key
Providers: Pushcut
Secret shape: the Pushcut API key (created with 'Add API Key' in the app's Account view)
Resolved by: config.connection_id, else node.connection_id
Note: Publishing needs MANTLE_APP_PUBLIC_BASE_URL set to a URL Pushcut's servers can reach from the public internet — the subscription is registered as a server-side callback, never a local-network one.

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
action_name The online action to subscribe to, spelled exactly as it is in the Pushcut app. It is not created here: define the action in Pushcut first, then trigger it from a widget, a Shortcut, an NFC tag or a notification button.	string	Yes	—	≤ 200 characters	Log a mood

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "action_name": "Log a mood"
}

Output

One shape.

pushcut event

The flattened Pushcut EventData: which online action ran, the input it carried, and when.

Field	Type	Example
id Pushcut's own id for this trigger event. Also the idempotency key: a redelivery carries the same id and joins the run it already started instead of starting a second.	string	1234567890abc
action_name The online action that fired — the same name this trigger subscribed to.	string	Log a mood
input Whatever was passed with the action: the text typed into an input notification, or the value a Shortcut handed it. Empty when the action took none.	string	cheerful
timestamp When the action ran, as Pushcut's Unix timestamp.	number	1564579405
iso_timestamp The same instant as an ISO-8601 string, for nodes that want a date.	string	2026-07-31T13:23:25Z
payload The delivery exactly as Pushcut sent it, for anything the fields above do not lift out.	object	—

{
  "action_name": "Log a mood",
  "id": "1234567890abc",
  "input": "cheerful",
  "iso_timestamp": "2026-07-31T13:23:25Z",
  "payload": {
    "actionName": "Log a mood",
    "id": "1234567890abc",
    "input": "cheerful",
    "isoTimestamp": "2026-07-31T13:23:25Z",
    "timestamp": 1564579405
  },
  "timestamp": 1564579405
}

Notes

Publishing registers the subscription in Pushcut; unpublishing, disabling or archiving deletes it. A workflow that is off is off at Pushcut too.
Pushcut does NOT sign these deliveries — its API document specifies no signature header and no shared secret — so the callback URL is the only thing standing between the internet and a run. Anyone who learns it can start one, with a payload of their choosing.
The online action must already exist in the Pushcut app; this trigger subscribes to a name, it does not create the action.
One subscription per published workflow. Two workflows may subscribe to the same action name — Pushcut delivers to both.

Related Pushcut nodes

See Online Action 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.

Book a technical demo Talk to sales