Skip to main content
Platform security guideReviewed

Is Zapier safe? What Zapier's own pages say, and how to review your Zaps

This guide does not hand Zapier a pass or a fail.

It sets out what Zapier's documentation says about connected accounts, the data kept in Zap history, webhook URLs, sharing and offboarding, each credited to the article that says it, then gives you a register for reviewing every Zap in your own account.

Zap data-flow canvas, offboarding checklist and test-record cleanup plan

Copy this into a document or spreadsheet and fill in one register per Zap. Part 1 is a worked example for an invented plumbing business with invented customer data, Part 2 is the blank form with where to look for each entry, and Parts 3 and 4 are the offboarding checklist and the test-record cleanup plan.

How to use it

Every entry is something you read in your own account, and no password, key, token or webhook URL goes into it.

zapier.txt

Introduction10 lines

ZAP DATA-FLOW CANVAS One register per Zap. Every entry is something you read in your own account. Write field names, never field values. Never write a password, API key, token or webhook URL into this register: Zapier's webhooks article says to treat a hook URL as a password. Zap: ______ Zap owner: ______ Folder, and who the Zap or folder is shared with: ______ Zapier plan (Free, Professional, Team or the fourth plan): ______ Date reviewed: ______ Reviewed by: ______

What Zapier's own pages say about how it handles your accounts

Zapier connects the apps a business already uses.

A Zap starts from a trigger in one app and runs action steps in others, and to do that Zapier holds an app connection for each account a Zap uses and records each run. Whether that arrangement suits your business turns on which accounts you connect, who in your Zapier account can use them, what data passes through, how long the record is kept and what happens when someone leaves. Each of those can be checked from your own account, and this guide shows where.

On the connection itself, Zapier's app connections article says Zapier accesses only the data authorised for the account used in a connection, that connecting an app grants Zapier access to read and write data within that app, and that Zapier only performs actions necessary to run your workflows. It lists five ways Zapier authenticates to an app: OAuth 2.0, API key, basic authentication, session authentication and digest authentication.

Zapier's security and compliance page says Zapier stores encrypted app credentials (OAuth, API keys and more) in account-owned connections, encrypts data in transit with TLS 1.2 or later and at rest with AES-256, and stores data on Amazon Web Services in the United States. On audits, the same page says Zapier is "SOC 2 (Type II) and SOC 3 certified, audited annually by an independent firm", and that both reports are in the Zapier "Trust Center": the SOC 3 report is public, and the SOC 2 (Type II) report requires an NDA.

Where a Zapier help article marks which plans a feature is available on, it lists four plans: Free, Professional, Team and a fourth plan listed after Team. This guide calls that one the fourth plan. Where a feature below depends on a plan, the plan is the one Zapier's article marks.

Where a Zap sits between your apps

Picture a quote request on a trade business's website.

The form handler posts the enquiry to a Zapier webhook URL, a filter step checks the suburb, a Google Sheets step adds a row to the job sheet, and a Gmail step sends the customer a reply. That one Zap moves the enquiry through four places: the website's form handler, Zapier's record of the run, the job sheet and the mailbox. The worked example in the register on this page follows this Zap step by step.

A connection can do more than the step that uses it. Zapier's Google Sheets article lists actions that delete or clear rows alongside those that create them, and an "API Request (Beta)" action that makes a raw HTTP request including the integration's authentication.

So the register records the account behind every step and what that account granted, not only the event the step performs. How an OAuth grant works, and what an application checks when it receives one, belongs to the OAuth and OpenID Connect guide.

Connected accounts: who can use them and what they can reach

Connections start private.

Zapier's sharing article says that by default only the person who created a connection can use it in Zaps, and that on the Team and fourth plans its owner can share it with chosen users, with teams on the fourth plan, or with everyone in the account through the "Share with everyone" checkbox.

Everyone a connection is shared with can view data used to test a Zap, use the connection in their own Zaps to access or update information, and edit steps in a team's Zap that use it.

The article's own example is an email connection: sharing it lets those users read emails in that account that trigger Zaps or are used to test triggers, and send email from that account.

The same article advises sharing only with people you are comfortable giving that access, and offers an alternative: create a separate account in the app to share instead, such as a shared email account, rather than sharing a connection to your own.

On the fourth plan, admins, super admins and owners can stop users sharing connections with everyone through the "Restrict sharing with everyone" setting under App connections in the "Admin Center".

Two more controls on the fourth plan change what members can connect. Managed apps let admins mark an app so that only admins create, share and delete its connections, while members use the ones admins share with them; Zapier's article says connections members made before the change are not removed.

Allowed domains limit new OAuth connections, for the apps Zapier lists as supported, to email domains an admin approves. Zapier's example is a team member connecting a personal Gmail account, which the setting blocks.

Among the limitations its article lists, the setting does not apply to apps that authenticate with API keys instead of OAuth, webhook connections operate independently of it, and existing connections are not affected.

Reading the inventory without exposing a credential

The App Connections page lists each connection with its app, the number of Zaps using it, when it was last modified and the "People with access", and can be filtered to active, expired or non-compliant connections. The account owner, or a super admin, can also start an export of every connection from "Security and data" in Settings, and Zapier emails them the CSV.

Zapier's export article lists its columns, among them the owner's email, whether the connection is shared and with whom, and its status, and says the export never includes credentials, API keys or other sensitive authentication data.

Zapier's roles article adds who else can reach a connection: super admins and owners can access connections they do not own and that are not shared with them, and admins can delete another member's private connections.

On the app's side, Google's help page on linked apps says a Google Account holder can review the access an app from another developer holds on the linked apps page, under "Access to your Google Account", then the app, then "See details".

The same page offers a button that removes the access, which is a change to the account and not part of a review.

Zap history: the task history data each run keeps

Zapier's help articles call the record of each run Zap history.

Its article says the Zap history page has two parts, Zap runs and task usage, that Zapier records information about each Zap run, and that a step's run details include a timestamp and the data received and sent by that step. In the worked example, that puts the customer's name, email address, phone number and job description in the webhook step's record and again in the Google Sheets step's data, and the name and job description a third time in the reply the Gmail step sent.

Reading that record does not depend on being able to edit every step. Zapier's roles article says that where a step uses a private connection, only the connection's owner can create or edit the step, while members, admins, super admins and owners with access to the Zap can view it and can also view any information that passes through its Zap history.

Its permissions table lets super admins and owners view assets they do not own and that are not shared with them.

How long the record stays depends on which article you read. The Zap history article says 60 days of run data is the most Zapier can commit to holding in Zap history, and that it displays up to 10,000 runs. The data retention article, which Zapier marks as available on the fourth plan only, says Zapier retains Zap history for 29 to 69 days, and that on the fourth plan admins, super admins and owners can set retention to between 7 and 30 days for all shared and unshared Zaps in the account.

That setting is a slider in the "Compliance and data" section of "Security and privacy" in Settings.

Its article says changes take effect immediately, deletion is permanent, and it may take up to 24 hours for the history to be deleted.

Two details decide what persists after that. Zapier's export article says up to 5,000 runs at a time can be exported as CSV or JSON, and that Zapier emails the export to the Zapier account's email address.

And for a run that finished, Zapier's Zap history article says deleting the run only removes the record of it and cannot undo the action. A retention setting therefore governs Zapier's copy, not the rows, emails and exports the runs produced.

Sending a Zap only the fields its steps use keeps the rest out of all of those copies; field-level minimisation in your own application is covered in the sensitive data exposure guide.

Webhook triggers: a URL Zapier says to treat as a password

A Webhooks by Zapier trigger gives a Zap its own URL to receive data.

Zapier's trigger article sets up two trigger events, "Catch Hook", which parses the request body, and "Catch Raw Hook", which keeps the body unparsed, up to 2MB, and includes headers, and marks webhook triggers as available on the Professional, Team and fourth plans. The set-up it describes has you copy the URL and paste it into the sending app's webhook settings; its steps do not include connecting an app account.

Zapier's getting-started article for webhooks says the URL is "secured by obscurity" and almost impossible to guess, but that if you make it public, for example in front-end JavaScript, anyone who finds it will be able to spam it and trigger your Zap. It says to treat the URL as a password or any other secret.

In practice the URL does the job of a credential, so the register records where each hook URL is pasted and never the URL itself. A form that calls the hook from the visitor's browser puts the URL in front-end code, while a form handler on your server keeps it off the page.

How secrets leak into code sent to browsers, and how to retire one that has, is covered in the secrets exposure guide.

The URL is tied to the Zap's owner. Zapier's trigger article says it contains the owner's Zapier ID and changes only when the Zap is transferred to another user, after which the sending app has to be given the new URL or the Zap will not trigger. Removing a member transfers their Zaps, so it changes these URLs too, which is why the offboarding checklist lists them.

Switching a Zap off does not stop its hook answering straight away, and Zapier's two articles describe the response differently. The trigger article says a Zap that is off or deleted returns 404 to incoming webhook requests, after a delay of up to several hours during which the URL keeps returning 200.

The getting-started article says Zapier always returns a success message for all webhooks, whether or not a live Zap is behind them, and that once you have started a Zap and configured its hook URL, Zapier tracks the payloads it receives even before the Zap is switched on, to make debugging easier. Read both before relying on a switched-off Zap to turn data away.

Webhooks run the other way too. A Zap can send data to a URL you give it, and the getting-started article lists Basic Auth and Headers among the options for that request. If an endpoint of yours receives a Zap's requests, record which step holds whatever the endpoint checks and who can edit that step, never the value itself. Whether the endpoint refuses a request without it is a property of your application, not of Zapier.

Sharing, roles and who can change a Zap

The Team and fourth plans add shared accounts and roles.

Zapier's roles article names four account roles: one owner per account; a super admin, on the fourth plan only, with every owner permission except transferring ownership of or deleting the account; an admin with limited administrative permissions; and a member with no administrative privileges.

Assets such as Zaps carry roles of their own, owner and editor, with a viewer role only for Canvas, Tables and Agents. In the article's asset-role table, an editor can view, duplicate, edit and share an asset, while changing its owner, moving it to another account and deleting it are marked for the asset's owner alone. Its account-level table separately lets super admins and owners transfer and delete assets they do not own.

Zaps are shared one at a time from the Zap editor or by sharing the folder they sit in. Zapier's assets article says subfolders inherit the sharing settings of their top-level folder, and that moving a folder into a shared folder changes its sharing to match the new parent.

Read together with the roles article, that means a Zap moved into a shared folder for tidiness can open its Zap history to everyone the folder is shared with. Sharing a Zap without its connections has a limit of its own: Zapier's article on managing app connections says the people it is shared with cannot edit or view the configuration of any step that uses a connection not shared with them.

Sign-in controls sit at the account level. Zapier's security and compliance page says two-factor authentication is offered on every plan. Single sign-on is described two ways: the SAML set-up article marks it as available on the Team and fourth plans and requires a verified domain and an admin, super admin or owner to configure it, while the FAQ on the security and compliance page says SSO (SAML) and SCIM provisioning are added on the fourth plan.

Confirm with Zapier which applies to your account before planning around it.

Once SAML login is switched on, the set-up article says all team members must sign in through it and username and password sign-in is disabled.

For a record of changes, Zapier's monitoring article, marked for the Team and fourth plans, says the audit log shows Zap activity across the account, such as when a Zap was published, turned on or off, or deleted. Zapier's roles article gives the "View audit log" permission to super admins and owners.

Testing a Zap can write real records

Zapier's article on testing steps is direct about this.

When you test an action step, Zapier performs the action on your behalf; testing is live and may result in changes in your app, and the same holds for an end-to-end test run. Testing a trigger loads data from the trigger app, and the article's own example is a Gmail trigger that pulls in a recent email you have received. Some apps return generic samples instead of real data.

A careless test can therefore copy a real customer's details into the Zap editor, where anyone a connection is shared with can view data used to test a Zap, and create a real row, contact or email in each app whose action step is tested.

The article says the trigger and every Filter and Paths step must be tested before a Zap can be published, while other action steps may skip testing. Zapier's article on test records adds that a modified trigger test record stays as a copy inside Zapier and does not change the trigger app, and that a previous Zap run can be used as a test record.

The cleanup plan in the register works from invented customer data. Send a test enquiry with an invented name and a marker such as ZAPTEST-0611 in a free-text field, point any test email at an inbox the business controls, and record where each action test landed.

Removing those records is a change each app's owner makes in that app; the plan records what was created and where, so nothing is left behind by accident.

When someone leaves the Zapier account

Zapier's article on removing members from a Team or fourth-plan account describes what removal does.

Ownership of all of the person's Zaps, shared and unshared, transfers to the user chosen in the dialog that "Remove member" opens, which defaults to the account owner; if an admin does the removal, the Zaps and connections go to the account owner instead.

Zaps keep their on or off status. Unshared Zaps move to a new unshared folder named after the person, and ownership of all their app connections transfers to the new owner, with each connection renamed with the person's name in front.

Connections are where the decision sits. For the person's private connections, the dialog asks whether they stay active for 30 days or until they expire on the app's own schedule. Shared connections keep working as long as the person's app account exists, until they expire on the app's schedule.

Zapier's best-practices article adds that removing the person from the connected apps themselves makes their connections expire, overriding the choice made in Zapier, and recommends testing each app connection after the removal.

Three details are worth planning before the removal. The CSV of the person's Zaps and connections can be downloaded from the Members page only while they are still a member; after removal, the new owner is emailed a link to it that stays valid for 7 days.

The webhook URLs on their Catch Hook and Catch Raw Hook triggers change. And on accounts using SCIM, the person is removed through the identity provider, their Zaps and app connections all transfer to the account owner, and private connections stay active for up to 30 days by default.

The best-practices article also says to transfer the person's Tables, Forms, Chatbots and Agents before removal, and that the removal process prompts for their Zaps and app connections.

Zapier's data privacy article says that once removed from an account on the fourth plan, a member no longer has access to any shared Zaps or connections in the account. Their access to the connected apps themselves is a separate question, answered in each app.

How to fill in the data-flow canvas

Make one register per Zap.

Open the Zap in the editor and give each step a row: the trigger first, then each action in order, including built-in steps such as filters that hold no connection but still carry data. Every entry is a reading. Nothing in the register asks you to change a setting, reconnect an account, run a test or send a request.

  • Connected account: the connection's name and owner from the App Connections page, whether it is private or shared, and who it is shared with.
  • Permission or scope: what the connected app's own page says Zapier holds, read where that app shows it, such as Google's linked apps page for a Google account. Add what Zapier's article for that app says the account needs, and note which page each part came from.
  • Webhook triggers: the system and setting where the hook URL is pasted. Never the URL.
  • Fields in Zap history: open one recent run and list the field names each step received and sent. Names only, never values.
  • Who else can see or edit: the people and teams the Zap or its folder is shared with, the people a connection is shared with, and the account owner, plus any super admins on the fourth plan, who can view every asset.
  • If the owner leaves, and test records: what changes for this step under the offboarding checklist, and what a test of this step created or sent.

Keeping the register current

A register is accurate on the day it is filled in. Update it when a Zap changes owner, when someone with access leaves, and when a step or connection is added. Zapier's best-practices article suggests regular workflow reviews on a schedule, such as monthly or quarterly, and says Zapier Manager can trigger when new app connections are created and when Zaps are created, turned on or turned off, which is one way to learn that a register is out of date.

Outside what the Zap register can see

The register records your settings and your Zaps.

Several things sit outside what it can see:

  • Anything inside Zapier's own systems, such as its infrastructure, staff access and audits. For those, you have what Zapier's own pages and reports say.
  • What each connected app does with the access it granted, or what it keeps. That sits with the app's own settings and terms.
  • Whether a hook URL has already been copied somewhere. The register shows where it is meant to be, not every place it has been.
  • Copies outside Zapier: exports of Zap history, and the rows, emails and records that runs and tests created in other apps.
  • Whether your own applications check the requests they send to a Zap or receive from one. That takes testing of the application itself.

Where Clever Ops fits around your Zaps

This guide is information for reviewing your own Zapier account, not a description of a service.

A Clever Ops test leaves out services that other businesses run unless their owner agrees, and Zapier's platform is one of them.

Where a Zap meets an application you own, such as a form handler that posts to a hook URL or an API endpoint that receives a Zap's requests, active testing of that application sits within a scoped web application and API penetration test. That test covers what each role can see and change and calls the API directly rather than only through the screens.

A secure code review lists webhooks among the entry points it traces from the request to the query, and the website security check includes keys and secrets in page source and JavaScript among its twelve checks.

Where Clever Ops built or hosts the application under review, the report names the builder and the host, and the work is a security review, not an independent test.

Frequently asked questions

Not only the people who can edit every step. Zapier's roles article says members, admins, super admins and owners with access to a Zap can view any information that passes through its Zap history, even in a step whose private connection only its owner can edit. Super admins and owners can view assets that are not shared with them, and anyone a connection is shared with can view data used to test a Zap.

Zapier's data retention article says 29 to 69 days, and its Zap history article says 60 days of run data is the most Zapier can commit to holding, with up to 10,000 runs displayed. On the fourth plan, admins, super admins and owners can set retention to between 7 and 30 days for the whole account. The setting applies to Zap history; exports, and the records your Zaps created in other apps, are separate copies.

Zapier says to treat it as one. Its webhooks article says the URL is secured by obscurity and almost impossible to guess, but that anyone who finds a URL made public, for example in front-end JavaScript, can spam it and trigger your Zap, and that you should treat it as a password. Its trigger article adds that the URL contains the owner's Zapier ID and changes when the Zap is transferred to another user.

For action steps, yes. Zapier's testing article says that when you test an action step Zapier performs the action, and that testing is live and may result in changes in your app, including during an end-to-end test run. The trigger and every Filter and Paths step must be tested before publishing; other action steps can skip testing.

On Team and fourth-plan accounts, Zapier transfers them to the user chosen at removal, or to the account owner when an admin does the removal. You choose whether their private connections stay active for 30 days or until they expire, the Catch Hook and Catch Raw Hook URLs on their Zaps change, and the CSV link emailed to the new owner works for 7 days. On accounts using SCIM, their Zaps and app connections all go to the account owner.

Zapier's SAML set-up article marks single sign-on as available on the Team and fourth plans and requires a verified domain, while the FAQ on its security and compliance page says SSO (SAML) and SCIM provisioning are added on the fourth plan. Confirm with Zapier which applies to your account. When SAML login is switched on, members must sign in through it and username and password sign-in is disabled.

Scope the right test for your application

Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.