Visual canvas
Drag steps around, connect them and see the whole flow at a glance — no formulas, no code.
Draw the flow once on a canvas — a trigger, a question, a branch, a wait — and Cerqa runs it every time, on every site, without anyone remembering to.
Automations are not only about tasks. A flow can branch on an answer, wait, notify people, and log every run — tasks are simply one of the things it can do.
Every run is recorded — which path it took, what it created and who was notified.
Drag steps around, connect them and see the whole flow at a glance — no formulas, no code.
Start from a submitted form, a new hire, a shift, a schedule or a recurring time.
Split the flow by what somebody answered, so one automation covers every case.
Pause for hours or days between steps, then continue on its own.
Send the right person a notification without opening a chat or writing an email.
Every run stores the path taken and the result of each step, and never repeats an action on a retry.
Creating a task is one step among several. A flow can ask a question, follow different branches, wait, notify a manager, and only then create work — or create nothing at all if the answer says so. That is why automations live on their own canvas instead of hiding inside the task list.
Incident escalation, onboarding steps for a new hire, weekly site rounds, follow-up after an inspection: the sequences your managers repeat every week become a flow you draw once. Nobody has to remember it, and nothing depends on the one person who usually chases it.
Each step is claimed before it runs, so a retry can never create the same task twice. Draft flows are saved without validation; before a flow can be turned on, Cerqa flags every step that is missing something right on the canvas.
Before you commit to any workforce software, get these points in writing — from us and from every other vendor. Our answers are below; we go deeper in the demo.
Yes. We provide a DPA under Art. 28 GDPR and sign it with you before your team starts using the app.
Hosting and database run on Supabase. The exact region and the sub-processor list are set out in writing in the DPA — not only on request.
Location sharing is opt-in per person — refuse it and clock-ins still record, just without coordinates. Reporting and access scope can be restricted per role. The contested points are settings you negotiate concretely in a works agreement.
Time and absence records stay for the legal retention period, then are deleted. All core and time data exports as CSV/Excel — you take your data with you when you switch.
No. A flow can branch, wait, notify people and log the run. Creating a task is one of several steps.
No. You place steps on a canvas and connect them; each step is configured with plain fields.
A submitted form, a new hire, a shift, a schedule or a recurring time.
Yes. A dry run shows which path the flow would take without creating anything, and incomplete steps are highlighted on the canvas.