What is a workflow?

A workflow is a flowchart that runs automatically when something happens in one of your tables — for example, when a leave application is created, or when an order's status changes to submitted.

Workflows let you wire up approval flows, notifications, and small automations without writing code.

How workflows fit in

Every workflow belongs to one table. When the table sees a matching event (a record is created, updated, or its status changes), the workflow starts running.

A workflow is built from nodes connected by edges:

Start — where the flow begins. Every workflow has exactly one.
Decision — branches based on a condition (e.g. days requested > 5).
Approval Task — pauses the flow and asks a person to approve or reject. The flow continues based on what they decide.
Action — does something automatic: send an email, update a field, call a webhook.
End — terminates the flow. You can have multiple End nodes (e.g. Approved, Rejected).

Glossary

Trigger — the event that starts a workflow (record.created, record.updated, record.status_changed).
Condition — a rule on a Decision node, like status = "submitted" AND days > 3.
Assignee — the person, role, or rule that decides who handles an Approval Task.
Fallback edge — the route a Decision takes when no other condition matches. Every Decision must have one, otherwise the flow can get stuck.
Action — anything the workflow does on its own (email, field update, webhook). No human in the loop.

Where to next

Step-by-step: configure a leave approval workflow — guided walkthrough
Common mistakes — things that bite people the first time