Item: Zapier
Author: GILD

GILD verdict

Start with Zapier when business teams need to connect many SaaS apps without engineering help.

Before more teams build on it, set the task budget, name an owner for each shared Zap, and check which admin controls require Enterprise.

Zapier

Workflow Automation by Zapier

−4 Mixed

Fit and limits

Who it fits

Business and operations teams need hand-offs between SaaS apps, and engineers are not available to build each integration.
Your stack includes niche apps: Zapier lists 9,000+ app integrations, and Webhooks by Zapier on paid plans reaches APIs it does not list.
Most steps move data between apps: triggers, Filters, Paths, Formatter, and failed steps use no tasks, so a five-step Zap can bill two tasks per run.
You want AI assistants such as Claude, ChatGPT, or Cursor to act in your apps through Zapier MCP, with Zapier holding the app credentials.

Where it falls short

Zapier runs only in its own cloud, on AWS in the United States; there is no self-hosted or EU-hosted option.
Costs rise with volume and AI. Premium AI steps, the default on paid plans, use 5 tasks per run plus 5 per tool call.
App access controls, managed connections, SCIM, workspaces, and custom data retention are Enterprise only; Team offers SAML SSO, shared connections, and a 6-month audit log.
Zapier is moving Agents into AI by Zapier, which lacks the HubSpot, Asana, Zendesk, Zoom, and Jira knowledge sources until their planned Q4 2026 release.

Size the task tier on annual billing
Count the successful actions in each Zap, since triggers and built-in steps use no tasks. Professional starts at US$19.99 a month billed annually for 750 tasks. Monthly billing costs about 1.5x the annual rate. Self-serve tiers reach 2 million tasks a month. Enterprise uses an annual task limit.
Decide on pay-per-task
Set pay-per-task before rollout. It defaults to on for accounts created after January 2024, and Zaps pause only at 3x the plan's tasks. Overage costs 1.25x the base rate on annual plans and 2.5x on monthly plans. Only the owner can turn it off on Professional and Team. Zapier MCP sets no cap on tool calls per session, so the task allowance is its only limit.
Assign owners and connections
On Team, use shared app connections and assign an owner to each shared folder. Owner access includes private Zaps. Enterprise managed connections and managed apps keep credentials with the company after employees leave.
Set AI defaults before teams use them
Select the AI tier for each step. New paid-plan steps default to Premium at 5 tasks per run and per tool call. Use Standard or Advanced where they meet the need. A run pauses for review at 75 tasks by default, and the limit goes up to 500. Full-Zap tests use tasks like production runs. Turn on per-tool approvals, which default to off.

GILD found no activity-to-task rate in Zapier's Agents guides. Run each migrated agent for a week, read its tasks per run in Zap history, and move pause-limit runs to a cheaper tier.
GILD found no published share of task bills from MCP calls. Log the MCP Tasks and Plan Tasks counters weekly for a month, and give assistants their own budget if MCP passes a quarter.
Next Gen Zaps are in early access by request on every plan; if you join, count how many non-engineers ship one from an MCP client in the first month.