Zapier vs Make
Zapier
Zapier, Inc.
Zapier wins · 16–14 (26 drawn)
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
Agent access
ai-native userPoint an agent at llms.txt or agent-oriented docs
weight 2 · round to ZapierA direct probe confirms docs.zapier.com/llms.txt returns HTTP 200 with a structured index for developer documentation (SDK, MCP, integration building), exactly matching the llms.txt agent-discovery pattern, and this is corroborated by docs describing agent-oriented access points (MCP server, CLI, npm skills). Missing for 10: independent/community confirmation of an agent actually consuming llms.txt successfully.
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.zapier.com/llms.txt # Zapier — docs.zapier.com > Local index for developer documentation: SDK, MCP…”
- [claimed-docs] “Agents discover them on npm and skill registries, then run them as an agent skill, a CLI, a typed Node module, or a local MCP server.”
- [claimed-docs] “Give any MCP-compatible AI client governed access to 9,000+ apps through one connection: no code, no infrastructure, SOC 2 certified.”
Make hosts a live llms.txt at developers.make.com/llms.txt (HTTP 200, confirmed by probe) plus Markdown-formatted 'Make Skills' docs designed for AI assistants, directly supporting agent-oriented documentation consumption. missing for 10: confirmation that all doc subpages (not just the root) resolve as .md, and independent/third-party evidence of agents successfully using llms.txt in practice.
- [probe] “PROBE llms.txt: HTTP 200 at https://developers.make.com/llms.txt # Make Developer Hub ## Home - [Make Developer Hub](https://developers.ma…”
- [claimed-docs] “Make Skills are Markdown files that help your assistant reliably perform Make-specific tasks, including building scenarios, configuring modu…”
- [claimed-docs] “Make Skills are Markdown files that help your assistant reliably perform Make-specific tasks, including building scenarios, configuring modu…”
- [probe] “PROBE docs-md: HTTP 200 at https://developers.make.com/api-documentation.md # Page Not Found The URL `api-documentation` does not exist. Th…”
ai-native userRun the product headlessly / in CI for automation
weight 2 · round to MakeZapier offers a Platform CLI (Node.js) for building/publishing integrations and a Workflow API/Developer Platform, which can be invoked programmatically and scripted in CI for building or deploying integrations, but the core Zap workflow execution itself is primarily triggered by app events/schedules via the visual builder, not designed as a headless batch job runnable in a CI pipeline. There's no documented CLI command or API to 'run a Zap' synchronously in a pipeline the way a CI job would invoke a task. missing for 10: explicit documentation of running/triggering Zap executions headlessly from CI, a CLI/API command to invoke a workflow run synchronously and get results, and independent confirmation of CI-based automation use cases.
- [claimed-docs] “Zapier Platform CLI enables developers to build integrations using Node.js v22, OAuth1/OAuth2 authentication, webhooks, polling triggers, an…”
- [claimed-docs] “Use the Visual Builder for quick, no-code setups or the CLI for full control and customization.”
- [claimed-docs] “Use Zapier's Workflow API and 9,000 integrations to power a built-in automation experience, integration marketplace, or AI workflows.”
- [probe] “official CLI documented at https://docs.zapier.com/integrations/build-cli/overview”
Make exposes a REST API (with auth/scopes) and webhooks that let external systems or CI pipelines trigger, schedule, and manage scenarios without using the UI, which supports headless/automated invocation. However, there is no evidence of an official CLI, containerized runner, or CI-specific integration guide (e.g., GitHub Actions), and the openapi probe returned 404s, suggesting weaker machine-readable API tooling. Missing for 10: dedicated CLI or CI/CD integration docs, confirmed OpenAPI spec, and hands-on evidence of running scenarios in a pipeline.
- [claimed-docs] “All requests to the Make API require authentication with the user authentication token with the relevant scopes enabled.”
- [claimed-docs] “The Make API follows the REST API design. Make API is organized into resource-oriented URLs”
- [claimed-docs] “custom webhooks allow you to create a url to which you can send any data”
- [claimed-docs] “webhooks create a url that you can call from an external app or service, or from another use webhooks to trigger the execution”
- [claimed-docs] “If you don't want to run your immediately after a webhook receives data, you can schedule your to process all webhook requests periodically”
- [claimed-docs] “you can schedule your to process all webhook requests periodically”
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.make.com/openapi.json, https://developers.make.com/swagger.json, https://develope…”
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · round drawnZapiernone0/10All evidence describes Zapier acting as an MCP *server* (zapier.com/mcp) that other AI clients (Claude, ChatGPT, Cursor) connect to in order to use Zapier's own tools — not Zapier acting as an MCP *client* that ingests external MCP servers so Zapier itself can call their tools. No documentation shows Zapier importing or connecting to third-party MCP servers as a consumer.
- [claimed-docs] “Connect Claude, ChatGPT, Cursor, and other AI tools to Gmail, Slack, Salesforce, and 9,000+ apps. No code. No setup headaches.”
- [claimed-docs] “Give any MCP-compatible AI client governed access to 9,000+ apps through one connection: no code, no infrastructure, SOC 2 certified.”
- [claimed-docs] “Zapier MCP gives IT one governed connection across every AI agent your org uses: Claude, ChatGPT, Cursor. Account-level restrictions, manage…”
- [probe] “official MCP server documented at https://zapier.com/mcp”
Makenone0/10All evidence describes Make exposing its own scenarios as an MCP server to external AI clients (Claude, ChatGPT), the reverse of this story's requirement that Make itself act as an MCP client consuming external MCP servers' tools. No documentation shows Make importing or calling third-party MCP servers as tool providers within its scenarios/agents.
- [claimed-docs] “Turns your **active** and **on-demand** scenarios into callable tools for AI”
- [claimed-docs] “AI systems like Claude and ChatGPT act as MCP clients of Make MCP server. The server provides them access to **scenario run** and **manageme…”
- [claimed-docs] “AI systems like Claude and ChatGPT act as MCP clients of Make MCP server.”
- [claimed-docs] “Make MCP server allows AI systems, such as large language models (LLMs), to run scenarios and manage the contents of your Make account.”
- [claimed-docs] “learn about agentic automation with the make ai agents app”
ai-native userConnect an agent via an official MCP server
weight 3 · round drawnZapier ships an official hosted MCP server (zapier.com/mcp) giving any MCP-compatible client (Claude, ChatGPT, Cursor) governed access to 9,000+ apps/40,000+ actions with SOC2-certified, no-code setup, plus a local MCP server option via the CLI. Missing for 10: independent/hands-on third-party verification of the MCP server's reliability beyond vendor docs.
- [claimed-docs] “Connect Claude, ChatGPT, Cursor, and other AI tools to Gmail, Slack, Salesforce, and 9,000+ apps. No code. No setup headaches.”
- [claimed-docs] “Give any MCP-compatible AI client governed access to 9,000+ apps through one connection: no code, no infrastructure, SOC 2 certified.”
- [claimed-docs] “Zapier MCP gives IT one governed connection across every AI agent your org uses: Claude, ChatGPT, Cursor. Account-level restrictions, manage…”
- [claimed-docs] “It lets your AI take real actions across 9,000+ apps and 40,000+ actions, such as sending messages, creating tasks, and updating records”
- [probe] “official MCP server documented at https://zapier.com/mcp”
- [claimed-docs] “Agents discover them on npm and skill registries, then run them as an agent skill, a CLI, a typed Node module, or a local MCP server.”
Make documents an official MCP server that turns scenarios into callable tools for AI systems like Claude/ChatGPT, exposing scenario run and management capabilities, plus Make Skills to help agents connect. Missing for 10: independent/hands-on third-party corroboration and details on auth scopes specific to MCP server usage.
- [claimed-docs] “Turns your **active** and **on-demand** scenarios into callable tools for AI”
- [claimed-docs] “AI systems like Claude and ChatGPT act as MCP clients of Make MCP server. The server provides them access to **scenario run** and **manageme…”
- [claimed-docs] “AI systems like Claude and ChatGPT act as MCP clients of Make MCP server.”
- [claimed-docs] “Make MCP server allows AI systems, such as large language models (LLMs), to run scenarios and manage the contents of your Make account.”
- [claimed-docs] “Make Skills are Markdown files that help your assistant reliably perform Make-specific tasks, including building scenarios, configuring modu…”
- [probe] “official MCP server documented at https://developers.make.com/mcp-server”
ai-native userUse an official CLI
weight 2 · round to ZapierZapier ships an official Platform CLI for building integrations (Node.js, OAuth, webhooks, polling triggers) documented at docs.zapier.com/integrations/build-cli/overview, and docs explicitly note agents can run these as 'a CLI, a typed Node module, or a local MCP server,' tying the CLI directly to AI-agent workflows. Missing for 10: independent/hands-on developer corroboration of CLI usage and more detail on AI-native-specific CLI features beyond general integration building.
- [claimed-docs] “Zapier Platform CLI enables developers to build integrations using Node.js v22, OAuth1/OAuth2 authentication, webhooks, polling triggers, an…”
- [claimed-docs] “Agents discover them on npm and skill registries, then run them as an agent skill, a CLI, a typed Node module, or a local MCP server.”
- [claimed-docs] “Use the Visual Builder for quick, no-code setups or the CLI for full control and customization.”
- [probe] “official CLI documented at https://docs.zapier.com/integrations/build-cli/overview”
ai-native userDrive the product through a documented public API
weight 3 · round to MakeZapier documents a Workflow API for building automation experiences (zapier-docs-23) plus a Platform CLI and REST-style integration building (zapier-docs-3, zapier-docs-19), giving AI-native users programmatic ways to drive the product beyond the UI. However, a probe found no discoverable OpenAPI/swagger spec (zapier-probe-2 returned 404s across all candidate paths), suggesting the public API is not machine-discoverable in a standard way, and most current documentation emphasis is on MCP/agent-skill access rather than a general-purpose public API reference. Missing for 10: a published OpenAPI/swagger spec or full public API reference docs, and independent hands-on confirmation of API usage outside MCP/CLI contexts.
- [claimed-docs] “Use Zapier's Workflow API and 9,000 integrations to power a built-in automation experience, integration marketplace, or AI workflows.”
- [claimed-docs] “Zapier Platform CLI enables developers to build integrations using Node.js v22, OAuth1/OAuth2 authentication, webhooks, polling triggers, an…”
- [claimed-docs] “Use the Visual Builder for quick, no-code setups or the CLI for full control and customization.”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.zapier.com/openapi.json, https://docs.zapier.com/swagger.json, https://docs.zapier.com/…”
- [probe] “official CLI documented at https://docs.zapier.com/integrations/build-cli/overview”
Make documents a public REST API (resource-oriented URLs, token auth, troubleshooting section) plus a first-party MCP server exposing scenario run/management as callable tools, enabling AI-native driving of the product beyond just the raw API. Missing for 10: a working OpenAPI/swagger spec (probe found 404s) and independent hands-on corroboration of the API's completeness/reliability.
- [claimed-docs] “All requests to the Make API require authentication with the user authentication token with the relevant scopes enabled.”
- [claimed-docs] “The Make API follows the REST API design. Make API is organized into resource-oriented URLs”
- [claimed-docs] “If you are experiencing issues with the Make API, go to the Troubleshooting section for tips about what could go wrong and how to fix it.”
- [claimed-docs] “Turns your **active** and **on-demand** scenarios into callable tools for AI”
- [claimed-docs] “AI systems like Claude and ChatGPT act as MCP clients of Make MCP server. The server provides them access to **scenario run** and **manageme…”
- [claimed-docs] “Make MCP server allows AI systems, such as large language models (LLMs), to run scenarios and manage the contents of your Make account.”
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.make.com/openapi.json, https://developers.make.com/swagger.json, https://develope…”
- [probe] “official MCP server documented at https://developers.make.com/mcp-server”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · round drawnZapier MCP docs mention 'governed access', 'account-level restrictions, managed connections, and workspace controls' applied across agents (zapier-docs-11, zapier-docs-15), implying some control over what an agent can touch, and Zapier explicitly manages OAuth/credentials so users never handle tokens directly (zapier-docs-16). However there is no explicit documentation of issuing distinct, minimal-scope credentials per agent/action (e.g., granular OAuth scopes, per-agent API keys) — missing for 10: explicit per-agent scoped credential/token issuance mechanism, documentation of configurable least-privilege permission sets, and independent confirmation that these restrictions actually enforce least privilege.
- [claimed-docs] “Give any MCP-compatible AI client governed access to 9,000+ apps through one connection: no code, no infrastructure, SOC 2 certified.”
- [claimed-docs] “Zapier MCP gives IT one governed connection across every AI agent your org uses: Claude, ChatGPT, Cursor. Account-level restrictions, manage…”
- [claimed-docs] “Zapier handles OAuth, credentials, and API complexity so you never touch a token.”
- [claimed-docs] “It lets your AI take real actions across 9,000+ apps and 40,000+ actions, such as sending messages, creating tasks, and updating records”
Make API tokens support 'relevant scopes enabled' for authentication, indicating some scoped credential capability, and MCP server access can be scoped to specific scenarios/tools rather than full account access. However there's no documentation of granular least-privilege scope definitions, no scope list, no per-agent credential issuance workflow, and no independent verification of enforcement. Missing for 10: a documented list of available API scopes, evidence of fine-grained least-privilege controls (e.g., read-only vs write, resource-level restrictions), and independent/hands-on confirmation that scoped tokens actually restrict agent access as claimed.
- [claimed-docs] “All requests to the Make API require authentication with the user authentication token with the relevant scopes enabled.”
- [claimed-docs] “The Make API follows the REST API design. Make API is organized into resource-oriented URLs”
- [claimed-docs] “Make MCP server allows AI systems, such as large language models (LLMs), to run scenarios and manage the contents of your Make account.”
- [claimed-docs] “View and modify scenarios and their related entities (e.g., connections, webhooks, and data stores)”
ai-native userBuild against official SDKs
weight 2 · round to ZapierZapier documents a typed Node module/CLI SDK (Platform CLI, Node.js v22, OAuth handling) and explicitly positions agents/skills as consuming Zapier as a 'code-file interface' via npm/skill registries, plus a documented MCP server for agent access. However, there's no dedicated 'official SDK' branding beyond the CLI, no OpenAPI spec (probe returned 404s), and no independent/hands-on corroboration of AI-native developers building against these SDKs specifically. missing for 10: independent verification of the AI-native SDK workflow, a published OpenAPI/typed client spec, and community evidence of agents actually building against the SDK rather than just using MCP/no-code paths.
- [claimed-docs] “Zapier Platform CLI enables developers to build integrations using Node.js v22, OAuth1/OAuth2 authentication, webhooks, polling triggers, an…”
- [claimed-docs] “Agents discover them on npm and skill registries, then run them as an agent skill, a CLI, a typed Node module, or a local MCP server.”
- [claimed-docs] “The code-file interface to Zapier. Give coding agents programmatic access to 9,000+ apps: Zapier handles OAuth, credentials, and API complex…”
- [claimed-docs] “Zapier handles OAuth, credentials, and API complexity so you never touch a token.”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.zapier.com/llms.txt # Zapier — docs.zapier.com > Local index for developer documentation: SDK, MCP…”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.zapier.com/openapi.json, https://docs.zapier.com/swagger.json, https://docs.zapier.com/…”
- [probe] “official CLI documented at https://docs.zapier.com/integrations/build-cli/overview”
Makenone0/10Evidence shows a REST API and an MCP server, but no official client SDKs (Python/JS/etc.) or OpenAPI spec are documented—probes for openapi/swagger endpoints returned 404, indicating no formal SDK-generation artifact. The API docs describe raw REST endpoints and auth tokens, not packaged SDK libraries.
- [claimed-docs] “All requests to the Make API require authentication with the user authentication token with the relevant scopes enabled.”
- [claimed-docs] “The Make API follows the REST API design. Make API is organized into resource-oriented URLs”
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.make.com/openapi.json, https://developers.make.com/swagger.json, https://develope…”
ai-native userSubscribe to events via webhooks
weight 2 · round to ZapierZapier's Platform CLI explicitly supports building webhook triggers (subscribe/unsubscribe patterns) alongside polling triggers, and this is a core, well-documented capability for integration builders including AI-native/agent use cases via CLI, MCP, and Workflow API. Missing for 10: independent hands-on verification of webhook subscription specifically (vs. polling) and no explicit example of an AI agent subscribing to a webhook end-to-end.
- [claimed-docs] “Zapier Platform CLI enables developers to build integrations using Node.js v22, OAuth1/OAuth2 authentication, webhooks, polling triggers, an…”
- [claimed-docs] “Use the Visual Builder for quick, no-code setups or the CLI for full control and customization.”
- [probe] “official CLI documented at https://docs.zapier.com/integrations/build-cli/overview”
- [claimed-docs] “Use Zapier's Workflow API and 9,000 integrations to power a built-in automation experience, integration marketplace, or AI workflows.”
Make's custom webhooks let a scenario expose a URL that receives events from external systems and trigger scenario runs, effectively letting a user 'subscribe' to external events via webhook (make-docs-5, make-docs-15, make-docs-25), with queuing/scheduling options (make-docs-6, make-docs-21). However, this is a general automation feature, not something exposed or documented specifically for AI-native/agentic consumption (e.g., no MCP tool or agent-specific API for creating/managing webhook subscriptions is shown). Missing for 10: evidence of webhook subscription management being agent-callable via MCP or API, and any outbound event-notification (pub/sub) webhook mechanism for external AI systems.
- [claimed-docs] “custom webhooks allow you to create a url to which you can send any data”
- [claimed-docs] “webhooks create a url that you can call from an external app or service, or from another use webhooks to trigger the execution”
- [claimed-docs] “webhooks create a url that you can call from an external app or service, or from another use webhooks to trigger the execution of”
- [claimed-docs] “If you don't want to run your immediately after a webhook receives data, you can schedule your to process all webhook requests periodically”
- [claimed-docs] “the whole queue is then processed every time your schedule criteria are met”
Agentic features
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · round to ZapierZapier shows some AI-generated suggestions tied to user workflow data — AI troubleshooting instructions for Zap errors (docs-10) and Canvas's automatic process mapping/optimization (docs-18), plus Copilot helping build agents (docs-8) — but these are narrow, workflow-centric suggestions rather than broad 'insights from your data' analytics. missing for 10: dedicated data-insights/analytics feature, evidence of AI surfacing patterns or recommendations from connected app data (not just error-fixing or workflow mapping), independent/hands-on corroboration of these AI suggestion features actually working.
- [claimed-docs] “Zapier will use AI to create troubleshooting instructions for you to review.”
- [claimed-docs] “Canvas automatically maps and optimizes your processes to help your team document, refine, and automate with ease.”
- [claimed-docs] “Create specialized agents—with the help of Zapier Copilot—to connect to your business data and perform tasks across 9,000+ apps.”
Makenone0/10Evidence shows Make's AI Agents app and MCP server let external AI systems build/run automations and manage scenarios, but there is no evidence of a feature that surfaces AI-generated insights or suggestions from a user's own data inside the product UI.
- [claimed-docs] “learn about agentic automation with the make ai agents app”
- [claimed-docs] “Make MCP server allows AI systems, such as large language models (LLMs), to run scenarios and manage the contents of your Make account.”
ai-native userSet up automations that run autonomously in the background
weight 2 · round drawnZapier's core product is trigger-based automations (Zaps) that run autonomously in the background once set up, and this is extended with AI-native features like Zapier MCP and Agents for triggering/running workflows via AI clients. Community evidence confirms real-world autonomous background execution (e.g., a Zap misfiring and sending thousands of invites unattended), corroborating that these run without active user supervision. Missing for 10: independent hands-on verification specifically of AI-triggered autonomous background runs (vs. classic Zaps), and detail on monitoring/error-recovery for unattended agentic runs beyond the troubleshooting-assistant mention.
- [claimed-docs] “Create specialized agents—with the help of Zapier Copilot—to connect to your business data and perform tasks across 9,000+ apps.”
- [claimed-docs] “It lets your AI take real actions across 9,000+ apps and 40,000+ actions, such as sending messages, creating tasks, and updating records”
- [claimed-docs] “Connect Claude, ChatGPT, Cursor, and other AI tools to Gmail, Slack, Salesforce, and 9,000+ apps. No code. No setup headaches.”
- [community] “One of our users recently found us after screwing up his calendar sync Zap and, on a random Sunday morning, ended up inviting thousands of h…”
- [claimed-docs] “Zapier will use AI to create troubleshooting instructions for you to review.”
Make scenarios are core automations that run autonomously on triggers (webhooks, schedules) in the background without human intervention, with error handling and history/monitoring built in, and can even be exposed as callable tools via MCP for AI orchestration. missing for 10: independent/hands-on evidence of long-running autonomous scenarios at scale, and no third-party corroboration beyond vendor docs.
- [claimed-docs] “custom webhooks allow you to create a url to which you can send any data”
- [claimed-docs] “If you don't want to run your immediately after a webhook receives data, you can schedule your to process all webhook requests periodically”
- [claimed-docs] “webhooks create a url that you can call from an external app or service, or from another use webhooks to trigger the execution”
- [claimed-docs] “you can schedule your to process all webhook requests periodically”
- [claimed-docs] “the whole queue is then processed every time your schedule criteria are met”
- [claimed-docs] “this page helps users navigate errors, diagnose and resolve issues in by providing detailed information on common errors and warnings, error…”
- [claimed-docs] “scenario history”
- [claimed-docs] “Turns your **active** and **on-demand** scenarios into callable tools for AI”
- [claimed-docs] “Make MCP server allows AI systems, such as large language models (LLMs), to run scenarios and manage the contents of your Make account.”
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · round to ZapierZapier ships 'Zapier Agents' and 'Zapier Copilot,' a built-in AI assistant that lets users create agents to perform tasks across 9,000+ apps and even auto-generates troubleshooting help, matching the delegate-to-built-in-assistant story. However, evidence is entirely first-party marketing copy with no independent hands-on verification of how well the assistant performs delegated tasks. Missing for 10: independent/community corroboration of the built-in AI assistant's real-world performance, and more concrete detail on its task scope/limits beyond marketing claims.
- [claimed-docs] “Create specialized agents—with the help of Zapier Copilot—to connect to your business data and perform tasks across 9,000+ apps.”
- [claimed-docs] “Zapier will use AI to create troubleshooting instructions for you to review.”
- [claimed-docs] “Simplify and scale your processes with visual mapping—add owners, notes, and images to create structured, easy-to-follow systems.”
- [claimed-docs] “Canvas automatically maps and optimizes your processes to help your team document, refine, and automate with ease.”
Make documents a 'Make AI Agents' app for 'agentic automation' inside the platform, suggesting a built-in AI agent/assistant capability, but the evidence is a single glancing mention with no detail on how tasks are delegated or what the assistant can do. Missing for 10: detailed docs on the AI Agents app's task-delegation UX, concrete examples of use, and independent/hands-on corroboration of its capabilities.
- [claimed-docs] “learn about agentic automation with the make ai agents app”
ai-native userOperate the product with natural-language commands
weight 2 · round to ZapierZapier MCP explicitly enables natural-language commands: 'Describe what you need in plain language. Your AI calls the right Zapier action and confirms what it did' and 'Schedule a meeting with one prompt,' letting AI clients trigger 40,000+ actions across 9,000+ apps via governed MCP connections. This is well-documented first-party functionality with a dedicated product page, though independent hands-on validation of the natural-language flow itself is absent. Missing for 10: independent/community corroboration of the MCP natural-language experience specifically (community evidence covers classic Zap-building, not the AI prompt-driven flow).
- [claimed-docs] “Describe what you need in plain language. Your AI calls the right Zapier action and confirms what it did.”
- [claimed-docs] “Schedule a meeting with one prompt. Your AI finds time on everyone's calendar and books it. No back and forth.”
- [claimed-docs] “It lets your AI take real actions across 9,000+ apps and 40,000+ actions, such as sending messages, creating tasks, and updating records”
- [claimed-docs] “Connect Claude, ChatGPT, Cursor, and other AI tools to Gmail, Slack, Salesforce, and 9,000+ apps. No code. No setup headaches.”
- [claimed-docs] “Zapier MCP gives IT one governed connection across every AI agent your org uses: Claude, ChatGPT, Cursor. Account-level restrictions, manage…”
- [probe] “official MCP server documented at https://zapier.com/mcp”
Make ships an official MCP server and 'Make AI Agents' app that let LLMs (Claude, ChatGPT) run and manage scenarios via natural-language tool calls, plus 'Make Skills' markdown files to guide assistants — this is real agentic/NL operation support. However, this capability is mediated entirely through external AI clients rather than a built-in natural-language command interface in Make itself, and there is no independent/hands-on corroboration of reliability. Missing for 10: evidence of a native in-product NL command bar/assistant, and third-party/hands-on validation of the MCP-driven workflow.
- [claimed-docs] “Turns your **active** and **on-demand** scenarios into callable tools for AI”
- [claimed-docs] “AI systems like Claude and ChatGPT act as MCP clients of Make MCP server. The server provides them access to **scenario run** and **manageme…”
- [claimed-docs] “learn about agentic automation with the make ai agents app”
- [claimed-docs] “Make MCP server allows AI systems, such as large language models (LLMs), to run scenarios and manage the contents of your Make account.”
- [claimed-docs] “Make Skills are Markdown files that help your assistant reliably perform Make-specific tasks, including building scenarios, configuring modu…”
- [probe] “official MCP server documented at https://developers.make.com/mcp-server”
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round drawnZapiernone0/10Zapier has developer docs, CLI docs, and a Workflow API, so an interactive API reference is a fair axis to expect, but the evidence pack shows no such feature—probes explicitly found no OpenAPI/swagger spec (404s across all candidate paths) and no mention of a runnable/interactive API console anywhere in the docs.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.zapier.com/openapi.json, https://docs.zapier.com/swagger.json, https://docs.zapier.com/…”
- [claimed-docs] “Use Zapier's Workflow API and 9,000 integrations to power a built-in automation experience, integration marketplace, or AI workflows.”
- [claimed-docs] “Zapier Platform CLI enables developers to build integrations using Node.js v22, OAuth1/OAuth2 authentication, webhooks, polling triggers, an…”
Makenone0/10Make provides REST API documentation describing resource-oriented endpoints and authentication (make-docs-1, make-docs-11, make-docs-23), but no evidence shows an interactive reference with runnable/try-it examples; probes for OpenAPI/Swagger specs and even the docs page in machine-readable form returned 404s (make-probe-2, make-probe-3), suggesting no such interactive tooling exists.
- [claimed-docs] “All requests to the Make API require authentication with the user authentication token with the relevant scopes enabled.”
- [claimed-docs] “The Make API follows the REST API design. Make API is organized into resource-oriented URLs”
- [claimed-docs] “If you are experiencing issues with the Make API, go to the Troubleshooting section for tips about what could go wrong and how to fix it.”
- [probe] “PROBE docs-md: HTTP 200 at https://developers.make.com/api-documentation.md # Page Not Found The URL `api-documentation` does not exist. Th…”
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.make.com/openapi.json, https://developers.make.com/swagger.json, https://develope…”
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round drawnZapiernone0/10The probe explicitly found all candidate OpenAPI spec paths returning 404, and no evidence pack item shows a downloadable OpenAPI/Swagger spec; Zapier's Workflow API and integration docs are mentioned but no machine-readable spec is provided. Missing for 10: a publicly downloadable OpenAPI/Swagger JSON or YAML file, any documentation page linking to such a spec.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.zapier.com/openapi.json, https://docs.zapier.com/swagger.json, https://docs.zapier.com/…”
Makenone0/10Make documents its REST API but explicit probes for OpenAPI/swagger specs at standard paths all returned 404, and no downloadable machine-readable spec is referenced anywhere in the docs pack.
- [claimed-docs] “The Make API follows the REST API design. Make API is organized into resource-oriented URLs”
- [probe] “PROBE docs-md: HTTP 200 at https://developers.make.com/api-documentation.md # Page Not Found The URL `api-documentation` does not exist. Th…”
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.make.com/openapi.json, https://developers.make.com/swagger.json, https://develope…”
ai-native userTest against a sandbox environment without touching production data
weight 1 · round drawnZapiernone0/10No evidence pack item mentions a sandbox environment, staging mode, or test data isolation for Zapier's automation/MCP execution; the docs discuss OAuth, integrations, and MCP connectivity but nothing about testing against non-production data. missing for 10: any documentation of a sandbox/test mode, staging environment, or dry-run capability that avoids touching production data.
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round drawnZapiernone0/10No evidence of API versioning scheme or a documented deprecation policy; the OpenAPI probe returned 404s and no docs mention version numbers, sunset timelines, or breaking-change policy for Zapier's Platform API or Workflow API.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.zapier.com/openapi.json, https://docs.zapier.com/swagger.json, https://docs.zapier.com/…”
Makenone0/10The evidence shows Make has a REST API and MCP server documentation, but nowhere is there mention of API versioning scheme, version numbers, or a documented deprecation policy for breaking changes. Probes even show broken/missing OpenAPI spec links, further suggesting no formal versioning artifact is exposed.
- [claimed-docs] “The Make API follows the REST API design. Make API is organized into resource-oriented URLs”
- [claimed-docs] “If you are experiencing issues with the Make API, go to the Troubleshooting section for tips about what could go wrong and how to fix it.”
- [probe] “PROBE docs-md: HTTP 200 at https://developers.make.com/api-documentation.md # Page Not Found The URL `api-documentation` does not exist. Th…”
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.make.com/openapi.json, https://developers.make.com/swagger.json, https://develope…”
Ai workflows — AI in the engine loop — agent-driven editors, copilots, codegen-friendly APIs, runtime inferenceAi workflows
AI in the engine loop — agent-driven editors, copilots, codegen-friendly APIs, runtime inference
Agent integration
ai-native userHave an agent create, update, and activate a workflow programmatically through the public API
weight 2 · round to MakeZapier's Developer Platform page mentions a 'Workflow API' that can power AI workflows and integration marketplaces, implying programmatic Zap creation, but the evidence pack has no concrete docs, endpoints, or examples showing an agent creating/updating/activating a Zap via this API — attempts to find an OpenAPI spec returned 404s. The strongest concrete API surface documented is the Platform CLI/SDK (for building app integrations) and MCP (for invoking existing actions), neither of which directly evidences full CRUD+activate control over workflows. Missing for 10: documented Workflow API reference/schema, example of programmatic Zap creation/update/activation, and independent confirmation it works as described.
- [claimed-docs] “Use Zapier's Workflow API and 9,000 integrations to power a built-in automation experience, integration marketplace, or AI workflows.”
- [claimed-docs] “It lets your AI take real actions across 9,000+ apps and 40,000+ actions, such as sending messages, creating tasks, and updating records”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.zapier.com/openapi.json, https://docs.zapier.com/swagger.json, https://docs.zapier.com/…”
Make's public REST API is documented as resource-oriented and requires token auth, and the MCP server explicitly allows AI systems to view and modify scenarios, run them, and manage account contents, implying create/update/activate capabilities. However, no evidence explicitly documents an API endpoint or example for creating a new scenario or toggling activation state, and the docs snippets are largely generic descriptions rather than concrete workflow-lifecycle examples. missing for 10: explicit API endpoint documentation for scenario creation, explicit 'activate' endpoint/example, and independent confirmation of programmatic activation.
- [claimed-docs] “The Make API follows the REST API design. Make API is organized into resource-oriented URLs”
- [claimed-docs] “View and modify scenarios and their related entities (e.g., connections, webhooks, and data stores)”
- [claimed-docs] “Make MCP server allows AI systems, such as large language models (LLMs), to run scenarios and manage the contents of your Make account.”
- [claimed-docs] “All requests to the Make API require authentication with the user authentication token with the relevant scopes enabled.”
- [probe] “official MCP server documented at https://developers.make.com/mcp-server”
ai-native userExpose my workflows or connected app actions as MCP tools that an external agent can call
weight 3 · round drawnZapier ships an official MCP server (zapier.com/mcp) that exposes connected app actions across 9,000+ apps as callable MCP tools to any MCP-compatible client (Claude, ChatGPT, Cursor), with governed/managed access and account-level controls documented for IT admins. This directly matches the story of exposing workflow/app actions as MCP tools for external agents. missing for 10: independent hands-on verification of the MCP server's reliability/tool-call behavior beyond first-party docs.
- [claimed-docs] “Connect Claude, ChatGPT, Cursor, and other AI tools to Gmail, Slack, Salesforce, and 9,000+ apps. No code. No setup headaches.”
- [claimed-docs] “Give any MCP-compatible AI client governed access to 9,000+ apps through one connection: no code, no infrastructure, SOC 2 certified.”
- [claimed-docs] “Zapier MCP gives IT one governed connection across every AI agent your org uses: Claude, ChatGPT, Cursor. Account-level restrictions, manage…”
- [claimed-docs] “It lets your AI take real actions across 9,000+ apps and 40,000+ actions, such as sending messages, creating tasks, and updating records”
- [probe] “official MCP server documented at https://zapier.com/mcp”
Make offers an official MCP server that turns active/on-demand scenarios into callable tools for AI agents like Claude/ChatGPT, exposing scenario run and management capabilities via a documented protocol; scenarios can connect to third-party app actions, making them exposable as tools. Missing for 10: independent hands-on validation of the MCP server beyond first-party docs and more detail on granular scoping/security of exposed tools.
- [claimed-docs] “Turns your **active** and **on-demand** scenarios into callable tools for AI”
- [claimed-docs] “AI systems like Claude and ChatGPT act as MCP clients of Make MCP server. The server provides them access to **scenario run** and **manageme…”
- [claimed-docs] “AI systems like Claude and ChatGPT act as MCP clients of Make MCP server.”
- [claimed-docs] “Turns your active and on-demand scenarios into callable tools for AI”
- [claimed-docs] “Make MCP server allows AI systems, such as large language models (LLMs), to run scenarios and manage the contents of your Make account.”
- [probe] “official MCP server documented at https://developers.make.com/mcp-server”
Ai authoring
ai-native userGenerate or edit a workflow from a natural-language prompt
weight 2 · round drawnZapier documents 'Zapier Copilot' as an AI assistant to help create agents/workflows and mentions AI-generated troubleshooting instructions for Zaps, indicating some natural-language workflow creation/editing capability, but the evidence pack lacks concrete detail on how Copilot actually builds or edits a full multi-step Zap from a prompt, and there's no independent/hands-on corroboration of this specific capability. missing for 10: detailed docs/demo of Copilot generating or editing a full Zap workflow, independent user reports confirming it works as described.
- [claimed-docs] “Create specialized agents—with the help of Zapier Copilot—to connect to your business data and perform tasks across 9,000+ apps.”
- [claimed-docs] “Zapier will use AI to create troubleshooting instructions for you to review.”
- [claimed-docs] “Describe what you need in plain language. Your AI calls the right Zapier action and confirms what it did.”
Make's docs show 'Make Skills' (Markdown files) enabling an AI assistant to build and configure scenarios via the MCP server, and the MCP server lets AI systems like Claude/ChatGPT manage scenario contents — implying prompt-driven workflow creation/editing through external AI clients. However, this is an indirect, third-party-assistant-mediated path rather than a documented native in-product 'type a prompt, get a workflow' feature, and there's no hands-on or independent verification of it working. Missing for 10: a native first-party natural-language-to-workflow builder in the Make UI, concrete examples/screenshots of prompt-generated scenarios, and independent hands-on corroboration.
- [claimed-docs] “Make Skills are Markdown files that help your assistant reliably perform Make-specific tasks, including building scenarios, configuring modu…”
- [claimed-docs] “Make Skills are Markdown files that help your assistant reliably perform Make-specific tasks, including building scenarios, configuring modu…”
- [claimed-docs] “Make MCP server allows AI systems, such as large language models (LLMs), to run scenarios and manage the contents of your Make account.”
- [claimed-docs] “learn about agentic automation with the make ai agents app”
Ai steps
ai-native userAdd AI agent or LLM steps inside a workflow, with model choice and tool use
weight 3 · round drawnZapier's agents.zapier.com/agents page and Copilot indicate you can create AI agents that connect to business data and perform tasks across thousands of apps, implying LLM+tool-use steps inside workflows, but the evidence never specifies model choice (e.g., selecting GPT vs Claude) or granular tool-use configuration within a Zap step. missing for 10: explicit documentation of selectable LLM/model options inside a workflow step, detailed tool-use/function-calling configuration, and independent hands-on confirmation of the AI-agent-in-workflow experience.
- [claimed-docs] “Create specialized agents—with the help of Zapier Copilot—to connect to your business data and perform tasks across 9,000+ apps.”
- [claimed-docs] “It lets your AI take real actions across 9,000+ apps and 40,000+ actions, such as sending messages, creating tasks, and updating records”
- [claimed-docs] “Zapier will use AI to create troubleshooting instructions for you to review.”
Make has a dedicated 'AI Agents' app (make-docs-9) for agentic automation within workflows, implying model choice and tool use, but the evidence pack lacks first-party documentation detailing how to configure model selection or tool/function definitions within an agent step — most evidence instead focuses on the MCP server (which exposes Make scenarios as tools to external AI clients like Claude/ChatGPT, the reverse direction). missing for 10: detailed docs on adding an AI/LLM step inside a scenario, configuring model provider/choice, and defining tool use within that step, plus independent/hands-on confirmation of this workflow.
- [claimed-docs] “learn about agentic automation with the make ai agents app”
- [claimed-docs] “Turns your **active** and **on-demand** scenarios into callable tools for AI”
- [claimed-docs] “Make MCP server allows AI systems, such as large language models (LLMs), to run scenarios and manage the contents of your Make account.”
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
ai-native userPerform bulk operations across many items at once
weight 2 · round to MakeZapiernone0/10The evidence pack describes single-trigger, per-event automation (webhooks, triggers/actions, MCP calls) and even highlights community complaints about execution limits and workflows breaking down at complexity, but nothing documents batch/bulk item processing across many records at once.
- [community] “We see a number of users sign up for our service after having tried Zapier to solve their problem... simple 'if this then that' types of wor…”
- [community] “For me it was that IFTTT allows only one IF condition and one THEN step, whereas Zapier allows more simultaneous IFs & THENs. IFTTT is free …”
- [claimed-docs] “It lets your AI take real actions across 9,000+ apps and 40,000+ actions, such as sending messages, creating tasks, and updating records”
Make's webhook queue processing and API/data-store functions imply some capacity for handling batches of items via scenarios, and the REST API with scoped tokens could be scripted for bulk actions, but no evidence documents a native bulk-operation feature (e.g., batch endpoints, bulk item processing UI, or iterator-based bulk automation) for AI-native use. missing for 10: explicit documentation of batch/bulk API endpoints or iterator modules for processing many items in one call, evidence of AI agents invoking bulk operations via MCP server, and any hands-on confirmation of bulk throughput/performance.
- [claimed-docs] “custom webhooks allow you to create a url to which you can send any data”
- [claimed-docs] “If you don't want to run your immediately after a webhook receives data, you can schedule your to process all webhook requests periodically”
- [claimed-docs] “the whole queue is then processed every time your schedule criteria are met”
- [claimed-docs] “transform and format data using our range of functions”
- [claimed-docs] “The Make API follows the REST API design. Make API is organized into resource-oriented URLs”
- [claimed-docs] “Make MCP server allows AI systems, such as large language models (LLMs), to run scenarios and manage the contents of your Make account.”
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round to ZapierZapier's core product is trigger-action automation (Zaps): defining rules that fire actions when events occur across 9,000+ apps, with visual builder or CLI, plus AI-native surfaces (MCP, agent skills) that let AI tools invoke these automations. Community evidence corroborates real-world use for exactly this purpose, though some note limits on conditional complexity for advanced logic. Missing for 10: independent benchmarking of reliability/complexity limits and clearer first-party documentation of advanced conditional/multi-step trigger logic.
- [claimed-docs] “Build a Zapier integration - design triggers and actions for your product, wire up authentication, then publish to the App Directory.”
- [claimed-docs] “Simplify and scale your processes with visual mapping—add owners, notes, and images to create structured, easy-to-follow systems.”
- [claimed-docs] “It lets your AI take real actions across 9,000+ apps and 40,000+ actions, such as sending messages, creating tasks, and updating records”
- [community] “The options were: bump a dev to build the integration, pay ~$50/month to enable a non-technical person to build it via Zapier, or don't get …”
- [community] “We see a number of users sign up for our service after having tried Zapier to solve their problem... simple 'if this then that' types of wor…”
- [community] “Resonate a lot with the gaps with Zapier, particularly around the need for escape hatches/conditional logic when needed.”
Make's core scenario model is built on trigger-action automation: webhooks let users create URLs that trigger scenario execution on external events, schedules can batch-process queued events, and error handlers manage automated fault-response actions. This directly matches the story of defining rules that fire actions on events, though evidence is entirely first-party docs. Missing for 10: independent/hands-on verification and concrete examples of complex conditional rule logic beyond webhooks/schedules.
- [claimed-docs] “custom webhooks allow you to create a url to which you can send any data”
- [claimed-docs] “If you don't want to run your immediately after a webhook receives data, you can schedule your to process all webhook requests periodically”
- [claimed-docs] “webhooks create a url that you can call from an external app or service, or from another use webhooks to trigger the execution”
- [claimed-docs] “you can schedule your to process all webhook requests periodically”
- [claimed-docs] “the whole queue is then processed every time your schedule criteria are met”
- [claimed-docs] “webhooks create a url that you can call from an external app or service, or from another use webhooks to trigger the execution of”
- [claimed-docs] “this page helps users navigate errors, diagnose and resolve issues in by providing detailed information on common errors and warnings, error…”
- [claimed-docs] “diagnose and resolve issues in by providing detailed information on common errors and warnings, error handlers”
ai-native userSchedule recurring jobs or workflows
weight 2 · round to MakeZapier's platform is built around triggers/actions including polling triggers (zapier-docs-3) and Visual Builder/CLI workflow creation (zapier-docs-19, zapier-docs-22), which implicitly support recurring, trigger-based automations, but the evidence pack never shows an AI agent explicitly scheduling or configuring a recurring job through MCP — the MCP examples (zapier-docs-7, zapier-docs-20, zapier-docs-24) describe one-off actions like booking a single meeting or calling an action, not setting up persistent recurring workflows. Missing for 10: explicit documentation of an AI/MCP-driven interface for creating or managing scheduled/recurring Zaps, and independent confirmation that AI agents can configure recurrence intervals rather than just trigger single actions.
- [claimed-docs] “Zapier Platform CLI enables developers to build integrations using Node.js v22, OAuth1/OAuth2 authentication, webhooks, polling triggers, an…”
- [claimed-docs] “Use the Visual Builder for quick, no-code setups or the CLI for full control and customization.”
- [claimed-docs] “the Visual Builder is the place to start. It’s ideal for quick deployment and collaboration across teams, even without developer expertise.”
- [claimed-docs] “Schedule a meeting with one prompt. Your AI finds time on everyone's calendar and books it. No back and forth.”
- [claimed-docs] “It lets your AI take real actions across 9,000+ apps and 40,000+ actions, such as sending messages, creating tasks, and updating records”
Make's docs confirm native scenario scheduling ('schedule a scenario') and webhook queues that can be processed on a periodic schedule, directly supporting recurring automated workflows. Missing for 10: independent/hands-on confirmation of scheduling reliability, details on schedule granularity/frequency options, and any AI-specific scheduling interface beyond generic scenario scheduling.
- [claimed-docs] “schedule a scenario docid 8rwfo krohjlepg4qhx3 clone a scenario docid\ c8f35kwpicyg1az5vlgehdelete a scenario”
- [claimed-docs] “If you don't want to run your immediately after a webhook receives data, you can schedule your to process all webhook requests periodically”
- [claimed-docs] “you can schedule your to process all webhook requests periodically”
- [claimed-docs] “the whole queue is then processed every time your schedule criteria are met”
ai-native userVersion, review, and roll back my automations
weight 1 · round to MakeZapiernone0/10The evidence pack covers building integrations, MCP/agent access, embedding, and troubleshooting suggestions, but contains no mention of versioning Zaps, reviewing change history, or rolling back automations to a prior state.
Make documents 'scenario history' and the ability to 'clone a scenario', which suggest some versioning/backup capability, but there is no explicit documentation of a review/diff UI or a true rollback mechanism restoring a prior version. missing for 10: explicit rollback/revert feature docs, version diff/review UI, and independent confirmation that history can restore a scenario to an earlier state.
- [claimed-docs] “clone a scenario”
- [claimed-docs] “scenario history”
- [claimed-docs] “schedule a scenario docid 8rwfo krohjlepg4qhx3 clone a scenario docid\ c8f35kwpicyg1az5vlgehdelete a scenario”
Code extensibility — stories about code extensibility in this arenaCode extensibility
Stories about code extensibility in this arena
Code steps
developerDrop into real code (JavaScript or Python) as a step inside a workflow
weight 3 · round drawnZapiernone0/10The evidence pack never documents a native 'Code by Zapier' step allowing inline JavaScript/Python inside a Zap; the closest content is about the CLI for building whole integrations (zapier-docs-3, zapier-docs-19), not an in-workflow code step. A community comment even complains about the lack of an easy way to 'write some if or just 2 lines of code' inside Zaps (zapier-comm-11, zapier-comm-13), reinforcing that this specific capability isn't evidenced.
- [claimed-docs] “Use the Visual Builder for quick, no-code setups or the CLI for full control and customization.”
- [claimed-docs] “Zapier Platform CLI enables developers to build integrations using Node.js v22, OAuth1/OAuth2 authentication, webhooks, polling triggers, an…”
- [community] “As an engineer using Zapier (for the first time) these past few months I got so frustrated by the lack of an option to just write some 'if' …”
- [community] “Resonate a lot with the gaps with Zapier, particularly around the need for escape hatches/conditional logic when needed.”
Makenone0/10The evidence pack covers Make's API, webhooks, MCP server, error handling, and functions, but contains no mention of a custom code step, JavaScript/Python module, or code-execution capability inside a Make scenario. No evidence supports the ability to write and run custom code as a workflow step.
Connector dev
developerBuild a custom connector or private integration with a documented developer platform, SDK, or CLI
weight 2 · round to ZapierZapier documents a full Platform CLI (Node.js, OAuth1/2, webhooks, polling triggers, HTTP middleware) plus a Visual Builder for building and publishing custom integrations to the App Directory, and an embedded/developer platform API for private integrations. Independent probe confirms the CLI docs page and developer llms.txt index exist, corroborating first-party docs. Missing for 10: independent third-party hands-on account of building a CLI integration end-to-end (community evidence covers using Zaps, not building CLI-based custom connectors).
- [claimed-docs] “Zapier Platform CLI enables developers to build integrations using Node.js v22, OAuth1/OAuth2 authentication, webhooks, polling triggers, an…”
- [claimed-docs] “Use the Visual Builder for quick, no-code setups or the CLI for full control and customization.”
- [claimed-docs] “the Visual Builder is the place to start. It’s ideal for quick deployment and collaboration across teams, even without developer expertise.”
- [claimed-docs] “Build a Zapier integration - design triggers and actions for your product, wire up authentication, then publish to the App Directory.”
- [claimed-docs] “Use Zapier's Workflow API and 9,000 integrations to power a built-in automation experience, integration marketplace, or AI workflows.”
- [probe] “official CLI documented at https://docs.zapier.com/integrations/build-cli/overview”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.zapier.com/llms.txt # Zapier — docs.zapier.com > Local index for developer documentation: SDK, MCP…”
Make provides a documented Custom Apps platform (App components: Base, Connections, Webhooks, Modules, Remote Procedure Calls) plus a REST API for building custom connectors/integrations, directly matching the story. Missing for 10: no confirmed official CLI or OpenAPI spec (probe found 404s for openapi.json/swagger.json and a broken docs-md page), and no independent/hands-on corroboration of connector-building success.
- [claimed-docs] “App components * [Base] * [Connections] * [Webhooks] * [Modules] * [Remote Procedure Calls]”
- [claimed-docs] “The Make API follows the REST API design. Make API is organized into resource-oriented URLs”
- [claimed-docs] “All requests to the Make API require authentication with the user authentication token with the relevant scopes enabled.”
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.make.com/openapi.json, https://developers.make.com/swagger.json, https://develope…”
- [probe] “PROBE docs-md: HTTP 200 at https://developers.make.com/api-documentation.md # Page Not Found The URL `api-documentation` does not exist. Th…”
Data mapping
ops userMap and transform data between steps with expressions, functions, or formulas
weight 2 · round to MakeZapierdisputedcontradicted4/10Zapier's docs gesture at building and mapping data through the Visual Builder or CLI (zapier-docs-19, zapier-docs-22) and Canvas process mapping (zapier-docs-9, zapier-docs-18), but none of the evidence explicitly documents formula/expression/function-based field mapping between steps. Community evidence directly contradicts smooth delivery of this capability: an engineer using Zapier reports being 'frustrated by the lack of an option to just write some if or just 2 lines of code' and another user 'resonates a lot with the gaps... around the need for escape hatches/conditional logic' (zapier-comm-11, zapier-comm-13), and a separate user notes complex logic 'starts to break down' (zapier-comm-3). Missing for 10: explicit vendor documentation of Formatter/Code-by-Zapier style expression/function steps and independent confirmation they work well for complex transformations.
- [claimed-docs] “Use the Visual Builder for quick, no-code setups or the CLI for full control and customization.”
- [claimed-docs] “the Visual Builder is the place to start. It’s ideal for quick deployment and collaboration across teams, even without developer expertise.”
- [claimed-docs] “Simplify and scale your processes with visual mapping—add owners, notes, and images to create structured, easy-to-follow systems.”
- [claimed-docs] “Canvas automatically maps and optimizes your processes to help your team document, refine, and automate with ease.”
- [community] “As an engineer using Zapier (for the first time) these past few months I got so frustrated by the lack of an option to just write some 'if' …”
- [community] “Resonate a lot with the gaps with Zapier, particularly around the need for escape hatches/conditional logic when needed.”
- [community] “We see a number of users sign up for our service after having tried Zapier to solve their problem... simple 'if this then that' types of wor…”
Make docs confirm a dedicated functions system for transforming/formatting data between modules (make-docs-8), which is the core mapping/expression mechanism ops users use between steps. However, evidence lacks depth on formula syntax, custom function scripting (e.g., IML/JS custom functions), or hands-on examples of complex transformations. missing for 10: detailed docs/examples of expression syntax, custom JS functions, and independent validation of transformation capabilities.
- [claimed-docs] “transform and format data using our range of functions”
Collaboration governance — stories about collaboration governance in this arenaCollaboration governance
Stories about collaboration governance in this arena
Credentials
ops userStore connection credentials centrally, share them with my team, and control who can use which credential
weight 3 · round to ZapierZapier docs confirm centralized OAuth/credential handling and reuse of existing 'connections' across the org, plus 'managed connections' and 'workspace controls' governing access for MCP/agent use (zapier-docs-15, zapier-docs-12, zapier-docs-16). However, there's no detailed documentation of granular per-credential sharing/permission assignment (e.g., which specific team members can use which specific credential) beyond high-level 'account-level restrictions'. Missing for 10: explicit admin UI/workflow for assigning credential-level permissions, role-based access control details, and independent corroboration of these governance claims.
- [claimed-docs] “Zapier MCP gives IT one governed connection across every AI agent your org uses: Claude, ChatGPT, Cursor. Account-level restrictions, manage…”
- [claimed-docs] “Zapier brings in your existing app connections automatically. Gmail, Slack, Salesforce, whatever you've already set up in Zapier is ready to…”
- [claimed-docs] “Zapier handles OAuth, credentials, and API complexity so you never touch a token.”
- [claimed-docs] “Give any MCP-compatible AI client governed access to 9,000+ apps through one connection: no code, no infrastructure, SOC 2 certified.”
Makenone0/10The evidence pack only lists 'Connections' as an app component category in custom-app developer docs (make-docs-10); there is no evidence describing centralized credential storage, team sharing, or per-credential access control for ops users.
- [claimed-docs] “App components * [Base] * [Connections] * [Webhooks] * [Modules] * [Remote Procedure Calls]”
Human in the loop
ops userPause a workflow to wait for human approval or input before it continues
weight 2 · round drawnZapiernone0/10No evidence in the pack mentions Zapier's built-in 'Human in the Loop'/approval step, delay/pause-for-input actions, or any pause-and-resume-for-approval workflow feature; the pack covers integrations, MCP, canvas, and platform building only.
Makenone0/10The evidence pack covers webhooks, error handling, MCP server, and API docs, but contains no mention of a human-in-the-loop approval step, pause/resume mechanism, or manual confirmation module within Make scenarios. missing for 10: any documentation of a 'wait for input/approval' or manual confirmation module, pause/resume scenario capability, or timeout-based human approval feature.
Versioning
developerVersion workflows through source control or environments and promote changes from dev to production
weight 2 · round drawnZapiernone0/10Evidence covers building integrations via CLI/Visual Builder and embedding/MCP access, but nothing describes version control integration, environments (dev/staging/prod), or promotion/deployment pipelines for Zap workflows. No mention of git-based versioning, environment variables per stage, or a promote-to-production workflow mechanism.
Makenone0/10Evidence only shows scenario cloning and scenario history features, with no documentation of source-control integration, environment separation, or dev-to-production promotion workflows for Make scenarios.
- [claimed-docs] “clone a scenario”
- [claimed-docs] “scenario history”
- [claimed-docs] “schedule a scenario docid 8rwfo krohjlepg4qhx3 clone a scenario docid\ c8f35kwpicyg1az5vlgehdelete a scenario”
Connectors ecosystem — stories about connectors ecosystem in this arenaConnectors ecosystem
Stories about connectors ecosystem in this arena
Community
developerInstall community-built nodes, components, or integrations contributed outside the vendor
weight 1 · round to ZapierZapier's Platform CLI lets third-party developers build integrations and publish them to the App Directory (zapier-docs-1, zapier-docs-3, zapier-docs-19), and docs mention agents discovering Zapier-built skills via npm/skill registries outside Zapier's direct distribution (zapier-docs-4). But these are vendor-reviewed App Directory listings, not an open community-contribution marketplace akin to freely shared nodes; there's no evidence of a permissionless community repository or independent developer reports of installing unofficial/community nodes. Missing for 10: evidence of an open, unreviewed community marketplace, independent confirmation of installing non-vendor-approved integrations, and details on moderation/openness of the contribution process.
- [claimed-docs] “Build a Zapier integration - design triggers and actions for your product, wire up authentication, then publish to the App Directory.”
- [claimed-docs] “Zapier Platform CLI enables developers to build integrations using Node.js v22, OAuth1/OAuth2 authentication, webhooks, polling triggers, an…”
- [claimed-docs] “Agents discover them on npm and skill registries, then run them as an agent skill, a CLI, a typed Node module, or a local MCP server.”
- [claimed-docs] “Use the Visual Builder for quick, no-code setups or the CLI for full control and customization.”
- [claimed-docs] “the Visual Builder is the place to start. It’s ideal for quick deployment and collaboration across teams, even without developer expertise.”
Make provides a Custom Apps SDK (Base, Connections, Webhooks, Modules, RPCs) that lets developers build custom integrations, implying a framework where community-built apps could exist, but there is no evidence of a marketplace, directory, or install flow for discovering and installing third-party/community-contributed apps or modules into a Make account. missing for 10: evidence of a public app marketplace/store, discovery of community apps, one-click install of third-party nodes, and any review/vetting process for community contributions.
- [claimed-docs] “App components * [Base] * [Connections] * [Webhooks] * [Modules] * [Remote Procedure Calls]”
Connectors
ops userConnect to thousands of apps through prebuilt, vendor-maintained integrations
weight 3 · round to ZapierZapier provides thousands of prebuilt, vendor-maintained app integrations (9,000+ apps cited repeatedly) accessible via Visual Builder, MCP, and API, corroborated by independent community reports confirming the breadth (~1,000+) and ease of use of its integration catalog compared to competitors. Missing for 10: no independent third-party audit of the full current app count or comprehensive vendor-maintenance quality across all 9,000+ integrations.
- [claimed-docs] “Give coding agents programmatic access to 9,000+ apps: Zapier handles OAuth, credentials, and API complexity so you never touch a token.”
- [claimed-docs] “Connect Claude, ChatGPT, Cursor, and other AI tools to Gmail, Slack, Salesforce, and 9,000+ apps. No code. No setup headaches.”
- [claimed-docs] “Zapier brings in your existing app connections automatically. Gmail, Slack, Salesforce, whatever you've already set up in Zapier is ready to…”
- [claimed-docs] “It lets your AI take real actions across 9,000+ apps and 40,000+ actions, such as sending messages, creating tasks, and updating records”
- [community] “Zapier has about 1,000 integrations, more than any of their closest competitors and at a price that is far less than others in their space.”
- [community] “The options were: bump a dev to build the integration, pay ~$50/month to enable a non-technical person to build it via Zapier, or don't get …”
Makenone0/10The evidence pack covers Make's API, webhooks, MCP server, and custom-app-building framework (Base/Connections/Webhooks/Modules/RPC), but contains no citation confirming a marketplace of thousands of prebuilt, vendor-maintained app connectors. Missing for 10: any documentation or listing of the app/connector marketplace, connector count, or vendor-maintenance claims.
- [claimed-docs] “App components * [Base] * [Connections] * [Webhooks] * [Modules] * [Remote Procedure Calls]”
- [claimed-docs] “The Make API follows the REST API design. Make API is organized into resource-oriented URLs”
Templates
ops userStart from a public library of workflow templates instead of building from scratch
weight 2 · round drawnZapiernone0/10The evidence pack covers building integrations, MCP, embedding, and Canvas, but nowhere mentions a public gallery/library of pre-built workflow templates that ops users can start from instead of building from scratch. Without any documentation or community mention of a templates library, this applicable ecosystem capability is unevidenced.
Makenone0/10The evidence pack covers Make's API, MCP server, webhooks, error handling, and scenario management, but contains no mention of a public template library or gallery that ops users could start from instead of building scenarios from scratch. Missing for 10: any documentation of a templates gallery, marketplace, or pre-built scenario library, and evidence of browsing/importing templates.
Deployment embedding — stories about deployment embedding in this arenaDeployment embedding
Stories about deployment embedding in this arena
Embedding
developerEmbed the automation platform white-label inside my own product for my customers
weight 1 · round to ZapierZapier's Developer Platform explicitly supports white-label embedding via its Workflow API and Embed offerings, letting customers run automations/workflows under the host product's own brand without leaving the app. missing for 10: independent/hands-on case studies of a real embedded white-label deployment, and pricing/setup details for the embed program.
- [claimed-docs] “Embed Zapier's automation capabilities directly into your product so users can connect apps and run automations under your brand.”
- [claimed-docs] “Bring Zapier’s automation into your own product so customers can build workflows and run actions without leaving your app.”
- [claimed-docs] “Bring Zapier's automation into your own product so customers can build workflows and run actions without leaving your app.”
- [claimed-docs] “Embed Zapier’s automation capabilities directly into your product so users can connect apps and run automations under your brand.”
- [claimed-docs] “Use Zapier's Workflow API and 9,000 integrations to power a built-in automation experience, integration marketplace, or AI workflows.”
Makenone0/10The evidence pack covers Make's API, webhooks, MCP server, and app-building docs, but contains no mention of white-labeling, embeddable widgets, custom branding, or an embed SDK for reselling Make inside a third-party product. Absence of evidence for this applicable capability yields 'none'.
Local dev
developerRun workflows locally or against a dev instance for development and CI testing
weight 2 · round drawnZapiernone0/10Evidence shows only cloud-hosted Zap execution and a CLI for building integration triggers/actions (with local scaffolding), but nothing about running actual Zap workflows locally or against a dedicated dev/staging instance for CI testing. Missing for 10: any documented local workflow execution mode, sandbox/dev environment for Zaps, or CI integration testing tooling.
- [claimed-docs] “Zapier Platform CLI enables developers to build integrations using Node.js v22, OAuth1/OAuth2 authentication, webhooks, polling triggers, an…”
- [claimed-docs] “Use the Visual Builder for quick, no-code setups or the CLI for full control and customization.”
- [probe] “official CLI documented at https://docs.zapier.com/integrations/build-cli/overview”
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
ai-native userDo everything through the API that I can do in the UI
weight 2 · round to MakeZapier documents a Workflow API, Platform CLI, and MCP server that let external/agent callers create integrations and trigger actions across 9,000+ apps, suggesting substantial programmatic parity with the UI. However, the probe found no public OpenAPI spec (all candidate URLs 404), and there is no evidence that all UI capabilities (e.g., full Zap editing, Canvas, troubleshooting AI) are exposed via API, so full UI/API parity is unconfirmed. Missing for 10: a documented OpenAPI/complete API reference, explicit statement of full CRUD parity for Zap management via API, and independent confirmation that all UI features are API-accessible.
- [claimed-docs] “Use Zapier's Workflow API and 9,000 integrations to power a built-in automation experience, integration marketplace, or AI workflows.”
- [claimed-docs] “Zapier Platform CLI enables developers to build integrations using Node.js v22, OAuth1/OAuth2 authentication, webhooks, polling triggers, an…”
- [claimed-docs] “Use the Visual Builder for quick, no-code setups or the CLI for full control and customization.”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.zapier.com/openapi.json, https://docs.zapier.com/swagger.json, https://docs.zapier.com/…”
- [claimed-docs] “It lets your AI take real actions across 9,000+ apps and 40,000+ actions, such as sending messages, creating tasks, and updating records”
Make ships a documented, resource-oriented REST API covering scenarios, connections, webhooks, and data stores (make-docs-11, make-docs-14), plus an MCP server that lets AI systems run and manage scenarios (make-docs-3, make-docs-20). However, there's no evidence of a formal, discoverable OpenAPI spec (probe found 404s at standard locations, make-probe-3) and no explicit documentation confirming full parity for scenario-building/editing logic via API as opposed to the UI or Make Skills workflow. missing for 10: explicit API endpoints for full scenario creation/editing parity, public OpenAPI schema, independent confirmation of 1:1 UI/API feature parity.
- [claimed-docs] “The Make API follows the REST API design. Make API is organized into resource-oriented URLs”
- [claimed-docs] “View and modify scenarios and their related entities (e.g., connections, webhooks, and data stores)”
- [claimed-docs] “AI systems like Claude and ChatGPT act as MCP clients of Make MCP server. The server provides them access to **scenario run** and **manageme…”
- [claimed-docs] “Make MCP server allows AI systems, such as large language models (LLMs), to run scenarios and manage the contents of your Make account.”
- [probe] “PROBE openapi: all candidate paths 404 (https://developers.make.com/openapi.json, https://developers.make.com/swagger.json, https://develope…”
ai-native userExport all of my data in open formats and leave
weight 3 · round drawnZapiernone0/10No evidence of any data export feature (e.g., exporting Zaps, workflow configs, or automation history in open/portable formats) that would let a user leave the platform with their data intact; evidence focuses on integrations, MCP, and building automations, not on data portability/export.
Makenone0/10Evidence covers Make's REST API, webhooks, MCP server, and scenario management, but nothing addresses a bulk/full account data export feature or open-format portability guarantee that would let a user leave with all their data. Missing for 10: documented data export/download feature, open format (e.g., JSON/CSV) export of scenarios and data stores, any GDPR-style account export or migration tooling.
ai-native userRead the product's source under an open license
weight 2 · round drawnZapiernone0/10Zapier is a closed-source, proprietary SaaS platform; no evidence of any open-license source availability (only CLI/SDK docs for building integrations, not the product's own source). This is an applicable axis for judging openness but no evidence supports it, so verdict is none.
ai-native userSelf-host the core product
weight 3 · round drawnZapiernone0/10The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
ai-native userChoose where my data is stored (region/residency)
weight 2 · round drawnZapiernone0/10No evidence in the pack mentions data residency, region selection, or storage location controls for Zapier's automation or MCP data; SOC 2 certification is mentioned but that addresses security compliance, not residency choice.
ai-native userPrevent my data from being used to train AI models
weight 3 · round drawnZapiernone0/10No evidence pack item addresses AI training data usage, opt-out controls, or data privacy policies regarding model training; only SOC 2 certification is mentioned in passing without connection to training data opt-out.
ai-native userControl data retention and deletion
weight 2 · round drawnZapiernone0/10No evidence in the pack addresses data retention policies, deletion controls, or data lifecycle management for AI-native users; the pack only covers integrations, MCP connectivity, and automation features. Mentions of SOC 2 certification touch security posture but not retention/deletion controls specifically.
Makenone0/10The evidence pack contains no documentation of data retention policies, data deletion requests, or privacy/data lifecycle controls for AI-native users; only tangential scenario-management references (e.g., 'delete a scenario') exist, which do not address retention or deletion of underlying data/logs.
- [claimed-docs] “schedule a scenario docid 8rwfo krohjlepg4qhx3 clone a scenario docid\ c8f35kwpicyg1az5vlgehdelete a scenario”
ai-native userOpt out of telemetry and usage tracking
weight 2 · round drawnZapiernone0/10No evidence in the pack addresses telemetry/usage-tracking opt-out settings for Zapier; nothing about privacy controls, data collection preferences, or analytics opt-out is documented. missing for 10: any documentation of telemetry collection, an opt-out toggle/setting, or a privacy policy statement addressing usage tracking controls.
Reliability errors — stories about reliability errors in this arenaReliability errors
Stories about reliability errors in this arena
Durability
developerThrottle or queue workflow executions to respect downstream rate limits
weight 1 · round to MakeZapiernone0/10No evidence pack item mentions throttling, rate-limit handling, queuing, or delay/concurrency controls for workflow executions; docs focus on building integrations, MCP, embedding, and app connections. Community threads even highlight breakage/complexity issues but nothing about rate-limit throttling or queue controls.
Make's webhook documentation shows a queuing mechanism where incoming webhook data can be scheduled to be processed periodically in batches rather than immediately, which functions as a basic queue (make-docs-6, make-docs-16, make-docs-21). However, there is no documented general-purpose throttling/rate-limit control for scenario executions against downstream APIs, and no explicit concurrency or rate-limit configuration feature is evidenced. Missing for 10: explicit rate-limit/throttle settings for scenario modules calling downstream APIs, documentation of concurrency controls, and any independent/hands-on confirmation that queuing reliably respects downstream limits.
- [claimed-docs] “If you don't want to run your immediately after a webhook receives data, you can schedule your to process all webhook requests periodically”
- [claimed-docs] “you can schedule your to process all webhook requests periodically”
- [claimed-docs] “the whole queue is then processed every time your schedule criteria are met”
- [claimed-docs] “custom webhooks allow you to create a url to which you can send any data”
- [claimed-docs] “webhooks create a url that you can call from an external app or service, or from another use webhooks to trigger the execution”
developerRun long-lived workflows that wait for days and survive worker or platform restarts without losing state
weight 2 · round drawnZapiernone0/10The evidence pack contains no documentation or reports about Zapier's workflow execution durability, delay/wait steps surviving restarts, or state persistence guarantees; community comments even suggest complex workflows 'break down' and that Zapier is 'too high level' compared to durable-execution tools like Temporal, but no concrete confirmation or denial of long-lived, restart-surviving workflows is present.
- [community] “Zapier (and similar) is just a little too high level for a lot of our needs, but Temporal feels like overkill.”
- [community] “We see a number of users sign up for our service after having tried Zapier to solve their problem... simple 'if this then that' types of wor…”
Makenone0/10Make is a scenario-based automation platform; while it supports scheduling and webhook queuing, there is no evidence of durable long-running workflow execution primitives (e.g., multi-day waits with guaranteed state persistence across worker/platform restarts) comparable to durable-execution frameworks. Evidence only covers webhooks, scheduling, error handling, and MCP server — none address long-lived stateful workflow durability.
- [claimed-docs] “custom webhooks allow you to create a url to which you can send any data”
- [claimed-docs] “If you don't want to run your immediately after a webhook receives data, you can schedule your to process all webhook requests periodically”
- [claimed-docs] “the whole queue is then processed every time your schedule criteria are met”
- [claimed-docs] “this page helps users navigate errors, diagnose and resolve issues in by providing detailed information on common errors and warnings, error…”
Error handling
developerConfigure automatic retries with backoff for failed steps or activities
weight 3 · round to MakeZapiernone0/10No evidence in the pack mentions retry policies, backoff configuration, or error-handling settings for failed Zap steps or actions; the only related item is generic AI-generated troubleshooting instructions, which is not the same as configurable retry/backoff.
- [claimed-docs] “Zapier will use AI to create troubleshooting instructions for you to review.”
Make's docs repeatedly reference a dedicated 'error handling' system with 'error handlers' for diagnosing and resolving scenario failures, implying some built-in mechanism for handling failed steps, but none of the evidence explicitly mentions configurable retry counts or backoff intervals. missing for 10: explicit documentation of a retry directive with configurable attempts/backoff, and any hands-on confirmation of this behavior.
- [claimed-docs] “this page helps users navigate errors, diagnose and resolve issues in by providing detailed information on common errors and warnings, error…”
- [claimed-docs] “diagnose and resolve issues in by providing detailed information on common errors and warnings, error handlers”
- [claimed-docs] “detailed information on common errors and warnings, error handlers, and how to use them”
- [claimed-docs] “detailed information on common errors and warnings, error handlers, and how to use them in your”
ops userDefine dedicated error-handling paths or error workflows and get notified when a run fails
weight 2 · round to MakeThere is a documented troubleshooting help article (AI-generated troubleshooting instructions) for Zap errors, but no evidence of dedicated error-handling paths/branches or configurable failure notifications within a Zap workflow. missing for 10: documentation of built-in error-path branching, retry/fallback steps, and explicit failure-notification configuration (e.g., email/Slack alert on Zap failure) beyond generic troubleshooting help.
- [claimed-docs] “Zapier will use AI to create troubleshooting instructions for you to review.”
Make's help docs confirm a dedicated error-handling system with 'error handlers' for diagnosing and resolving failed runs, which is the core mechanism ops users would use to define error-handling paths. However, the evidence never explicitly describes configurable failure notifications (e.g., email/Slack alerts on scenario failure) or how error routes are wired into scenarios beyond generic mentions. Missing for 10: explicit notification-on-failure documentation, concrete error-handler route configuration details, and independent/hands-on confirmation.
- [claimed-docs] “this page helps users navigate errors, diagnose and resolve issues in by providing detailed information on common errors and warnings, error…”
- [claimed-docs] “diagnose and resolve issues in by providing detailed information on common errors and warnings, error handlers”
- [claimed-docs] “detailed information on common errors and warnings, error handlers, and how to use them”
- [claimed-docs] “detailed information on common errors and warnings, error handlers, and how to use them in your”
Observability
ops userInspect past execution logs and re-run a failed execution, resuming from the failing step
weight 2 · round to MakeZapiernone0/10The evidence pack only mentions AI-generated troubleshooting instructions for Zap errors, with no documentation of inspecting execution logs or re-running/resuming a failed multi-step Zap from the point of failure.
- [claimed-docs] “Zapier will use AI to create troubleshooting instructions for you to review.”
Make's docs confirm scenario execution history for inspecting past runs and dedicated error-handling documentation, which supports viewing logs and diagnosing failures, but none of the evidence describes a feature to re-run a failed execution and resume specifically from the failing step. Missing for 10: explicit documentation of a 'rerun/resume from failed step' capability, and any hands-on confirmation that partial re-execution (vs. full restart) is supported.
- [claimed-docs] “scenario history”
- [claimed-docs] “this page helps users navigate errors, diagnose and resolve issues in by providing detailed information on common errors and warnings, error…”
- [claimed-docs] “diagnose and resolve issues in by providing detailed information on common errors and warnings, error handlers”
- [claimed-docs] “detailed information on common errors and warnings, error handlers, and how to use them”
- [claimed-docs] “detailed information on common errors and warnings, error handlers, and how to use them in your”
Triggers scheduling — stories about triggers scheduling in this arenaTriggers scheduling
Stories about triggers scheduling in this arena
Schedules
ops userRun workflows on cron-style schedules with timezone control
weight 2 · round to MakeZapiernone0/10No evidence in the pack addresses Zapier's Schedule trigger, cron-style scheduling, or timezone configuration for workflows; all citations focus on integrations, MCP, CLI, and general automation marketing rather than scheduling controls.
Evidence confirms Make has a scenario scheduling feature ("schedule a scenario") and periodic webhook queue processing, but no documentation snippet describes cron-style expressions or explicit timezone configuration options. missing for 10: cron/interval expression syntax details, explicit timezone selection UI/API evidence, independent confirmation of scheduling behavior.
- [claimed-docs] “schedule a scenario docid 8rwfo krohjlepg4qhx3 clone a scenario docid\ c8f35kwpicyg1az5vlgehdelete a scenario”
- [claimed-docs] “If you don't want to run your immediately after a webhook receives data, you can schedule your to process all webhook requests periodically”
- [claimed-docs] “you can schedule your to process all webhook requests periodically”
- [claimed-docs] “the whole queue is then processed every time your schedule criteria are met”
Triggers
ops userTrigger workflows from events in connected apps (new record, message, email, form submission)
weight 3 · round to ZapierZapier's core product is trigger-based workflow automation across 9,000+ connected apps (new record, message, email, form submission triggers), documented extensively via Visual Builder, CLI, and platform docs, and corroborated by community users describing real-world use for webhook/event-based automations. missing for 10: independent hands-on benchmarking of specific trigger types (e.g., form submission) beyond general community anecdotes.
- [claimed-docs] “Use the Visual Builder for quick, no-code setups or the CLI for full control and customization.”
- [claimed-docs] “the Visual Builder is the place to start. It’s ideal for quick deployment and collaboration across teams, even without developer expertise.”
- [claimed-docs] “Simplify and scale your processes with visual mapping—add owners, notes, and images to create structured, easy-to-follow systems.”
- [community] “I am using Zapier because their service was very easy to implement a webhook for what I needed... However, the price is high enough that the…”
- [community] “The options were: bump a dev to build the integration, pay ~$50/month to enable a non-technical person to build it via Zapier, or don't get …”
- [community] “Zapier is a killer app for non technical marketers... It's a killer app for technical people that have better things to do than build custom…”
- [community] “Zapier has about 1,000 integrations, more than any of their closest competitors and at a price that is far less than others in their space.”
Make's docs describe webhooks that let external apps or events trigger scenario execution (make-docs-5,15,25) plus scheduling to batch-process trigger events (make-docs-6,16,21), which is the mechanism ops users use to fire workflows off new records, messages, forms, etc. from connected apps/modules (make-docs-10 lists Modules/Webhooks as core app components). Missing for 10: explicit named examples of app-specific instant triggers (e.g., new Gmail email, new Typeform submission) and independent/hands-on confirmation beyond vendor docs.
- [claimed-docs] “custom webhooks allow you to create a url to which you can send any data”
- [claimed-docs] “webhooks create a url that you can call from an external app or service, or from another use webhooks to trigger the execution”
- [claimed-docs] “webhooks create a url that you can call from an external app or service, or from another use webhooks to trigger the execution of”
- [claimed-docs] “If you don't want to run your immediately after a webhook receives data, you can schedule your to process all webhook requests periodically”
- [claimed-docs] “you can schedule your to process all webhook requests periodically”
- [claimed-docs] “the whole queue is then processed every time your schedule criteria are met”
- [claimed-docs] “App components * [Base] * [Connections] * [Webhooks] * [Modules] * [Remote Procedure Calls]”
developerExpose a custom webhook URL that receives external HTTP requests and starts a workflow run with the payload
weight 3 · round drawnZapier natively supports the 'Webhooks by Zapier' trigger (documented as part of Platform CLI's webhook trigger support in zapier-docs-3, and the built-in Visual Builder path in zapier-docs-19/22) allowing a custom URL to receive HTTP POSTs and start a Zap run with the payload — this is a long-standing, widely used core Zapier capability. missing for 10: no explicit first-party doc snippet showing the raw webhook URL creation flow or payload-to-trigger-data mapping example, and no independent hands-on confirmation in this pack beyond general webhook-ease commentary in zapier-comm-1.
- [claimed-docs] “Zapier Platform CLI enables developers to build integrations using Node.js v22, OAuth1/OAuth2 authentication, webhooks, polling triggers, an…”
- [claimed-docs] “Use the Visual Builder for quick, no-code setups or the CLI for full control and customization.”
- [claimed-docs] “the Visual Builder is the place to start. It’s ideal for quick deployment and collaboration across teams, even without developer expertise.”
- [community] “I am using Zapier because their service was very easy to implement a webhook for what I needed... However, the price is high enough that the…”
Make's custom webhooks feature lets developers create a URL that receives external HTTP requests and triggers scenario (workflow) execution with the received payload, with options for immediate or scheduled/batched processing of the queue. missing for 10: independent/hands-on corroboration beyond first-party docs, and no detail on payload parsing/validation specifics.
- [claimed-docs] “custom webhooks allow you to create a url to which you can send any data”
- [claimed-docs] “If you don't want to run your immediately after a webhook receives data, you can schedule your to process all webhook requests periodically”
- [claimed-docs] “webhooks create a url that you can call from an external app or service, or from another use webhooks to trigger the execution”
- [claimed-docs] “the whole queue is then processed every time your schedule criteria are met”
- [claimed-docs] “webhooks create a url that you can call from an external app or service, or from another use webhooks to trigger the execution of”
Visual builder — stories about visual builder in this arenaVisual builder
Stories about visual builder in this arena
Builder
ops userBranch a workflow with conditions, filters, and parallel paths that merge back together
weight 2 · round to ZapierCommunity evidence indicates Zapier supports more than one simultaneous IF/THEN condition compared to IFTTT (zapier-comm-8), implying some conditional/branching capability, but no documentation in the pack describes explicit 'Paths', filters, or parallel-path merge-back features, and users explicitly flag 'the need for escape hatches/conditional logic when needed' and frustration at lacking simple 'if' logic (zapier-comm-11, zapier-comm-13) as ongoing gaps. Missing for 10: first-party docs on Paths/filter steps, evidence of parallel branch execution, and confirmation that branches can merge back into a single continuing workflow.
- [community] “For me it was that IFTTT allows only one IF condition and one THEN step, whereas Zapier allows more simultaneous IFs & THENs. IFTTT is free …”
- [community] “As an engineer using Zapier (for the first time) these past few months I got so frustrated by the lack of an option to just write some 'if' …”
- [community] “Resonate a lot with the gaps with Zapier, particularly around the need for escape hatches/conditional logic when needed.”
- [claimed-docs] “Use the Visual Builder for quick, no-code setups or the CLI for full control and customization.”
- [claimed-docs] “the Visual Builder is the place to start. It’s ideal for quick deployment and collaboration across teams, even without developer expertise.”
Makenone0/10The evidence pack contains no mention of routers, filters, conditional branching, or parallel path merging in Make scenarios — it only covers API auth, MCP server, webhooks, error handling, and scenario management pages. Missing for 10: any documentation of router/filter modules, branch conditions, or parallel-path merge behavior.
ops userBuild multi-step workflows in a visual editor without writing code
weight 3 · round to ZapierZapier's Visual Builder is documented as a no-code interface for building multi-step Zap workflows, explicitly positioned for non-developers ('quick deployment and collaboration across teams, even without developer expertise'), and community evidence corroborates non-technical/ops users successfully building workflows themselves. Missing for 10: independent hands-on review specifically walking through multi-step visual editing (community evidence focuses more on general ease-of-use and pricing than a detailed multi-step build).
- [claimed-docs] “Use the Visual Builder for quick, no-code setups or the CLI for full control and customization.”
- [claimed-docs] “the Visual Builder is the place to start. It’s ideal for quick deployment and collaboration across teams, even without developer expertise.”
- [community] “The options were: bump a dev to build the integration, pay ~$50/month to enable a non-technical person to build it via Zapier, or don't get …”
- [community] “Zapier is a killer app for non technical marketers... It's a killer app for technical people that have better things to do than build custom…”
Evidence confirms Make's core building blocks—scenarios, modules, connections, webhooks, functions, and error handlers—implying a scenario-based workflow model, but nothing in the pack explicitly describes a visual drag-and-drop editor or no-code experience. Missing for 10: explicit description of the visual canvas/editor UI, no-code claims, and evidence of building multi-step workflows without code.
- [claimed-docs] “clone a scenario”
- [claimed-docs] “scenario history”
- [claimed-docs] “schedule a scenario docid 8rwfo krohjlepg4qhx3 clone a scenario docid\ c8f35kwpicyg1az5vlgehdelete a scenario”
- [claimed-docs] “transform and format data using our range of functions”
- [claimed-docs] “this page helps users navigate errors, diagnose and resolve issues in by providing detailed information on common errors and warnings, error…”
- [claimed-docs] “webhooks create a url that you can call from an external app or service, or from another use webhooks to trigger the execution”
Composition
developerCompose reusable sub-workflows or modules that other workflows call
weight 2 · round to MakeZapiernone0/10No evidence in the pack describes reusable sub-workflows, modules, or the ability for one Zap/workflow to call another as a nested unit; Canvas and Workflow API references cover visual mapping and API access, not composable sub-workflows. missing for 10: documentation of a 'Sub-Zap'/nested-workflow or reusable module feature, evidence of one workflow invoking another as a callable unit, and any hands-on confirmation of this pattern.
Evidence shows webhooks can be used to trigger one scenario's execution from another scenario or external app (make-docs-15, make-docs-25), which offers a rudimentary way to compose workflows, and custom apps can define reusable 'Modules' and 'Remote Procedure Calls' (make-docs-10). However there is no explicit documentation of a native 'call another scenario/sub-workflow' module or reusable workflow-as-module composition pattern within the visual builder itself. Missing for 10: dedicated sub-scenario/sub-workflow invocation feature, parameter passing between parent/child scenarios, and independent/hands-on confirmation of this composability pattern.
- [claimed-docs] “webhooks create a url that you can call from an external app or service, or from another use webhooks to trigger the execution”
- [claimed-docs] “webhooks create a url that you can call from an external app or service, or from another use webhooks to trigger the execution of”
- [claimed-docs] “App components * [Base] * [Connections] * [Webhooks] * [Modules] * [Remote Procedure Calls]”
- [claimed-docs] “custom webhooks allow you to create a url to which you can send any data”
Testing
developerTest a workflow with sample or pinned data and inspect each step's input and output before going live
weight 2 · round drawnZapiernone0/10No evidence pack items describe testing a Zap with sample/pinned data or inspecting per-step input/output before publishing; docs cover integration building, MCP, embedding, and Canvas but not the test/debug workflow in the visual builder. missing for 10: mention of 'test step' or 'pinned sample data' feature, evidence of step-by-step input/output inspection during Zap creation, any documentation of the testing UI.
Makenone0/10The evidence pack covers Make's API, MCP server, webhooks, and error-handling docs, but contains no documentation of running a scenario with sample/pinned data or inspecting per-step input/output before publishing. 'Scenario history' and 'error-handling' entries are the closest topics but don't describe a test-run/inspect-bundle workflow. missing for 10: docs on 'Run once' test execution, pinned/sample data configuration, per-module input/output bundle inspection.
- [claimed-docs] “scenario history”
- [claimed-docs] “this page helps users navigate errors, diagnose and resolve issues in by providing detailed information on common errors and warnings, error…”
- [claimed-docs] “diagnose and resolve issues in by providing detailed information on common errors and warnings, error handlers”