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

What are workflows?

Workflows let you automate repetitive tasks — when X happens in Neowit, do Y — without writing code. For organization admins and members who want to connect Neowit events to notifications, device control, or scheduled jobs.

The big idea

A workflow is a chain of steps that runs when something happens. You build it by dropping nodes onto a canvas and drawing connections between them. There are three kinds of node:

  • Triggers — the event that starts the workflow (a booking is marked no-show, a room becomes occupied, the clock ticks over to 9 AM, …).
  • Conditions — yes/no branches that route the flow based on data from the trigger (only run if the booking was auto-booked, only fire between 08:00 and 17:00, only match this floor, …).
  • Actions — what actually happens (send a Slack message, switch on a Philips Hue light, …).

You wire them together in the order you want them to run. The workflow then waits, and every time the trigger event fires, it runs through the chain from top to bottom.

[SCREENSHOT] Workflow editor showing a simple three-node chain: a trigger on the left labelled "Booking No-Show", a condition in the middle labelled "If guest was auto-booked", and an action on the right labelled "Send Slack DM". Arrows connect left to right.

What can workflows do?

Common patterns Neowit customers use:

  • Notify someone when a bookable space is flagged no-show or stays empty past its start time.
  • Control a device (lights, HVAC scenes via Philips Hue) when a room becomes occupied or goes idle.
  • Send a daily summary to a channel at a fixed time using a schedule trigger.
  • Filter noise by combining a trigger with a condition — e.g. "send the no-show alert only for auto-booked meetings on the 3rd floor".

You can chain multiple conditions and actions. Workflows support fan-out (one trigger → multiple actions) and filtering (one trigger → condition → different actions for yes vs. no).

What workflows aren't

  • Not real-time. Triggers fire within seconds, not milliseconds.
  • Not a replacement for integrations you haven't connected yet. To send Slack messages you first need to connect Slack; for Hue lights you need to connect Philips Hue.
  • Not a general programming environment. If you hit the edge of what the provided conditions and actions can express, reach out to Neowit support — the node catalogue grows over time.

Who can build workflows?

Workflows are an admin-only feature today. An admin enables workflows for the organization, and then any admin (or a configured service account) can build and run them. See Manage access for specifics.

Next steps

Related