Automation
What follows the submission, and what proves it
Automation is worth something only if you can check that it happened. Six step types, a condition on each, and a log that says what was attempted, when, with what result.
15 days • 10 users • no card required
The steps
Six types, combinable
Change the submission's status, generate a document, send an email, assign it to someone, ask for approval, call a webhook.
- Approval has a deadline
- The manager receives the request, decides from their decision inbox, and the rest follows. A delay is visible rather than guessed at.
- Assignment pushes a prefilled form
- A recorded defect creates the colleague's service sheet, already filled with what is known, on their phone.
- The webhook talks to your systems
- Signed, retried, logged — and refused if it points at an internal address, which would be a door into your own network.
The conditions
A condition per step, written like a calculation
The same expression engine as the forms. What you can write in a calculated field, you can write in a step condition.
- On the submission's values
- "If the check failed", "if the amount exceeds ten thousand euros", "if the customer is this one".
- Checked on save
- A condition that does not compile is not saved: a workflow does not break the first time it is used.
- Readable by whoever wrote it
- No hidden language and no invisible branch: a workflow is a list of steps with their conditions, in order.
The proof
A log, step by step
Every run can be read: the step, its result, its error message if there is one. A failed step is retried without replaying the others.
- A network failure is retried
- A drop or a briefly unavailable server does not cancel the workflow: it goes again.
- A permanent failure says so at once
- A missing template or a refused address gains nothing from three retries: the error is returned with its reason.
- Nothing happens quietly
- If an email did not go out, the console knows and tells you. That is the opposite of automation whose absence you learn about from the customer.
The first workflow takes five minutes
"Submission sent" then "generate the document" then "send the email": three steps, and the evening report goes out without anyone thinking about it.