OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 7.5/10
Structured API for the declared product scope
Zapier / Workflow API v2 Zap enumeration for an embedded public integration; connected-app data, task history and independent workflow execution are excluded.
Zapier’s Workflow API lists user-owned Zaps. Default results contain the authenticating integration; broader scopes are needed for other or shared workflows.
Zapier Workflow API list Zaps ↗
Pagination, filters and returned workflow fields · Checked 2026-10-22
Bulk delivery 8.8/10
Batched or iterable API requests
Zapier / Workflow API v2 Zap enumeration for an embedded public integration; connected-app data, task history and independent workflow execution are excluded.
Traverse the /zaps endpoint’s pagination within the authorized user and integration scope.
Zapier Workflow API list Zaps ↗
Pagination, filters and returned workflow fields · Checked 2026-10-22
Query expressiveness 8.8/10
Documented structured API filters
Zapier / Workflow API v2 Zap enumeration for an embedded public integration; connected-app data, task history and independent workflow execution are excluded.
Use input filters and expand step details. zap:all and zap:account:all change which workflows and step inputs are visible.
Zapier Workflow API list Zaps ↗
Pagination, filters and returned workflow fields · Checked 2026-10-22
Access cost barrier -
-
Zapier / Workflow API v2 Zap enumeration for an embedded public integration; connected-app data, task history and independent workflow execution are excluded.
Minimum commercial entitlement and exact API charges were not established for the assessed route.
Zapier Workflow API list Zaps ↗
Pagination, filters and returned workflow fields · Checked 2026-10-22
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility 7.5/10
Open registration under published review criteria
Zapier / Workflow API v2 Zap enumeration for an embedded public integration; connected-app data, task history and independent workflow execution are excluded.
This embedded route requires an integration published in Zapier’s App Directory and a user access token. Account-wide scope does not follow from an ordinary integration grant.
Zapier embedded workflow eligibility and authorization ↗
Prerequisites and scope-dependent visibility · Checked 2026-10-22
Downstream permission -
-
Zapier / Workflow API v2 Zap enumeration for an embedded public integration; connected-app data, task history and independent workflow execution are excluded.
Processing, AI-use, redistribution and other downstream contractual permissions were not settled by this technical review.
Zapier embedded workflow eligibility and authorization ↗
Prerequisites and scope-dependent visibility · Checked 2026-10-22
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface -
-
Zapier / Workflow API v2 Zap enumeration for an embedded public integration; connected-app data, task history and independent workflow execution are excluded.
A matching write operation was not verified; this review makes no claim that writes are absent.
Zapier Workflow API list Zaps ↗
Pagination, filters and returned workflow fields · Checked 2026-10-22
Custom application path 5.0/10
Approved third-party applications using fixed interfaces
Zapier / Workflow API v2 Zap enumeration for an embedded public integration; connected-app data, task history and independent workflow execution are excluded.
The documented interface can connect customer application code within its authorization and resource scope.
Zapier embedded workflow eligibility and authorization ↗
Prerequisites and scope-dependent visibility · Checked 2026-10-22
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 5.0/10
Scheduled feeds or recurring extracts
Zapier / Workflow API v2 Zap enumeration for an embedded public integration; connected-app data, task history and independent workflow execution are excluded.
Repeat the assessed collection traversal to reconcile current state. Native change delivery and retained replay were not established in this review.
Zapier Workflow API list Zaps ↗
Pagination, filters and returned workflow fields · Checked 2026-10-22
Limit visibility 10.0/10
Published numeric quotas and recovery instructions
Zapier / Workflow API v2 Zap enumeration for an embedded public integration; connected-app data, task history and independent workflow execution are excluded.
The Workflow API permits 60 requests/minute per IP and 150/minute per partner. A 429 starts a 60-second cooldown.
Zapier Workflow API rate limits ↗
Per-IP and partner budgets; cooldown · Checked 2026-10-22
CDC and deletion capture 2.5/10
Full snapshots permit customer reconciliation; native deltas unverified
Zapier / Workflow API v2 Zap enumeration for an embedded public integration; connected-app data, task history and independent workflow execution are excluded.
Compare complete scoped snapshots to reconcile missing records; native deletion identities and intermediate changes were not established.
Zapier Workflow API list Zaps ↗
Pagination, filters and returned workflow fields · Checked 2026-10-22
Replay and gap recovery 2.5/10
Rebuild from a fresh snapshot; no historical replay established
Zapier / Workflow API v2 Zap enumeration for an embedded public integration; connected-app data, task history and independent workflow execution are excluded.
Repeat the declared collection or export route to rebuild current state within its permissions and selection limits. Deleted payloads and intermediate history are unverified.
Zapier Workflow API list Zaps ↗
Pagination, filters and returned workflow fields · Checked 2026-10-22
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 7.5/10
Customer-held structured files or API records
Zapier / Workflow API v2 Zap enumeration for an embedded public integration; connected-app data, task history and independent workflow execution are excluded.
The assessed structured payloads can be retained in customer-held files. Broader contractual reuse rights remain unresolved.
Zapier Workflow API list Zaps ↗
Pagination, filters and returned workflow fields · Checked 2026-10-22
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Zapier / Workflow API v2 Zap enumeration for an embedded public integration; connected-app data, task history and independent workflow execution are excluded.
The reviewed technical documentation does not establish retrieval rights after account termination.
Zapier embedded workflow eligibility and authorization ↗
Prerequisites and scope-dependent visibility · Checked 2026-10-22
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Zapier / Workflow API v2 Zap enumeration for an embedded public integration; connected-app data, task history and independent workflow execution are excluded.
Retain returned Zap metadata and permitted step inputs. This route does not establish a restorable independent workflow, credentials or complete task history.
Zapier Workflow API list Zaps ↗
Pagination, filters and returned workflow fields · Checked 2026-10-22
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 2.5/10
External integration code; native business logic portability not established
Zapier / Workflow API v2 Zap enumeration for an embedded public integration; connected-app data, task history and independent workflow execution are excluded.
External code can use this interface; native workflow portability was not established (API clients and native definitions are different artifacts).
Zapier embedded workflow eligibility and authorization ↗
Prerequisites and scope-dependent visibility · Checked 2026-10-22
Rights to custom logic -
-
Zapier / Workflow API v2 Zap enumeration for an embedded public integration; connected-app data, task history and independent workflow execution are excluded.
Ownership and reusable export rights for native workflow artifacts need a separate contractual review.
Zapier embedded workflow eligibility and authorization ↗
Prerequisites and scope-dependent visibility · Checked 2026-10-22
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
This embedded route requires an integration published in Zapier’s App Directory and a user access token. Account-wide scope does not follow from an ordinary integration grant.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
Traverse the /zaps endpoint’s pagination within the authorized user and integration scope. Use input filters and expand step details. zap:all and zap:account:all change which workflows and step inputs are visible.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Workflow API v2 Zap enumeration for an embedded public integration | oauth2 | partner | Yes | provider approval | 2026-10-22 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
Minimum plan and exact route fees remain unconfirmed.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
Write operations remain unverified for this assessed route.
Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.
KEEP ACCESS USEFUL
Continuity
Repeat the assessed collection traversal to reconcile current state. Native change delivery and retained replay were not established in this review.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Full snapshots permit customer reconciliation; native deltas unverifiedZapier / Workflow API v2 Zap enumeration for an embedded public integration; connected-app data, task history and independent workflow execution are excluded. Compare complete scoped snapshots to reconcile missing records; native deletion identities and intermediate changes were not established. | Zapier Workflow API list Zaps ↗Pagination, filters and returned workflow fieldsChecked 2026-10-22 |
| How can extraction recover after missed events or an interrupted consumer? | Rebuild from a fresh snapshot; no historical replay establishedZapier / Workflow API v2 Zap enumeration for an embedded public integration; connected-app data, task history and independent workflow execution are excluded. Repeat the declared collection or export route to rebuild current state within its permissions and selection limits. Deleted payloads and intermediate history are unverified. | Zapier Workflow API list Zaps ↗Pagination, filters and returned workflow fieldsChecked 2026-10-22 |
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
Retain returned Zap metadata and permitted step inputs. This route does not establish a restorable independent workflow, credentials or complete task history.
Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.
BUILD / INSPECT / REUSE
Business logic and customization
Customers can write external integration code. Native workflow rights and independent execution remain unresolved (record access does not establish portable application logic).
Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.
AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS
Documented conditions
Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| What structured read interface is documented? | Structured API for the declared product scopeZapier / Workflow API v2 Zap enumeration for an embedded public integration; connected-app data, task history and independent workflow execution are excluded. Zapier’s Workflow API lists user-owned Zaps. Default results contain the authenticating integration; broader scopes are needed for other or shared workflows. | Zapier Workflow API list Zaps ↗Pagination, filters and returned workflow fieldsChecked 2026-10-22 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsZapier / Workflow API v2 Zap enumeration for an embedded public integration; connected-app data, task history and independent workflow execution are excluded. Traverse the /zaps endpoint’s pagination within the authorized user and integration scope. | Zapier Workflow API list Zaps ↗Pagination, filters and returned workflow fieldsChecked 2026-10-22 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersZapier / Workflow API v2 Zap enumeration for an embedded public integration; connected-app data, task history and independent workflow execution are excluded. Use input filters and expand step details. zap:all and zap:account:all change which workflows and step inputs are visible. | Zapier Workflow API list Zaps ↗Pagination, filters and returned workflow fieldsChecked 2026-10-22 |
| Who decides whether a chosen third party may connect? | Open registration under published review criteriaZapier / Workflow API v2 Zap enumeration for an embedded public integration; connected-app data, task history and independent workflow execution are excluded. This embedded route requires an integration published in Zapier’s App Directory and a user access token. Account-wide scope does not follow from an ordinary integration grant. | Zapier embedded workflow eligibility and authorization ↗Prerequisites and scope-dependent visibilityChecked 2026-10-22 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Zapier / Workflow API v2 Zap enumeration for an embedded public integration; connected-app data, task history and independent workflow execution are excluded. Minimum commercial entitlement and exact API charges were not established for the assessed route. | Zapier Workflow API list Zaps ↗Pagination, filters and returned workflow fieldsChecked 2026-10-22 |
| Which external write operations are documented? | -Zapier / Workflow API v2 Zap enumeration for an embedded public integration; connected-app data, task history and independent workflow execution are excluded. A matching write operation was not verified; this review makes no claim that writes are absent. | Zapier Workflow API list Zaps ↗Pagination, filters and returned workflow fieldsChecked 2026-10-22 |
| How can customers connect an application they build or choose? | Approved third-party applications using fixed interfacesZapier / Workflow API v2 Zap enumeration for an embedded public integration; connected-app data, task history and independent workflow execution are excluded. The documented interface can connect customer application code within its authorization and resource scope. | Zapier embedded workflow eligibility and authorization ↗Prerequisites and scope-dependent visibilityChecked 2026-10-22 |
| What mechanism supports repeatable extraction of changes? | Scheduled feeds or recurring extractsZapier / Workflow API v2 Zap enumeration for an embedded public integration; connected-app data, task history and independent workflow execution are excluded. Repeat the assessed collection traversal to reconcile current state. Native change delivery and retained replay were not established in this review. | Zapier Workflow API list Zaps ↗Pagination, filters and returned workflow fieldsChecked 2026-10-22 |
| How are integration limits disclosed? | Published numeric quotas and recovery instructionsZapier / Workflow API v2 Zap enumeration for an embedded public integration; connected-app data, task history and independent workflow execution are excluded. The Workflow API permits 60 requests/minute per IP and 150/minute per partner. A 429 starts a 60-second cooldown. | Zapier Workflow API rate limits ↗Per-IP and partner budgets; cooldownChecked 2026-10-22 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsZapier / Workflow API v2 Zap enumeration for an embedded public integration; connected-app data, task history and independent workflow execution are excluded. The assessed structured payloads can be retained in customer-held files. Broader contractual reuse rights remain unresolved. | Zapier Workflow API list Zaps ↗Pagination, filters and returned workflow fieldsChecked 2026-10-22 |
| What retrieval rights are documented at cancellation? | -Zapier / Workflow API v2 Zap enumeration for an embedded public integration; connected-app data, task history and independent workflow execution are excluded. The reviewed technical documentation does not establish retrieval rights after account termination. | Zapier embedded workflow eligibility and authorization ↗Prerequisites and scope-dependent visibilityChecked 2026-10-22 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedZapier / Workflow API v2 Zap enumeration for an embedded public integration; connected-app data, task history and independent workflow execution are excluded. External code can use this interface; native workflow portability was not established (API clients and native definitions are different artifacts). | Zapier embedded workflow eligibility and authorization ↗Prerequisites and scope-dependent visibilityChecked 2026-10-22 |
| What rights or portability are documented for custom workflow artifacts? | -Zapier / Workflow API v2 Zap enumeration for an embedded public integration; connected-app data, task history and independent workflow execution are excluded. Ownership and reusable export rights for native workflow artifacts need a separate contractual review. | Zapier embedded workflow eligibility and authorization ↗Prerequisites and scope-dependent visibilityChecked 2026-10-22 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedZapier / Workflow API v2 Zap enumeration for an embedded public integration; connected-app data, task history and independent workflow execution are excluded. Retain returned Zap metadata and permitted step inputs. This route does not establish a restorable independent workflow, credentials or complete task history. | Zapier Workflow API list Zaps ↗Pagination, filters and returned workflow fieldsChecked 2026-10-22 |
| What permission is needed for the documented downstream use? | -Zapier / Workflow API v2 Zap enumeration for an embedded public integration; connected-app data, task history and independent workflow execution are excluded. Processing, AI-use, redistribution and other downstream contractual permissions were not settled by this technical review. | Zapier embedded workflow eligibility and authorization ↗Prerequisites and scope-dependent visibilityChecked 2026-10-22 |
SOURCES / SCOPE / HISTORY
Sources and open questions
This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.
Still to confirm
- Minimum commercial entitlement and exact API charges
- Downstream contractual permissions and post-cancellation retrieval rights
- Complete migration of history, files, permissions and native workflow definitions
Documentation
Assessment checked 2026-10-22. Each answer retains its source and applicable route; the check date does not establish live account behavior.