The person who built your automations has gone. What now?

Everything still works, which is the confusing part. Orders sync, reminders go out, the invoices appear. The only difference is that the person who built it is gone, and nobody who remains can open any of it.

This holds until the first thing breaks. Then the question stops being administrative.

What the platform will and will not do

Start here, because it determines everything else, and the answer is often worse than people expect.

Zapier's documentation for accessing an account after a user leaves lists what it does not do, plainly. It will not "transfer ownership of Zapier accounts". It will not "update connected app accounts". It will not "transfer ownership of connected app accounts".

What remains possible depends on two things: which plan the account is on, and what role the departed person held.

On Team and Enterprise plans, if the person was a member, admin or super admin, a super admin or the account owner can transfer their workflows and update their connected app accounts. This is the good case.

On Team and Enterprise plans, if the person was the account owner, the documentation is blunt: there are no Zapier-managed solutions.

On Pro or Free plans, there is no transfer capability at all, whatever role they had.

That last line covers most small businesses, because most small businesses are on a personal plan. If your automations were built by a contractor on their own Pro account, or by an employee on the free tier with their own email, the platform will not hand them over. Not as a policy you can appeal — as a capability that does not exist.

Which means the real asset is the mailbox

The workaround the same page describes is telling. Where the departed person was the account owner, your IT administrator may be able to grant access to the email address the account was registered to, letting you reset the password and then change the address on the account.

So control does not come from the automation platform. It comes from controlling the email address the account sits on.

This is why the single most valuable thing in a handover is not documentation. It is that every business-critical account was registered to an address the business owns — ops@yourcompany.com rather than dave@gmail.com. If that is true, almost everything is recoverable. If it is not, some of it simply is not.

The trap inside a successful transfer

Say you are in the good case and the transfer works. There is a detail worth knowing before you celebrate.

Zapier documents that a webhook URL contains the owner's Zapier ID, so transferring a Zap to another user changes the URL. The receiving app has to be updated to point at the new address, or the requests keep going to the old one.

The symptom is nasty precisely because the transfer looks clean: ownership moved, the workflow is on, the dashboard is green, and data quietly stops arriving — not with an error, but with silence, because the sender is still posting somewhere that no longer routes anywhere useful.

If you transfer anything that receives webhooks, updating the URL at the sending end is part of the job, not a follow-up.

The order to work in

Inventory before you fix. What runs, where it runs, and what stops if it stops. An hour with a spreadsheet. You cannot prioritise what you cannot see, and the first breakage will not wait.

Find out what each account is registered to. For every platform: which email address, and do you control it? Sort into recoverable and not-recoverable now, while there is no emergency.

Chase the mailbox, not the platform. Where the address belongs to a former employee on your own domain, your first call is whoever administers that domain, not the vendor's support.

Check the connections, not just the workflows. An automation may transfer while the app connections it uses do not — and a workflow whose connections have gone is a workflow that will fail the next time a token expires, which may be months from now.

Rebuild the ones you cannot recover, in order of what they touch. Anything that talks to a customer or moves money first. Anything internal can wait.

Then fix the registration problem for good. Every rebuilt automation goes on an account the business owns, with the credentials somewhere more durable than one person's memory.

What to change before the next time

The reason this is expensive is almost never technical. It is that access was attached to a person rather than to the business, and nobody noticed while that person was still around.

Two habits prevent most of it. Register every business account to an address the business controls, and keep a one-page list of what runs where. Neither requires tooling, and both are the difference between an inconvenient week and a rebuild.

If you are working with a contractor now, the time to agree this is before they start, not at the end. Whose accounts will the work live on, what happens to them when the engagement ends, and what exactly gets handed over.

When the rebuild is the better option

Sometimes recovery is not worth it. If the automation was built on personal accounts, undocumented, by somebody unreachable, and it touches money or customers, the honest answer may be to rebuild it deliberately rather than reverse-engineer it under pressure.

That decision is easier with an inventory in front of you: what each process does, what it would cost to lose for a week, and which parts you could still explain if the software vanished. Producing that inventory, and separating what can be recovered from what has to be rebuilt, is one of the things a process audit does: $299, three business days, and a list you can make decisions from.

Sources

I read these pages in August 2026. Vendor documentation moves, and this is one platform's policy rather than a general rule.

What the platform cannot transfer, and what your options are by plan and role: Zapier on accessing an account after a user leaves.

Why a transferred workflow can stop receiving data: Zapier on triggering Zaps from webhooks.

Related: what you should get when an automation is handed over to you covers the planned version of this, and whose accounts does your automation actually run on? covers the question you want answered before anybody leaves.