zapier
Zapier — run actions in 9,000+ apps via MCP; do NOT expect programmatic Zap CRUD
This skill operates Zapier from an agent. It does one thing well — invoke a preconfigured action across thousands of apps by natural language through the official Zapier MCP server — and it is loud about the one thing Zapier does not let you do: manage your own Zaps by API. Being honest about that boundary is the point of this skill, because the wrong assumption here wastes hours.
The honest boundary — read this before you promise anything
There is NO public REST API for a normal Zapier user to create, read, update, or delete their own Zaps. Not "hard", not "undocumented" — it does not exist for a standard account. Anyone who tells the user "just hit the Zapier API to build the Zap" is wrong. Say this plainly and early.
What actually exists, and what each thing is for:
| Path | What it does | Who it is for |
|---|---|---|
| Zapier MCP (this skill) | RUNS a preconfigured action (send/search/create) in 9,000+ apps by natural language. GA on all plans. | Anyone wiring an agent to act in SaaS apps. |
Partner API (api.zapier.com/v1/...) |
Embed Zapier inside your product: zap-templates, list the Zaps that include your app, an embeddable iframe editor. |
SaaS vendors, needs OAuth client_id. |
| Workflow API | Can create a Zap — but ONLY for developers who ship a published public integration on Zapier. | Integration builders, not account owners. |
| Does not exist. | Nobody. Route them elsewhere. |
So the routing rule is one sentence: dynamic "run an action in any app by natural language" → Zapier MCP (excellent). "Programmatically create/manage my Zaps" → not possible on a normal account → route to the visual builder (automation-flows) or to n8n / Make, which DO expose full workflow CRUD APIs. Full detail: references/programmatic-limits-and-partner-api.md.