Process builder
Trigger, steps, conditions and owners on one canvas. No scripting, no consultant.
Flows
Build the process once. It runs itself after that.
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.
Process builder
This is a flow. The whole thing.
An event at the top starts it, a guard decides who it applies to, and everything under it follows — in order down a branch, and in parallel across them, which is the point: the welcome email is already out while IT is still ordering the laptop. Automatic steps run the moment the one above them finishes. Steps that belong to a person land in their list with a deadline. A condition reads a field you already hold and takes one leg or the other. Nothing here is written in a scripting language, and nothing here is a diagram of the process kept up to date on the side — it is the process.
Active
Run
Save
Draft v3 · Active v2
Access · HR Administrator, Manager
An employee joins the companyTrigger · fires the moment it happens
Whenemployee.joinedGuardEmployee type = Full-time
Send welcome emailTo the employee · Welcome aboard
DelayPauses this branch
Wait3 days
Send check-in surveyTo the employee · How is week one going?
Create task — Prepare equipmentAssigned to the IT team · due before day one
WaitHolds until an event arrives
UntilTask completedTimeout7 days · fail branch
ConditionBranches on data you already hold
IfDepartment = Retail
Matches
Create task — Order uniformAssigned to the store manager
Otherwise
Send email — Office guideTo the employee · Office guide
Trigger
The event that starts it. The guard under it narrows the field — this one runs for full-time hires and nobody else.
Send email
To the employee, the manager or anyone else on the record. The address comes from the record, so there is no list to keep.
Create task
Lands in a named person's or team's list with a due date. Overdue tasks escalate to the manager rather than sit there.
Delay
Pauses one branch for a set time. Three days after the welcome email, the check-in survey goes out on its own.
Wait
Holds the branch until something actually happens — the equipment task is closed. Nothing within seven days and it takes the fail branch.
Condition
Reads a field you already hold and picks a leg. Retail gets a uniform ordered; everyone else gets the office guide.
- Triggers on events that already exist — someone joins, resigns, changes team or has a contract amended
- A guard on the trigger, so one flow does not have to serve everybody
- Branches that run side by side rather than one long queue
- Delay pauses a branch for a set time; Wait holds it until a task is actually finished
- Conditions branch on department, employment type, location or pay group
- A draft version beside the running one, and named roles that may edit either
An example
Mikkel starts in the Aarhus shop on Monday.
Nobody in HR opens Komma that morning. The flow above fired when his record was saved as a full-time hire, and it split immediately: the welcome email went out, and the IT team got a task for his equipment. Three days later the check-in survey followed on its own. When IT closed the equipment task, the condition read his department, saw Retail, and ordered a uniform instead of sending him the office guide. The run is below, with a time and a name on every line.
- It starts on the record, not on someone remembering — 09:12, the moment the hire was saved
- Two branches at once: he hears from you while IT is still ordering the equipment
- The wait step releases when IT closes the task, not when a date passes
- Retail got a uniform; everyone else gets the office guide — same flow, one condition
- The leg that was not taken is on the run too, so a branch can be read after the fact
- Automatic steps logged as the flow, the equipment task as the person who closed it
MS
Mikkel SørensenSales assistant · Retail, Aarhus
Done
Day 109:12Flow startedEmployee type = Full-timeTrigger
Day 109:12Send welcome emailSent to MikkelFlow
Day 109:12Create task — Prepare equipmentDue before day oneIT team
Day 314:30Task completedEquipment handed overLucas Berg
Day 314:30ConditionDepartment = Retail · matchesFlow
Day 314:31Create task — Order uniformAssigned to the store managerFlow
Day 409:12Send check-in survey3 days after the welcome emailFlow
—Send email — Office guideNot sent · the other leg ranOtherwise
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 — the accounts that stay open, the equipment nobody asked for, the final pay line. Both are shipped as templates you can take apart rather than as a fixed sequence.
- Onboarding starts when the candidate is marked hired, not when someone remembers
- Contract out for signing, accounts requested and equipment ordered as steps in the chain
- A 30-day plan the new colleague sees in the app, not a document they never open
- Offboarding closes access, collects equipment and hands the final pay line to payroll
- Templates per department, so a shift-based hire and an office hire differ where they should
Active flows
18
7 built from templates
Running now
43
across 6 departments
Steps done automatically
71%
of all steps this month
FlowStatusIn progress
ONOnboarding — office #f1Running12 people
ONOnboarding — shift work #f2Running9 people
OFOffboarding #f3Running3 people
CTContract amendment #f4PausedAwaiting HR
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 owes the next one and how long it has been sitting there. Nothing a flow does is anonymous: the automatic steps are logged as the flow, the human ones as the person, and both land in the same audit trail as every other change in Komma.
- A run view per employee, showing the step it is on and who owes it
- 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
Steps overdue
4
2 escalated
Median run
6 days
onboarding, end to end
Logged this month
1.284
steps, all attributed
EmployeeStepState
FHFrederik Holm #4Step 6 of 9On time
NJNoah Jensen #10Step 3 of 9Overdue 2 days
SLSofie Lund #1DoneRan 6 days
ENEmma Nielsen #3Step 2 of 7Waiting on IT
What is in it
Flows, in full
Onboarding
Starts when the candidate is marked hired and runs for the first 30 days.
Offboarding
Access closed, equipment collected, final pay line handed to payroll.
Deadlines
A due date and a reminder on every step that waits for a person.
Templates
Ship a flow per department, then take the template apart where it does not fit.
Audit trail
Automatic steps logged as the flow, human steps as the person — same log as everything else.
See it on your own data.
A 30-minute walkthrough with someone who knows the module — and your org structure, not a demo tenant.