HR workflow automation software
Set up a process once, let it run
HR automation software that starts each process on an employee or candidate event, a date or a schedule, and hands every step to the module that does it.
HR workflow automation on your company model
HR processes run on memory and checklists
Checklists are copied from spreadsheets, IT is asked in Slack, approvals sit in email threads. When a step is missed, nobody can say which one or whose it was.
HR processes you can automate with Flows
Flows automate HR processes that follow the same steps each time. Here are the processes teams automate most often. Each one runs on your company structure, so the steps adapt to each legal entity, department, and role.
- Onboarding Send contracts to sign, create accounts, and give IT, the manager, and a buddy their tasks before day one.
- Offboarding Remove access, collect equipment, and send an exit survey on dates tied to the last day.
- Probation reviews Remind the manager before probation ends and start the review automatically.
- Profile change requests Let employees request changes to their bank details or address, and send each request for approval.
- Documents to sign Send contracts and policies for signature when someone is hired, promoted, or gets a new contract.
- Recruiting steps Email candidates, move them between stages, and keep the hiring team updated.
Start each process on its event, date or schedule
A flow starts on an employee or candidate event, days before or after a date, on a schedule, or by hand. Date triggers run at the hour and timezone you choose, and overnight events wait until morning.
Hand each step to the module that does the work
Each block does real work in Skailer, and you set it up without code: a task, review, survey, signature request, approval, meeting or recognition badge. The flow waits until the step is done, and variables such as name or manager make each task personal.
Keep one flow for every entity and team
Conditions decide whether a flow starts and whether each block runs, by department, division, legal entity, location, position, years in the company or time off category. One onboarding flow can send each entity its own contract addendum.
Let employees start requests that update their profile
Use flows as approval workflows: share a flow, and it appears in the employee's profile as a request with your title, description and emoji. A Survey with approval step shows approvers each change as before and after, then saves approved values.
Use AI in the processes your flows run
When a flow sends a survey or starts a review, SK.AI can summarize the answers and highlight repeated themes, so HR doesn’t read every comment by hand. Employees and managers can also ask SK.AI about their requests and tasks, and it answers using only the data their role can see.
Find a stuck process from its step-by-step run log
Executions records every run with its employee, start time, duration and the status of each step, filtered by employee, status, period or flow. A failed run shows why on the step, and the owner gets email and Slack.
Flows run on the company model every module uses
Flows reads entities, departments, positions, managers and custom fields. Flows starts and routes the work; Tasks, Reviews, Surveys, E-sign and Approvals carry it out.
What is HR process automation in Skailer?
Flows is the HR automation and HR workflow automation software in Skailer. A flow starts on an employee or candidate event, a date such as probation end, a schedule, a manual run or an employee's request. Its steps create tasks, reviews, surveys, signature requests, approvals and meetings, give recognition badges, send email or Slack messages, and call Google Workspace or an external API. Conditions on legal entity, department, location and position target each step, and every run is logged.
SkailerA record of every run, a signature on every call
Each run is logged with every step. HTTP requests are signed, so the receiving system can check they came from Skailer. Separate permissions cover building, managing and running flows. All flow data and run logs are stored in the EU.
What the model shows for a 500-person company
NEW HIRE PROCESSING
PROBATION MANAGEMENT
DOCUMENT APPROVAL
How flows compare with other HR automation tools
Automation in HR usually lives in one of 3 places: spreadsheets and checklists, a general automation tool, or flows inside the HR platform.
| Capability | Spreadsheets & checklists | General automation tools | Skailer |
|---|---|---|---|
| What starts a process | Someone remembers | Usually events in connected apps | Events, dates, schedules, manual runs, requests |
| What a step does | A checklist line or a message | Usually a call to another app's API | Creates tasks, reviews, approvals, signatures |
| Waiting for a step | Manual follow-up | Depends on the other app reporting back | Waits for tasks, answers, approvals, signatures |
| Targeting by entity | A copy per team | Filters on synced fields | Conditions and assignee rules on one flow |
| Employee requests | Email and a form | Usually a separate form tool | Shared flows in the profile, answers saved to it |
| Run history | None | Logs kept apart from HR records | Executions per employee, with errors and cancel |
How HR workflow automation works
See how teams use Skailer
Flows in Skailer: common questions
It's the module that runs HR processes on their own. A flow starts on an employee or candidate event, a date, a schedule, a manual run or an employee's request, then creates tasks, reviews, surveys, signature requests, approvals and meetings, and sends messages.
No. Flows starts and routes the work; Tasks, Reviews, Surveys, E-sign and Approvals carry it out. A Create task step makes ordinary tasks in Tasks, and the flow waits until they are completed.
Yes. Share the flow with employees and give roles access to run it. Employees start it from their profile, and a Survey with approval step can save the approved answers to their profile.
Yes. Trigger and block conditions use department, division, legal entity, location, position and years in the company, so one flow can send different documents or tasks to each entity instead of keeping a copy per team.
Yes. Flows can start when a candidate is added, moves to a stage, is hired or disqualified, when feedback is submitted, or when an offer is approved or declined. Steps can email the candidate, move them to a stage or disqualify them.
A flow can create or delete a Google Workspace user, message people by email, in Slack or in a Slack channel, and send signed HTTP requests to your own systems. Webhooks can report when a task, an approval or a signature created by a flow is completed.
Flows is included in the Full-cycle HR plan, which starts at €12 per employee per month. The plan covers all modules and legal entities, as well as implementation and data migration.
No. HR builds flows in Skailer by choosing a trigger, adding steps, and setting conditions, without writing code. A developer is only needed if you want a flow to send requests to your own internal systems.
Yes. You can start from a ready-made flow for common processes, such as onboarding, offboarding, or probation reviews, and adjust it to your company. You can also duplicate any flow that already works.
Skailer stores flow data and run logs in the EU, in the AWS Frankfurt region. HTTP requests that flows send are signed, so your systems can check they came from Skailer. A Data Processing Agreement (DPA) is available to every customer.