Skip to content
English
Do you need help? Customer portal
neowit.io
  • There are no suggestions because the search field is empty.

Workflows overview

A tour of the workflow editor: where to find things, what the different areas do, and how a workflow goes from draft to live. For anyone building or maintaining workflows.

Opening the editor

Click Workflows in the left navigation. The main list shows every workflow in your org.

  • Create a workflow with the button in the top right.
  • Open a workflow by clicking its name.
  • Search using the box at the top of the list.
  • Filter by status (active, disabled) or last-modified date.

[SCREENSHOT] Workflow list page: a table of workflows with columns for name, status, last modified, and last execution. The "New workflow" button is in the top right.

The editor at a glance

Opening a workflow shows three areas.

The canvas fills the middle of the screen. Nodes you drag onto it appear here; drag edges between them to connect.

The node picker sits on the left. It groups nodes by type:

  • Triggers — events that start a workflow.
  • Conditions — yes/no branches.
  • Actions — what the workflow does.
  • Integrations (Slack, Philips Hue, …) — third-party nodes grouped under each service.

The inspector opens on the right when you click a node. It shows that node's settings, status, and recent executions.

[SCREENSHOT] Workflow editor with a three-node workflow on the canvas. Node picker panel labelled on the left, inspector panel labelled on the right, top toolbar with Save, Version history, and Run workflow buttons labelled, and the Enabled toggle visible next to the workflow name.

Node basics

Every node has:

  • Inputs — where edges come in. Most nodes have one input called main.
  • Outputs — where edges go out. Triggers have one, conditions have two (true and false), actions have one (main).
  • Config — the settings shown in the inspector. These drive what the node does.

Connect nodes by dragging from one node's output dot to another node's input dot.

How data flows

Every trigger carries data — the booking, the sensor reading, the schedule time. As the workflow progresses, each node can read from any earlier step using the data picker in its settings.

  • Click the link icon inside a settings field to open the picker.
  • Browse the available fields from the trigger and any upstream actions.
  • Pick the field you want; it's inserted as a chip like trigger.event.space.name.

You can also write small templates using {{ }} — for example, a Slack message body of Booking {{ trigger.event.subject }} was cancelled. inlines the subject.

See Conditions for how this feeds into branching.

Saves, versions, executions

A workflow lives in three layers:

  • The current state in the editor. What you're looking at right now. Unsaved changes are remembered until you save or reload.
  • Versions. Every save that changes the DAG (nodes/edges) creates a new immutable version with the commit message you wrote. The most recent saved version is the active one — that's what real triggers run against.
  • Executions. One per trigger event. The Executions tab on each node — and the Executions mode on the top toolbar — show every past run.

You can open older versions from Version history in the toolbar, Load them into the editor for inspection, or Make active to revert. See Publishing and versions for the full story.

[SCREENSHOT] Inspector panel for a Send Slack DM node, with the Executions tab selected. A table shows the last five executions with columns for started-at, duration, and status (success / error).

Saving your work

Click Save in the toolbar to open the Save Workflow dialog. Adjust the name, description, the Enabled toggle, and (when you've changed the DAG) the Commit message, then save. A workflow doesn't receive real triggers until Enabled is on.

There is no autosave today — leave the editor with unsaved changes and you'll be prompted before losing them.

Where to next

Related