Build the processonce.It runs itself.
A flow is a trigger, a chain of steps and a named owner for each of them. Mark a candidate hired and onboarding starts on its own — the record, the contract, the accounts and the first-day plan — because it is the same employee data underneath, not an integration.
With a link to each failed runApprove
Process builder
This is a flow. The whole thing.
An event starts it, a guard decides who it applies to, and everything under it follows: in order down a branch, in parallel across them. No scripting language, and no diagram kept up to date on the side. It is the process.
- 1Two branches at once: the welcome email is out while IT prepares the equipment.
1234- 2The trigger starts the moment someone joins. The guard lets full-time hires through, nobody else.
- 3Wait holds until the equipment task is done. Nothing in 7 days and it takes the fail branch.
- 4A condition on data you already hold: Department = Retail.
An example
Mikkel starts in the Aarhus shop on Monday.
Nobody in HR opens Komma that morning. The flow above started when his record was saved as a full-time hire. This is the run, with a time and a name on every line.
- Day 1, 09:12 · The hire is savedThe flow starts on the record, not on someone remembering. Employee type is full-time, so the guard lets it through.
- Day 1, 09:12 · Two branches at onceThe welcome email goes to Mikkel, and the IT team gets a task to prepare his equipment, due before day one.
- Day 3, 14:30 · IT closes the taskLucas Berg hands the equipment over. The wait step releases on that event, not when a date passes.
- Day 3, 14:31 · The condition reads RetailDepartment = Retail matches, so the store manager gets a task to order a uniform.
- Day 4, 09:12 · The check-in surveyThree days after the welcome email, “How is week one going?” goes out on its own.
- On the run · The leg not takenThe office guide was not sent, and the run says so. Automatic steps are logged as the flow, the equipment task as the person who closed it.
Onboarding and offboarding
The two processes everyone does badly by hand.
Onboarding starts before day one and does not stop after the first week. Offboarding is the same chain read backwards, and it is the one that gets forgotten. Both ship as templates you can take apart.
- It starts on the hireOnboarding starts when the candidate is marked hired, not when someone remembers.
- Steps in the chainContract out for signing, accounts requested and equipment ordered, each a step with an owner.
- A 30-day plan in the appThe new colleague sees the plan in the app, not in a document they never open.
- Offboarding, read backwardsAccess closed, equipment collected and the final pay line handed to payroll.
- Templates per departmentA shift-based hire and an office hire differ where they should.
Ownership and the audit log
Every step has a name on it and a time it was done.
An automated process is only worth having if you can see where it stopped. Each run shows which step it is on, who it is waiting for and how long it has been sitting there.
- A run view per employee, showing the step it is on and who it is waiting for
- Overdue steps escalate to the manager rather than dying quietly
- Automatic steps are logged as the flow, human steps as the person
- The same audit trail as the rest of the platform, one place to look
- Karma can draft a flow from how you describe it, but a person approves it
123- 111 runs live right now, 3 parked on a delay or an event.
- 22 failed in the last 24 hours, flagged for attention.
- 3Each run shows the step it is on: Ashton Morgan, 1 of 5, create account.
What is in it
Flows, in full.
See it on your own data.
A 30-minute walkthrough with someone who knows the module, and your org structure, not a demo tenant.