01 · Records and state owned
Scoped actions across 9,000+ apps and tens of thousands of actions; account/workspace governance applies
Zapier
Zapier
Curated anchor platform in automation and connector network with material relevance to the Marcom operating stack and a first-party developer surface.
Automation, data & MCP bridgesSystem of orchestrationAgent-accessible SaaS
Concrete capability record
Data, retrieval, actions, identity, and operating limits
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
02 · Data you can retrieve
Scoped actions across 9,000+ apps and tens of thousands of actions; account/workspace governance applies
03 · Actions and write paths
Zapier's first-party MCP/agent surface includes state-changing tools in the documented capability area: Scoped actions across 9,000+ apps and tens of thousands of actions; account/workspace governance applies. The audit did not enumerate every mutation; verify the current tool catalog and require explicit confirmation for consequential actions.
04 · Authentication and permissions
For Zapier, the audited authentication model is: Authentication model is documented by the vendor; inspect the cited source before implementation. The effective permission model is: Existing vendor identity, account, tenant, and permission controls should be treated as the authorization boundary. Reconfirm the cited first-party source before implementation.
05 · Monitoring, approval, and recovery
Official product and technical docs confirm hosted MCP; action counts are time-sensitive and should carry verification dates. Official product and technical docs confirm hosted MCP; action counts are time-sensitive and should carry verification dates.
06 · Gaps and implementation limits
Official product and technical docs confirm hosted MCP; action counts are time-sensitive and should carry verification dates.
Agent access
MCP and adjacent posture
Verified first-party provider MCPZapier-hosted integration MCPGenerally available
Role: provider
Read scope: Scoped actions across 9,000+ apps and tens of thousands of actions; account/workspace governance applies
Write scope: State-changing tools are present in the documented scope; review the official tool catalog and require confirmation for consequential actions.
Authentication: Authentication model is documented by the vendor; inspect the cited source before implementation.
Approval boundary: Official product and technical docs confirm hosted MCP; action counts are time-sensitive and should carry verification dates.
Protocol does not erase product boundaries.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
Access-maturity dimensions
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Data access4
Action access4
Event access4
Identity2
Governance3
Agent access4
UI extensibility3
Portability4
Observability4
Documentation5
Proposed interfaces
What customers could build on top.
These are design proposals derived from documented access—not claims that Zapier ships these experiences.
Single-platform patterns
- Rapid MCP wrapper and campaign workflow factory
- Marcom control plane
- Data-quality exception console
- Approved capability registry
Multi-platform compositions
- Zapier + systems of record: marcom control plane
- Zapier + systems of engagement + interface host or builder: cross-system decision workspace
Evidence and dates
First-party references, with publisher and review dates separated
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
5 recorded sources
MCPRepresentative source
https://zapier.com/mcp ↗Official product and technical docs confirm hosted MCP; action counts are time-sensitive and should carry verification dates.
- Publisher published
- Jul 9, 2026
- BYO-UI reviewed
- Jul 10, 2026
Targeted first-party MCP/agent-role review; broader API inventory retained
APISource inventory
https://docs.zapier.com/platform/reference/intro ↗First-party API reference or API overview recorded for this platform.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Developer docsSource inventory
https://docs.zapier.com/ ↗First-party developer documentation or platform overview.
- Publisher updated
- Jun 24, 2026
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Webhooks / extensionsSource inventory
https://docs.zapier.com/platform/build ↗First-party webhook, event, SDK, embedded-app, or extension documentation.
- Publisher updated
- Jul 6, 2026
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
HomepageSource inventory
https://zapier.com/ ↗First-party product homepage used to confirm product identity and current positioning.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Verified fact
Tied to the representative first-party source or targeted access review.
Source inventory
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
Editorial assessment
System role, maturity interpretation, and architectural boundary.
Proposed design
Interface patterns and compositions—not vendor product claims.