In short: The risk is whose name is on the account, the connected apps and the inbox that receives errors. Zapier will not transfer an account when the leaver was the owner or the plan is Pro or Free. Other products differ. Inventory the workflows before you revoke access.
The risky part of an automation is rarely the logo on the tool. It is whose name is on the account, whose password is on the connected app, and whose inbox receives the error. When that person leaves, the workflow can keep running unseen, or it can stop, and you will not know which until a customer does.
A public post by someone who described themselves as newly responsible for an existing account, not as the owner, asked how to start without making a large undocumented set of workflows worse. A comment visible as a search excerpt had the builder admitting they had not documented what they made. Another comment, from an account whose name reads like a vendor, advised an audit before a rebuild. The opening post was the part fetched in full. Comments are excerpts. Use them as a warning about documentation, not as a method you must copy.
This checklist is the practical meaning of ownership. It is not legal advice about intellectual property. FYAdvisers is not a law firm. What a contract should say about copyright in a workflow is for your adviser. What follows is what breaks on a Monday if you skip it.
Five layers, and none of them is optional
| Layer | What you think you own | What you actually need |
|---|---|---|
| Platform account | “We use Zapier” | A company email as the owner or a role that can transfer assets, plus MFA recovery the company holds |
| Connected apps | “It talks to Xero and the mailbox” | A list of which login each connection uses, and a way to replace that login |
| Error inbox | “We get emails if it fails” | A mailbox the company will still read after the builder leaves |
| Documentation | “It’s obvious” | One row per workflow a deputy can follow |
| Business owner | “IT looks after tools” | A person who knows what the workflow is for, and may turn it off |
Miss any layer and the others do not save you. A perfect diagram in a shared drive does not help if the only admin login is a personal Gmail you cannot reset.
Staff access removal is a related but different job. The offboarding guide is about identity, apps and devices. This page is about the automations those people leave behind. Do both. Revoking access before you have moved the workflows is how you discover, too late, which invoices depended on them.
What Zapier’s own help says
Zapier’s article “How do I access an account after a user leaves?”, updated 29 May 2026, is specific. It does not describe Make, n8n or Power Automate. For those, open the vendor’s current document. Do not assume this policy travels.
Zapier says it cannot, as a general rule, grant another person access to a user’s account, transfer ownership of that account, or update its connected app accounts. Whether you can do something narrower depends on the plan and your role.
- If the leaver was a member, admin or super admin, another super admin or the account owner can transfer ownership of that member’s Zaps and update their connected app accounts. The page also says the account owner can do this for a member or admin.
- If the leaver was the owner of the account, Zapier says it cannot transfer ownership of the account, update connected app accounts, or transfer those connected accounts. The route it describes is organisational: if you control the email address the Zapier account was registered to, reset the password and consider changing the email.
- On a Pro or Free plan, Zapier says it cannot transfer the account or the connected app accounts. The same email-recovery route is what the page offers.
Read that twice before you let a freelancer build “in their Zapier”. If they are the owner of a Pro or Free account, you do not have a transfer button. You have a hope that they will cooperate, or that you control the mailbox.
Error mail is the second Zapier fact that belongs in a handover. The notifications article, also updated 29 May 2026, says errors go to the Zapier account email by default. Frequency can be immediate, a summary, or Never, which Zapier marks as not recommended. Zapier will not send an error email when an error handler runs. If the account email is the leaver’s personal address, the company may already be on “Never” without having chosen it. The maintenance guide covers what to do when a run fails. It cannot help if the only alert went to a closed mailbox. A run that never starts is a further gap: an error email does not fire if the trigger never arrives. That limit is why a periodic check that expected work appeared still belongs to a person.
The handover list
Do this while the person is still employed or still on the contract. Afterwards is the next section, and it is worse.
- Put the platform owner on a company email the company can reset.
- Store MFA recovery codes with a second company admin, not in the builder’s password manager alone.
- List every connection: app, the login name, whether it is a company user or a personal one, and the date the token was last replaced.
- Point error notifications at a shared inbox more than one person reads. On Zapier, confirm the frequency is not Never.
- For each workflow, fill the inventory row below. One row. Plain language.
- Export or duplicate what the product allows, into a company-owned place. A screenshot is not an export.
- Confirm a second person can disable the workflow without the builder.
- Agree the moment access is revoked: after a test by the deputy, not before.
- Remove the leaver from the platform, from shared folders of credentials, and from the connected apps that were theirs.
- Change any password they knew for a shared mailbox used as a trigger. Then confirm the workflow still runs with the new secret. This is the step teams skip and then call the tool broken.
- Write a one-line change log: who changed the rule, when, and why. The retention guide is about how long to keep records. A change log is the record of the rule itself.
- Name the business owner who may retire the workflow. A tool admin is not that person by default.
- If a freelancer built it, match this list to the scope in the hire guide. Build-in-our-account is a commercial term, not a courtesy.
- If the workflow writes to accounting or sends mail, run one witnessed item after the transfer and compare it with the last item from before. Same business key, no duplicate.
- Book the next review. A departure is not the only time an account drifts back to a personal login.
Inventory row
Copy this table once per workflow. Keep it where the deputy can open it without the builder’s laptop.
| Field | Write this |
|---|---|
| Name | What the team calls it, not only the vendor’s title |
| Trigger | The event, and which account emits it |
| What it does | Three sentences a new hire could read |
| Apps and logins | Each connection and the login name |
| If it stops | Who is affected on day one, and what they will notice |
| How you know it is working | A record you can look up, not “it usually runs” |
| Business owner | A person, not a department |
| Last tested | Date and who watched |
If they have already gone
Do not start by switching workflows off. You do not yet know which quiet ones are holding up invoices.
- List who consumes the outputs: finance, the warehouse, a customer inbox.
- Match those outputs to workflows, using names, folders and the last successful run if you can still see history.
- Triage anything that takes money, sends a customer message, or grants access. Those are first.
- For each, decide keep, fix or retire. Retire is allowed. An undocumented workflow that nobody can explain is a liability, not an asset.
- Only then revoke what you can still revoke.
Where the platform allows a transfer of the member’s workflows, do that before you delete the user. Where it does not, the email-recovery path above is Zapier’s documented route for owner and Pro or Free accounts. If you do not control the mailbox, you are asking the former person for help. That is a relationship problem the software will not solve. Say so internally early.
A comment on the inherited-account thread advised auditing before rebuilding. That is consistent with this order. Rebuilding first, because the old design embarrasses you, is how you run two versions.
What to require from a freelancer or an agency
Put the company account, the inventory rows and the error inbox in the statement of work, not in a handover email on the last Friday. The cost guide already treats export and access transfer as acceptance tests before the final invoice. Use them. A builder who will only work in their own tenant is telling you the ownership answer in advance.
What to ask each product, since only Zapier was checked
Send the same questions to Make, n8n, Power Automate or any other tool. Do not fill the answers in from this page.
| Question | Why it matters |
|---|---|
| Can an admin transfer a member’s workflows to another member? | This is the difference between a Tuesday task and a recovery project |
| What if the leaver is the owner of the tenant? | Zapier’s answer is no transfer. Another vendor may differ |
| Which mailbox receives failures, and can it be a shared mailbox? | A personal inbox is a silent offboarding |
| Can error mail be switched off, and is that the current setting? | Zapier allows Never, and says it is not recommended |
| Does an error handler suppress the alert? | On Zapier, an error handler means no error email |
| How do you export the workflow definition? | A screenshot will not restore it |
| What happens to in-flight runs if you disable the user? | You want this answer before you click disable |
Write the replies next to the inventory. A blank cell is a reason not to revoke access yet.
Illustrative scenario
Illustrative scenario, not a client. An office manager built the company’s reminders and invoice filing while signed into a platform with a personal Gmail, on a plan that does not allow account transfer. They resign. The company can still read the shared drive where a few notes were kept. It cannot reset the platform. One connected mailbox was a company shared inbox, so that trigger can be recreated. One connection used the manager’s personal login to a supplier portal. That connection cannot be recovered from the notes. The company recreates the internal reminders in a new company-owned account, retires the supplier-portal step until someone has a proper login, and does not discover this by turning the old workflows off first. Nothing in the story is a measured saving. The point is which item was unrecoverable.
Limits
Zapier’s pages were read for this article and can change. Make, n8n and Microsoft are not given a policy here because their documents were not the ones checked for account transfer. Personal data in the workflows still sits under the company’s other duties. This checklist does not replace the offboarding guide and does not assign copyright.
The same file applies when the builder is an AI or RPA firm: questions to ask an AI agency and hiring an RPA consultant.
To list one account before someone leaves, use the workflow service or WhatsApp +65 9071 3976 (chat).
Frequently asked questions
Can Zapier transfer an ex-employee's account to us?
Zapier's help page, updated 29 May 2026, says Zapier cannot grant another person access to a user's account, transfer ownership of that account, or update its connected app accounts, except where your role and plan allow a narrower transfer. If the person was a member, admin or super admin, an owner or another super admin can transfer that member's Zaps and update their connected app accounts. If the person was the account owner, or the plan is Pro or Free, Zapier says it cannot transfer the account or the connected apps. Recovery is then through the email address the account was registered to, if your organisation controls that mailbox.
Should automations run under one shared login?
Prefer a company-owned admin and named users. A shared password looks simple and becomes the thing you cannot revoke without breaking every workflow. The business email on the platform account, with MFA recovery held by the company, is the control.
Does this have anything to do with the PDPA?
If the workflows move personal data, access control is part of protecting that data. The offboarding guide covers closing a leaver's access to business systems. This page is about the automation assets themselves. It is not a full data-protection programme.
How often should we review ownership?
At every departure of someone who built or administered a workflow, and on a calendar you choose, such as when you renew the tool. There is no statutory interval for this review.
