A person confirms the irreversible ones
Put an approval step before access is removed or anything reaches an employee. The run waits, and carries on once someone approves or rejects it.
Lodol runs the work around every hire and every departure, across BambooHR, Okta, Slack, Gmail and the rest of your stack, while your HR system stays exactly where it is. The steps that matter wait for a person.
Free to start, no credit card. Not priced per employee, and every plan has unlimited seats.
List changed employeesBambooHRNew hire found: Design team, starts Oct 13
Add eventGoogle CalendarFirst-day 1:1 with her manager, 10:00
Send messageGmailWelcome email with where to go on Monday
Send a message to a channelSlack#team: say hello to Amara on MondayNo migration and no new system for employees to learn. Lodol picks the work up where it starts and finishes it in the tools your team, IT and managers already use.
Someone's hired
A new hire in your HR system or ATS starts the work, with nothing typed twice.
Accounts get set up
Accounts, groups and the laptop request, ready before day one.
People get told
A welcome email, calendar invites and a hello in the team channel.
Paperwork gets done
Policies sent for signature, acknowledgements collected, reminders until done.
Someone leaves
Access removed and sessions ended, once a person confirms.
940 apps and 11,056 actions in all, and a workflow can call any other tool’s API directly, so nothing has to move for Lodol to fit in.
Explore all integrationsBuilt and tested by our team for the people side of the business, with fairness written in. Open one, connect your apps, and it runs.
Every Monday, emails anyone starting in the next week and tells the team in Slack who is joining.
Written from the roster, not by AI, so there's nothing to get confidently wrong. Nobody is welcomed twice.
Open this workflowReads each job application that lands in Gmail, adds the candidate's details as a row in your Google Sheet and tells your team in Slack.
Told to extract, not judge. It never records age, gender, ethnicity or anything unrelated to the work.
Open this workflowReads new applications each day and writes preparation notes against your role brief for a person to review.
Never recommends hiring, rejecting or ranking anyone. It says what isn't evidenced rather than inferring it.
Open this workflowReads a CV PDF and writes what it says onto a fresh copy of your own Google Docs CV template.
No writing step: every word comes from the CV. Date of birth, nationality and photos never come across.
Open this workflowEvery Monday, the week's feedback form responses summarized for HR and emailed, then cleared from the sheet.
Harassment, safety or distress goes to 'Needs attention now' at the top, never averaged into a theme.
Open this workflowTotals the clock-in and clock-out times your team logs themselves into a weekly hours summary per person.
An entry it can't read is reported with its row number, never counted as zero.
Open this workflowEnboarder, Wisq and Applaud automate HR on top of your HR system, the way Lodol does, and they are good at it. Here is how they compare on what a people team weighs.
| What a team asks | Enboarder | Wisq | Applaud | |
|---|---|---|---|---|
| Published pricing | Yes. Free, or from $18 a month; never per employee | No. Custom quote | No. Not published | No. Per user, from 500 users; by quote |
| Try it without a sales call | Yes. Free plan, no card | No. Demo only | No. Demo only | No. Demo only |
| Works with your HR system | BambooHR and Zoho People; others read through Finch | 120+ ATS and HRIS; logos include Workday and BambooHR | Workday, UKG, SuccessFactors, ADP and Dayforce | Workday, SAP, Oracle and ADP |
| Build and change your own workflows | Yes. Any trigger, any steps, across your apps | Yes. Workflow builder and AI Journey Builder | Yes. Agent Studio, though Wisq's team does the building | Yes. No-code builder; HR builds its own |
| Acts on accounts and IT ticketsYour identity provider and IT service desk. | Yes. Okta and Entra accounts; Freshservice and Jira tickets | Yes. IT provisioning via ServiceNow, Jira and Okta | Partly. Works with ServiceNow and Jira; coordinates access removal | Partly. Tickets in your IT desk; Okta and Entra for sign-in |
| Employee HR assistant in Slack or chat | Yes. Deploy your own assistant in Slack, Discord or Telegram | Partly. Assistants inside journeys; nudges in Slack and Teams | Yes. Harper, in Slack, Teams and email | Yes. In Teams, Slack and WhatsApp |
| Built for HR out of the box | Partly. HR templates, on the AI model you choose | Yes. Best-practice journeys, curated by its team | Yes. HR-trained models and pre-built HR workflows | Yes. HR portal, knowledge base and case management |
| A person signs off on the risky steps | Yes. Any step waits for a person; every run traced | Yes. People approve AI output; audit trails | Yes. Approval steps and a full audit trail | Yes. Workflow approvals; every AI chat logged |
If you want a ready-made HR service desk, with an HR-trained assistant, best-practice journeys and an enterprise rollout to match, Enboarder, Wisq and Applaud are built for that. If you want the work around every hire and every departure to run across the tools you already use, priced by runs and started today, that is Lodol.
From each company’s own website, checked October 2026. Products change; if something here has, tell us and we will correct it.
Removing someone's access, sending an offer, changing a record: any step can stop and wait for the person who owns it. Every run is on the record.
Put an approval step before access is removed or anything reaches an employee. The run waits, and carries on once someone approves or rejects it.
Every edit is a version. Open any one to see what changed, and restore it in a click.
Owner, admin or member, per person, so the workflows that touch personal data are edited only by the people who should.
Every run is traced step by step, so when someone asks whether a leaver's access was removed, and when, the answer is on the record.
No. Lodol works alongside the HR system you have. BambooHR and Zoho People are built in, from new hires and changed employees to time off, and so are Workable and Zoho Recruit for hiring. Payroll and HR data from many other systems can be read through Finch, and anything with an API can be reached with a Call an API step.
Yes, in Okta and Microsoft Entra ID: create users, add them to groups, deactivate them and end their sessions. If Okta already provisions accounts from BambooHR, keep that, and use Lodol for everything around it: the approvals, the IT ticket, the emails and the calendar invites.
No. The recruiting templates are built to extract, not judge: they never recommend hiring, rejecting or ranking anyone, and never record age, gender, ethnicity or anything unrelated to the work. Decisions stay with people. Check your local rules on automated hiring tools before you automate any screening.
When you decide. A workflow can run on each person's last day at the time you set, ask the right person to confirm, then remove their access in Okta or Microsoft Entra ID and tell IT. If your identity provider already removes access on its own, keep that, and let Lodol run the steps around it.
Credentials are encrypted in transit and at rest. Roles decide who can run, edit and manage each workflow, so the ones that touch personal data are changed only by the people who should, and every run is recorded step by step. AI steps run on your own model key, under your provider's terms.
Not per employee. Free includes 200 runs a month. Builder starts at $18 a month for 2,500 runs and Pro at $120 for 10,000, and every plan has unlimited seats. A run counts once, however many steps it takes. Pro adds advanced permissions and an activity audit log you can export.
Open the new-starter workflow, point it at your roster and see Monday's welcomes go out. Free to start, no credit card.
Free plan, no credit card · Credentials encrypted in transit and at rest · Security and trust