Zapier makes it easy to build automations, but inspecting their underlying configurations is another story.
If you have dozens of Zaps and need to document, audit, migrate, or understand them, clicking through every step manually is tedious. A Zap might contain several actions, filters, branches, and field mappings. You need more than a list of application names to understand what it actually does.
I recently ran into this problem while auditing a client's Zapier integrations with WordPress and Gravity Forms.
The goal was straightforward: retrieve the complete configuration of every Zap, including the input parameters and mappings between steps, without modifying any existing automation.
After investigating Zapier's browser requests and internal APIs, I found a surprisingly simple approach.
The Zapier editor embeds the published workflow definition as JSON inside its HTML response. You can retrieve and parse that data directly from an authenticated browser session.
In our audit, this technique retrieved 58 published Zap definitions, approximately 190 KB of structured JSON, without entering edit mode or changing any workflows.
This guide explains how it works, how to extract a single Zap, how to retrieve an entire account's published workflows, and how to identify the external systems triggering them.
Tested October 27, 2026. The internal endpoints discussed below are undocumented and could change.
1. What can you extract from Zapier?
A useful Zap export should tell you more than which applications are connected.
Ideally, you want access to:
For example, imagine an automation that starts when a form is submitted, creates a contact in a CRM, and sends an email.
A simplified representation of the extracted JSON might look like this:
json
This is an illustrative example, not an actual Zapier response.
Notice the mapping syntax:
{{111111__Email}}
This references the Email output of an earlier step identified by 111111.
These references are particularly valuable when migrating automations to another platform or documenting dependencies between steps.
2. The discovery: Zapier embeds workflow JSON in its HTML
My first assumption was that the Zapier editor fetched its complete workflow configuration through an API request.
That would be a natural architecture: load the editor, make a request for the Zap definition, and render the steps.
Indeed, Zapier has internal endpoints such as:
http
GET /api/v4/zaps/{id}/
However, in our investigation, this endpoint returned the list of steps without their complete parameters.
The more useful discovery was that the editor's published view already contains the complete published Zap definition.
The relevant URL is:
http
GET https://zapier.com/editor/{zapId}/published
The response is HTML, but embedded in that HTML is a script element commonly used by Next.js applications:
In other words, you do not need to reverse-engineer every request made by the editor.
You can fetch the page HTML and extract the state that Zapier has already serialized for the frontend.
Why this works
Next.js applications can serialize data during server rendering or page generation and embed it in the resulting HTML.
This allows the browser to initialize its frontend with data already obtained by the server.
The exact implementation varies between applications and Next.js versions. In the version of Zapier we investigated, the embedded data happened to include the published Zap's underlying definition.
This is an implementation detail rather than a supported export API, but it is very useful for read-only workflow analysis.
3. How to extract one Zap as JSON
You only need Chrome or another browser with developer tools and access to the Zap you want to inspect.
Step 1: Open the Zap editor
Sign in to Zapier and open one of your existing Zaps.
Your URL should resemble:
text
https://zapier.com/editor/123456789/published
The numeric portion identifies the Zap.
Use a Zap that has a published version. Unpublished, draft-only Zaps may not have a current_version to extract.
Step 2: Open the browser console
Open Chrome Developer Tools with F12 or Cmd + Option + I on macOS.
Select the Console tab.
Make sure you are running the script on zapier.com, not another website.
Replace YOUR_ACCOUNT_ID before running the script.
This implementation fetches the Zaps sequentially rather than issuing dozens of concurrent requests.
For a larger account, a production-grade extractor should also handle pagination failures, retryable errors, rate limiting, and differences in permissions.
Step 3: Download the JSON
Once the extraction completes, the results are stored in:
javascript
window.__zaps
Before saving or sharing these definitions, consider that step parameters may contain private URLs, tokens, customer identifiers, or hardcoded credentials.
For local analysis, you can create a redacted export:
The redaction is deliberately a starting point, not a guarantee that all sensitive values have been removed. For example, a secret might be embedded in a generic field such as url, value, or body.
Review the resulting file before uploading it anywhere or sharing it with an AI tool.
For our audit, we kept the original workflow definitions outside the Git repository and committed only derived documentation.
5. How to identify what triggers a Zap
Obtaining the Zap definition solves most workflow documentation problems, but not every one.
One complication we encountered involved Gravity Forms.
The Zap definition contained the trigger step and its configuration, but it did not reliably identify the exact WordPress form or website responsible for sending the data.
This matters when a business operates multiple websites.
A form ID might be unique within an individual WordPress installation but not across all websites connected to the same Zapier account.
Use Zap execution history
To resolve this, we queried Zapier's execution history.
In our Gravity Forms investigation, trigger outputs exposed useful information such as form ID, form title, and source URL.
By extracting only this metadata, we could connect a Zap to the originating WordPress form without exporting full customer submissions.
This distinction matters because execution outputs can contain names, email addresses, phone numbers, and other personal data.
Run history is subject to account retention settings. Our audit covered approximately 30 days of available runs, but that should not be treated as a universal Zapier limit.
What if a Zap has no recent runs?
No recent runs does not automatically mean the automation is broken.
The form might simply receive very few submissions, the Zap might be disabled, or the integration could use another Zapier account.
In our audit, we compared Zapier execution history with the WordPress database's Gravity Forms entries.
That let us distinguish inactive forms from forms that were receiving submissions but had no corresponding runs in the accessible Zapier account.
The WordPress side was especially useful because the Gravity Forms Zapier add-on configuration contained its feed information and webhook destination.
Important: A Zapier Catch Hook URL is effectively a secret. Possessing it can allow someone to submit events to the associated automation. Do not publish it in documentation or logs.
6. Why not just use Zapier's official export?
There are several official ways to obtain Zapier data, and they may be more appropriate depending on what you need.
Option A: Export your account data
Zapier documents a data export accessible under:
Settings → Security and data → Download my account data
The resulting ZIP includes a file named Zapfile.json.
According to Zapier's account export documentation, this contains undeleted Zap workflows and information needed to execute their steps, including step values and references.
This is a good choice if you simply want an official account-level export and do not need to capture workflow definitions immediately through browser automation.
Option B: Export Zap workflows directly
Zapier also supports dedicated workflow JSON exports for Team and Enterprise plans.
Eligible users can export their workflows from the account settings, and a Zap owner can export an individual Zap from the editor.
Before finding the embedded JSON, we explored several other approaches.
Zapier MCP and Zapier Manager: These were useful for discovering Zap names, status, and editor links, but they did not expose the full field mappings required for our audit.
The ordinary Zap editor API: The /api/v4/zaps/{id}/ response included step information but not the complete step parameters we needed.
Read-only editor UI: We could see step names, but inspecting complete field configurations through the interface required entering edit mode. We wanted to avoid creating drafts or changing workflows in a production account.
Zap History UI: The visual history was useful but showed human-readable labels rather than always exposing the raw source keys required for accurate mapping analysis.
Zapier CLI: This is designed primarily for developing and managing Zapier integrations, not for extracting the complete definitions of existing workflows in an account.
Ultimately, the server-rendered editor JSON was the simplest read-only solution for our specific requirements.
8. Limitations and security considerations
This approach worked in our October 2026 investigation, but there are important limitations.
First, the endpoint is undocumented. Zapier may change the URL, authentication behavior, embedded JSON structure, or frontend rendering architecture without notice.
Second, it retrieves published definitions. If a Zap contains unpublished draft changes, those changes may not be reflected in current_version. A draft-only Zap may have no published definition at all.
Third, the technique was verified on the Classic Zap editor. It should not automatically be assumed to work for Zapier's newer workflow products or Next Gen Zaps, which may use different implementations.
Fourth, the method operates with the permissions of your signed-in browser session. It is not a way to obtain access to Zaps you are not authorized to view.
Finally, remember that read-only does not mean non-sensitive. Reading configuration data is different from modifying a Zap, but its parameters may still contain confidential information.
Only run extraction scripts you understand, on accounts you are authorized to inspect. Keep session cookies and authentication material private. Review all JSON before sending it to outside services.
9. What can you do with exported Zap definitions?
Once the configurations are available as structured JSON, several useful workflows become possible.
You can generate technical documentation describing the triggers, actions, and field mappings for every Zap.
You can build a dependency inventory showing which applications exchange data and which workflows rely on specific integrations.
You can analyze a large Zapier account to identify duplicate automations, outdated app versions, hardcoded configuration, or workflows that may be candidates for consolidation.
And perhaps most importantly, you can use the definitions as reference material when migrating automations to another system.
The extracted JSON is not necessarily directly portable to another automation engine. Zapier-specific actions, authentication schemes, expressions, and runtime behavior still need to be interpreted and implemented.
But having the underlying configurations eliminates much of the manual discovery process.
For our WordPress and Gravity Forms audit, combining Zapier definitions, execution history, and the originating WordPress configurations gave us a much clearer picture of how submissions traveled between systems.
Conclusion
The interesting lesson from this investigation is that the data you need might already be present in the page you are viewing.
Instead of trying to reconstruct a Zap by clicking through every step or reverse-engineering individual network requests, we extracted the published workflow definition from the JSON embedded in the editor's server-rendered HTML.
The essential path was:
javascript
next.props.pageProps.zap.current_version.zdl
Combined with Zapier's internal listing and execution-history endpoints, this allowed us to inventory an entire account and inspect its published automation configurations without modifying production workflows.
For supported exports and long-term backups, Zapier's official data-export functionality remains the more stable option.
But if you are doing technical discovery, documenting existing automations, or building a migration inventory, knowing how to inspect the editor's embedded JSON can save considerable time.
Last validated: October 27, 2026. This is an independent technical investigation, not an officially supported Zapier integration.