This happens all the time at Zapier: someone builds a Zap for themselves, and then the whole team wants it. If you started a Zap in your own account and need it on your team's, you can now copy it to another Zapier account instead of rebuilding it by hand. Tables, Forms, Interfaces, Chatbots, and Agents copy over, too.
Copy a Zap to another account
It takes five steps, and you review the changes before anything is copied.
Select the assets on your Assets page, or open one asset's row menu.
Click Copy to another account.
Pick the destination in the Select a destination account dialog, then click Continue.
Choose a folder, or click + Create new folder.
Click Continue to review, then click Copy.
The Help Center guide has the full steps.
Check these before you turn a copy on
A copy starts fresh: it has no run history or usage data, and the original keeps its own. It also takes the permissions of the folder you put it in, which may not match the original's.
Connections. A copied Zap comes with placeholder connections. The Connect your apps dialog lets you pick an existing connection or connect a new account for each app.
Turned off. A copied Zap or agent arrives turned off, so nothing runs until you turn it on.
Webhook URLs. If a copied Zap uses Webhooks by Zapier, its webhook URL changes, so update anything that sends data to the old one.
Related assets. A Table that a Zap uses doesn't come along automatically, so copy it too.
Global variables. Zapier swaps them for their current values at the time of copying.
What you need
You can copy to any account you belong to, as long as you have View access to what you're copying. Agents have to be in a folder first, and if your account uses SAML single sign-on, an admin needs to provision your account in your company's identity provider.
