You know how it should run.
Click it together.
The workflow builder is the heart of HR-Autopilot. You describe your process the way you already have it in your head: what the starting point is, what should happen next, what counts as an exception. Clicked together in minutes, without a line of code.
Drag the building blocks,
set the order, done.
The palette sits at the top and your workflow grows underneath it. Each building block brings its own settings. You fill in what you need and leave the rest.
- Over 30 building blocks, combine them as you like
- Every step shows the programme, the action and the values handed over
- The order can be changed at any time, even in live operation
- Automatic layout, so the view stays readable
Not a diagram.
This is the builder.
A real workflow from live operation: every evening it reads the workforce from Personio and from payroll, compares both by personnel number, carries over every difference and reports the result to the team.
Every working day at 6 pm the workflow starts on its own. Instead of a time, another system can report the start, for example when a new person has been created there.
Nobody has to remember. The reconciliation happens even in holiday season.
Reads the current workforce from the HR system. You pick the programme, the action and the field the list lands in.
No export, no retyping. The data comes straight from the source.
The same query against the second system. Two separate lists for the next block to hold against each other.
Both sides are read at the same moment. The comparison never works on stale data.
Holds both lists against each other and recognises the same person by the personnel number. The result is a list of the records that have drifted apart.
The key is yours to choose. Where there is no personnel number, use another field.
Runs through the differences one by one. Whatever sits in the branch below happens for each single entry.
One difference or four hundred: the workflow stays the same.
Carries the record over into the target system, in the format that system expects. The layer below handles the translation between the fields.
Two systems, one set of data, without anyone typing twice.
Writes a summary into the team channel: what was changed and how many records were affected.
Nobody has to check whether something happened. The information arrives by itself.
Every block has its own exit for the case where it does not get through. Here a message goes to the payroll team instead of the workflow quietly stopping.
An error stays an error, but it does not stay unnoticed.
Twenty-four building blocks.
Everything is built from these.
This is the complete list, not a selection. Every building block is set up through fields, not through code.
Functional building blocks 17
Working with systems
Involving people
Preparing data
Logical building blocks 6
Closing 1
On top of that there are variables: what one block delivers is available to the next. The list from the HR system, the list from payroll, the differences found, all visible and named. Every block also has its own error path, so a workflow never quietly stops.
Test before it counts.
Roll back if you have to.
You do not change a workflow that touches salaries on a hunch. So every change runs in test mode first, every version is kept and every change is recorded.
- A test run with real data, with nothing written
- Versioning, with every earlier version one click away
- Change log: who changed what in the workflow, and when
- Automatic retries when a programme is briefly unreachable
No brochure, no sales loop. In a few minutes you have a number you can put in front of your management.
What customers have
actually built with it.
From a one-line workflow to a nested process across six programmes, all with the same building blocks.
Passing on a change of address
Four building blocks, built in ten minutes. The typical first workflow, the one HR learns on.
Joining, with site-specific logic
Depending on the site and the contract type a different branch runs, including creating the contract and a welcome email to the team.
A promotion with an approval chain
The manager requests it, HR checks it, the board approves it, with a reminder, escalation after five days and an automatic contract change.
Before you
get started
Do I have to be able to program?
Can I test a workflow before it goes live?
What happens if I make a mistake?
What if a programme is unreachable at that moment?
How many building blocks are there?
Build your first workflow
in our call.
We do not demonstrate. You click. After 30 minutes you will know whether you want to work with it.
