Automations (Flows): what they do and how they are built

Automations (flows) carry out a task on their own when something happens: for example, they create a project from an accepted quote or send a notification when stock runs low. You create and manage them under Logistics → Flows.

You build an automation on a drawing canvas from building blocks. Drag blocks from the Node Palette on the left onto the canvas and connect them with arrows.

• Trigger – the event that starts the process, such as "Quote accepted" or "Low stock level". Every automation has exactly one.
• Condition – a decision point: based on the event's data, the process continues on the Yes or the No branch.
• Action – the actual task: creating a project or task, sending a notification, requesting approval, creating an invoice draft, calling a webhook, or escalating.
• Delay – waits for a set time (minutes, hours, days) before the next step.
• Merge – brings several branches back together.

Statuses:

• Draft – editable, but not yet listening for events.
• Active – the system watches the trigger and runs the process for every matching event.
• Paused – temporarily switched off; the settings are kept.

On the automation's detail page, the Execution History table shows when it ran, what started it, and whether it succeeded.

The Flows menu item is visible to users who have the manage permission for the Automation module.