For Personio and Google Workspace
With idenflow, every hire, move and exit in Personio becomes a plan for Google Workspace, with no ticket in between. You decide what needs approval.
| Person | PersonioHR record | Google WorkspaceAccounts, groups, OUs |
|---|---|---|
| Anna Schmidt | active | account active |
| Felix Schäfer | activeleftlast working day 14 Nov | account activeaccount suspended |
|
Plan · exit · 14 Nov, CET
|
||
| Sophie Wagner | active | account active |
Audit log
Today
What HR enters in Personio reaches Google Workspace only if someone remembers it.
HR enters the exit in Personio.
Someone writes a ticket, often confidential.
Someone else reads it when there's time.
IT does it all by hand.
One step slips. The account stays active.
With idenflow
For idenflow, the entry in Personio is the message to IT.
HR enters a hire, move or exit as usual.
Every difference shows as a change, with its old and new value.
New rules wait for your approval. Auto rules write without a click.
Every step is logged: when, by whom, person or system.
On your schedule, the playbook signs out everywhere, removes licences and suspends the account.
Clara Kochlast working day 21 Nov
Account suspended
The account is created on your schedule, with groups from your rules.
Emilia Kleinemilia.klein
ready
Your rules re-plan groups, OU and manager.
Hannah ZimmermannDepartmentSales → Marketing
Schematic, with made-up data.
Calculator
With your numbers, worked out in your browser; nothing is stored or sent.
11 days
of access to your Google Workspace for people who had left, by your numbers, added up per year.
How it is calculated: 15 exits × 1 of 10 × 7 days · All assumptions and sources
Demo
With made-up data and no sign-in; nothing you do there is sent.
Justus-Constantin Weidhaus
Founder of idenflow.com
Weidhaus, a sole proprietorship in Germany
LinkedIn
Why idenflow exists
For more than eight years I have worked with Google Workspace, for companies such as HelloFresh: first as an IT manager, later as product owner. Today, as a freelancer, I set up and run Google Workspace for new clients.
At HelloFresh I saw how fast a company can grow:
about 5,000 employees when I started, and 25,000 user accounts when I left.
In Germany alone, around 50 people joined in a typical month and 10 to 25 left. Done by hand, every one of those cases is a ticket: written, read, carried out in the Admin console. Things are easily forgotten. And an exit handled too late is a security risk.
Over the years I have administered IT, led it and automated it, always working closely with HR and management. I know Personio from working with HR, and Google Workspace from running it.
That is how I saw the gap: Personio knows who joins, moves and leaves. In Google Workspace, someone has to carry it out. And nobody owns that hand-over.
At my next employer, again on Personio and Google Workspace, I started closing that gap. A rudimentary version of idenflow that I had set up in the meantime ran there: Google followed Personio, with no ticket in between.
Alongside it ran a tool of my own that backs up leavers' mail and Drive from Google Vault before the licence goes. As of November 2026, the tool had completed 267 of 269 accounts and backed up 5.2 TB in about 4.8 million emails and files. The licences it freed up cost about €29,800 a year.
My goal is to save as many companies as possible the time these tickets take, so they can focus on what matters. That is why I rebuilt idenflow from scratch: for many companies, not just one.
I build and run it myself. When you get in touch, you talk to me.
Free check
You connect Personio and Google Workspace and see where the two do not match.
Status: built and tested, not yet in use at any customer. We will offer the free check once idenflow runs in production; you can request it now. To hear when idenflow is available, join the waitlist.
Pricing is on request during the pilot phase. Write to us through the form. You can work out above what slips through at your company today, with your own numbers.
No. The connection runs directly from Personio to Google Workspace. Single sign-on and multi-factor sign-in for other apps are not part of idenflow; for those, an identity platform remains the right tool.
Yes, with general automation tools. You then add approvals, safety limits and logging to every flow yourself, and whoever built your API calls maintains them when Personio or Google change. In idenflow, all three are built in.
Personio is the reference, so a wrong value becomes a planned change. If the rule is on review, you reject it; it does not come back while nothing changes. The fix goes into Personio.
From Personio, core data such as name, status, start and leaving dates, department and manager; from Google, a copy of each account's directory record. For data protection and the works council, idenflow generates a system description from your configuration.
The app's interface is in English for now. Mail templates are kept per language, and each person gets the one in their language, or the English one otherwise.
