Illizeo’s workflow builder draws a graph: trigger, approvals, conditions, notifications, actions, end. Here is what it can do — and what actually executes today.
Advanced patterns #
| Node type | Role in the graph |
|---|---|
| Trigger | The entry point. Exactly one per graph — a graph with none, or two, is refused on save. |
| Approval | An approval step, with its approver and its own delays. |
| Condition | The branch. |
| Notification | A message sent mid-circuit. |
| Action | An effect internal to Illizeo. |
| End | The exit. |
Step-by-step #
-
Start from a template and a category #
The builder offers predefined templates and categories (absences, attendance, expense reports…). The category determines what the circuit handles.
-
Place the nodes and connect them #
The graph is validated on save: an orphan node or a missing trigger is refused with an explicit message, rather than accepted and broken at runtime.
-
Set the auto-approval thresholds #
This is the conditional branch that earns its keep, and it is already wired: an absence below a number of days, an expense below an amount, go through without approval. Above, they are routed.
-
Chain sequential steps #
A two-step chain opens the second as soon as the first is confirmed, and the request stays pending until the last one answers.
-
Check on a real request #
There is no simulator. You verify by creating a test request and following its path through the approvals screen.
FAQ #
Does the visual builder really drive day-to-day approvals?
Not fully yet. Absence, attendance and expense approvals run today on the historical approval circuit — that is what carries the auto-approval thresholds, the sequential chains, delegation, reminders and escalations. The graph engine is functional but deliberately held back. In other words: what you draw does not yet replace what runs.
Can two signatures be required above an amount?
A two-step sequential chain exists. Conditionally triggering a second signature based on the amount is not an available setting as things stand.
Can one workflow call another?
No. There are no sub-workflows.
Can an external action be wired in?
No. None of Illizeo’s eight connectors can be driven from a step, and there is no outbound webhook.
Which protections hold whatever you draw?
Nobody approves their own request, even holding the right to bypass approval. Delegating to yourself is refused. And an insufficient absence balance can block the request, where that check is enabled.
What does not exist #
No “advanced mode” to switch on in the editor. No branch simulator. No sub-workflows. No return loop capped at a number of iterations. No PDF export of the business rules. No call to an external system from a step.
See Integrations and API #
Learn to plug external actions into your workflows.
