Actions

How actions work

Every useful workflow has at least one action.
Actions have one input and one main output. Wire them downstream of a trigger, a condition's true / false port, or another action.
They run in order — when one action finishes, the next one starts. Nothing runs in parallel.
If an action fails, the workflow stops. Anything downstream of the failure doesn't run.
Every action produces output data that later nodes can reference. See References and templates.

Adding an action

Click Add node in the toolbar. The Add Node dialog opens.
Scroll to the Actions group, or type in the Search nodes… field.
Pick an action. It appears on the canvas; drag an edge from your upstream node to its input.

[SCREENSHOT] The Add Node dialog with the Actions group expanded, showing the four actions (Post To Channel, Send Direct Message, Set Light, Stop And Fail). The search field is empty; the Triggers and Conditions groups are collapsed above.

The action catalog

Today the product ships four actions. More will land as integrations grow.

Stop And Fail

Built-in. Always fails the workflow with a message you choose. Useful after a condition where the "false" path should deliberately end in a red execution — easy to spot in history.

Message — the error text stored on the failed execution. Optional; defaults to "Stop And Fail Reached".

Send Direct Message (Slack)

Slack DM to one person, looked up by email.

Email — the recipient's Slack email.
Content type — text or markdown.
Content — the message body.
Output: channel (the DM's channel id) and ts (message timestamp).

See Slack for connect setup and common failures.

Post To Channel (Slack)

Message to a Slack channel.

Channel — name (e.g. #alerts) or ID.
Content type / Content — same as the DM action.
Output: channel, ts.

Set Light (Philips Hue)

Controls one Hue light.

Device — the light to change.
On — true/false; leave blank to not change the state.
Brightness — 0–100.
Color temperature — in mireks, 153 (cool) to 500 (warm).
Color X / Color Y — CIE xy for precise color; power users only.
Output: lightId and success.

See Philips Hue for setup.

Filling in the fields

Every action field has a three-mode picker: Fixed value, Data reference, or Template. Full walkthrough (and a template quickstart) in References and templates. The short version:

Fixed value — the value never changes.
Data reference — pull one upstream field into this field.
Template — combine fixed and dynamic text, or coerce a type.

Enable and disable

Right-click an action (or use the hover toolbar) and pick Disable node to skip it on future runs. Enable node turns it back on.

A disabled action is skipped at execution time.
Anything wired downstream through a disabled action is also skipped — disabling cuts off that whole subtree.
Useful for pausing one branch without deleting the nodes.

Chaining multiple actions

Actions run in the order of the edges connecting them:

Upstream first, downstream after.
If the first action fails, the second doesn't run.
To fan out (e.g. DM the organizer and post to a channel after the same trigger), connect both actions to the same upstream node — they still run one after the other, not in parallel.

Design tips

Use Stop And Fail deliberately. Dropping it on the "false" side of a condition makes unwanted runs show up red in history.
Prefer channels over DMs for team alerts. Fewer integration-disconnect failures, clearer audit trail.
Reference outputs of earlier actions when useful. Slack actions produce a ts you can include in follow-up messages.