What leaders and teams rolling out Zapier report, with every finding tied to its evidence.
Read the findingsPractitioner sentiment, leaders and teams
−4 Mixed from 24 sources that take a side
How this figure is madeFrom 24 authors in 23 discussions. Small sample. Run a pilot on one live workflow to measure failed runs and the time spent fixing them.
Jan 2025 to Oct 2026.
51 sources from practitioners, by month and sentiment.
Team accounts split 8 for Zapier to 9 against. Departments and executives credit Zapier's app reach and its AI agents; at SaaStr one form fill starts six agents in parallel. Task cost is the only concern with enough sources among team accounts. It comes from a six-year customer whose Tables allowance shrank, a 50-person SaaS company paying about US$400 a month, and two company heads who moved work to their own code.
Positive, mixed and negative sources
The score counts each source once, as the split does. See How the numbers work.
See the evidenceBelow: 2 praise themes, 1 concern and 1 disagreement.
Counted for Leaders and teams rolling it out, from 28 sources. Change group
Every capability practitioners describe positively, ranked by how many sources say so. Open one to read who said it.
Counted for Leaders and teams rolling it out.
Positive
Digital Developer
Zapier as the most complete integration and automation system that connects to most app.G2 review (incentivized)
Builds with Zapier Canvas by prompting and connects the company's CRM, spreadsheets, Xero, and PandaDoc, but finds task limits restrictive against cheaper rivals.
Positive
Luke Harries, Head of Growth at ElevenLabs (as ElevenLabs' author page names him)
3 AI Workflows to Save $140K & Automate Marketing with ElevenLabs' Luke HarriesPodcast interview and episode notes, How I AI
Harries connects Salesforce and Zapier to invite eligible ElevenLabs customers to share their stories. The automation supplies interviews for the team's customer-marketing workflow, where AI drafts still receive editorial and customer approval.
"Luke also connected Salesforce and Zapier so eligible customers could receive an invitation to share their story."
Positive
Team Lead in Information Technology
Zapier ZAPsTrustRadius review (incentivized)
Zapier runs onboarding across 15 tools and 4 teams and an order workflow across 5, cutting manual entry, though loops and branches lengthen the workflows.
Positive
Employee in Product Management
Robust Automation SolutionTrustRadius review (incentivized)
A software company centralizes customer data from many apps with Zapier, chose it over Power Automate for app reach, and wants easier re-testing of single steps.
Positive
Amelia Lerutte, Chief AI Officer, SaaStr (GTM AI Podcast guest)
The Secret Sauce of SaaStr and How they Built a $5 million Pipeline Machine with 20 AI AgentsPodcast episode recap, GTM AI Podcast
At SaaStr, one Zapier flow fires on each form fill, pushes the contact to Salesforce and Google Sheets, and hands it to six agents in parallel. Zapier actions grew from a couple hundred a day to over 1,000.
Positive
Andrew Wilkinson, co-founder of Tiny
Claude + Zapier MCP just became the world's most diligent employeeX post
Wilkinson calls Claude with Zapier MCP the world's most diligent employee. He asks it to catch up on email and write a report on last month's P&L through any app that has a Zapier API, such as Xero or HubSpot.
"Works with any app that has a Zapier API (Gmail, Xero, Hubspot, etc)."
Counted for Leaders and teams rolling it out.
Positive
Amelia Lerutte, Chief AI Officer, SaaStr (GTM AI Podcast guest)
The Secret Sauce of SaaStr and How they Built a $5 million Pipeline Machine with 20 AI AgentsPodcast episode recap, GTM AI Podcast
At SaaStr, one Zapier flow fires on each form fill, pushes the contact to Salesforce and Google Sheets, and hands it to six agents in parallel. Zapier actions grew from a couple hundred a day to over 1,000.
Positive
Matt Britton, founder and CEO of Suzy (How I AI guest)
How this CEO turned 25,000 hours of sales calls into a self-learning go-to-market enginePodcast episode show notes, How I AI (Lenny's Newsletter)
Britton, who does not code, built a Zapier workflow that turns each customer call transcript into a summary, sentiment analysis, coaching feedback, a follow-up email, and a blog draft. The episode calls Zapier the backbone of his AI automations.
Positive
Office manager
The best no-code AI powered automation platform to streamline workflows and boost productivityG2 review (incentivized)
An office manager answers quote requests through Zapier Copilot-built workflows connected to the team's Google apps and Stripe, and finds the cost worth the hours saved.
Positive
Andrew Wilkinson, co-founder of Tiny
Claude + Zapier MCP just became the world's most diligent employeeX post
Wilkinson calls Claude with Zapier MCP the world's most diligent employee. He asks it to catch up on email and write a report on last month's P&L through any app that has a Zapier API, such as Xero or HubSpot.
"Works with any app that has a Zapier API (Gmail, Xero, Hubspot, etc)."
Positive
Digital Developer
Zapier as the most complete integration and automation system that connects to most app.G2 review (incentivized)
Builds with Zapier Canvas by prompting and connects the company's CRM, spreadsheets, Xero, and PandaDoc, but finds task limits restrictive against cheaper rivals.
Every concern practitioners raise, most raised first.
Counted for Leaders and teams rolling it out.
Raised as a concern, 6
Negative
Tim, founder building RevenueFlow, an AI-native outbound agency (X profile)
What replaced Cursor, OpenRouter and ZapierX post
Paid US$178.50 a month for one Zap that posted Stripe payments to Slack. Claude Code rewrote it into the company's own webhook code in a single commit, and the Zapier bill went to zero.
Negative
Noah Kagan, founder and CEO of AppSumo
Another one bites the dust in our War on Expensive SoftwareX post
After 10 years on Zapier, AppSumo found that 63 of the automations it paid for had not run in a month and 2 did 88% of the work. Claude rebuilt one, the rest moved into tools the company already paid for, and the US$4,788 yearly bill went to zero.
"We paid for 123 automations. 63 hadn’t run in a month. 2 did 88% of the work."
Negative
Zapier Community member
Tables and the new pricing planCommunity forum post
A six-year customer on a 100,000-task Pro plan says the new pricing cut Tables records from 1,000,000 to 100,000 per account, pushing the business toward Team.
Negative
Alex Kruger, CEO, Scale Army (X profile)
We replaced what we were using Zapier for in a weekX post
After an ops leader kept getting stuck making Zapier do what the team needed, Kruger's AI team built an in-house tool in a week. It checks leads from 10 providers across company databases, saving thousands of dollars a month.
Negative
RevOps lead
Tired of Zapier breaking at 2am. What does everyone actually trust for production?Reddit post
After three years and a bill near US$400 a month, a RevOps lead lost 6 form leads over a weekend to a silent failure. The lead plans to move the workflows where failures cost money.
Positive
Digital Developer
Zapier as the most complete integration and automation system that connects to most app.G2 review (incentivized)
Builds with Zapier Canvas by prompting and connects the company's CRM, spreadsheets, Xero, and PandaDoc, but finds task limits restrictive against cheaper rivals.
Discussed without concern, 2
Positive
Office manager
The best no-code AI powered automation platform to streamline workflows and boost productivityG2 review (incentivized)
An office manager answers quote requests through Zapier Copilot-built workflows connected to the team's Google apps and Stripe, and finds the cost worth the hours saved.
Negative
Security researcher at Repello AI
Exploiting Zapier's Gmail auto-reply agent for data exfiltrationSecurity research write-up, Repello AI blog
A crafted email made a Zapier Gmail auto-reply agent forward earlier emails to an attacker, with no approval step, and the agent ran past its activity limit, reaching 451 of 400.
GILD's fact checks, which don't count as sources
Checked Oct 12, 2026.Only successful actions use tasks: triggers, filters, paths, Formatter, and failed steps use none. Each successful Zapier MCP tool call uses 2 tasks, and AI steps use 1, 3, or 5 tasks per run and per tool call by model tier. Task usage rates
Open them in the recordStatements this group's sources agree on, then the ones close to agreement.
For leaders and teams rolling it out, no statement reaches 5 sources from 3 authors.
Questions the sources split on, with the count on each side.
Evidence remains mixed
Stay on Zapier, 2 sources
Some keep Zapier or return to it for app coverage and to avoid maintaining code or servers.
Move workflows off, 6 sources
Others move workflows to n8n, Make, GitHub Actions, or code for lower cost at volume and more control over logic.
The three groups, then every practitioner by the context they work in, and how emphasis changes with scale.
Three groups drawn from the same sources. Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. Signals open on Leaders and teams rolling it out.
28 sources. These reports from small teams, departments, and business leaders weigh team-volume cost, ownership of shared Zaps, and AI steps.
23 sources. These accounts weigh setup speed against the cost and logic limits that individual users hit as automations grow.
51 sources. This broad read combines one-person automations with team accounts that reach different conclusions.
51 sources from practitioners, by the context they work in. Filled rows count for this group.
Emphasizes A fast builder weighed against task cost and moves to n8n or code
Emphasizes Zapier connecting a few apps, and Zaps nobody documented
Emphasizes App coverage, Zapier MCP for accounts payable, and error logging
Emphasizes Leaders running AI agents through Zapier, and leaders replacing it with their own code
What changes with scale. Individual users praise fast Zap creation and complain about cost and logic limits. Small teams connect a few apps and inherit undocumented Zaps. Department accounts lean positive on app coverage and AI agents. Business leaders split. SaaStr and Suzy run their AI agents through Zapier, while two company heads moved work to their own code. A RevOps lead plans to move the workflows where a silent failure costs money.
Where this group's sources were published.
Counted for Leaders and teams rolling it out, from 28 sources. Change group
45 sources for this group, 17 of them documentation
Older evidence stays when it still applies. Records that depend on changed features stay in the history, marked Needs a recheck.
See sources by originWho each source is, how it knows, whether it still applies and what it counts toward.
Newest first, on its own page. Every count above opens its sources there.
Read all 68 sourcesAbout this read
A running review of what people using Zapier at work report, from individual users to IT and business leaders. Each finding links to its sources, and each conflict shows both sides.
Counts cover only the sources GILD reviewed.
Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. GILD files each source in a group from how the account describes its author. A role or employer marked self-described is what the source states about themselves. Documentation checks facts for every group and never counts toward sentiment.
A source's date and whether it still applies are separate: a recent post can describe an old version, and an old one can still hold.
Flagged for a recheck, of the sources that take a side: leaders and teams 1 of 24, individual users 2 of 23, all users 3 of 47.
Each row opens its sources for the group you are reading.
| Finding | Leaders and teams rolling it out | Individual users | All users | Sources |
|---|---|---|---|---|
| Current readCurrent sentiment | 9 positive, 5 mixed, 10 negative | 5 positive, 10 mixed, 8 negative | 14 positive, 15 mixed, 18 negative | Sources |
| PraiseApp coverage | 6 of 6 positive | 3 of 4 positive (under the minimum) | 9 of 10 positive | Sources |
| PraiseEase of use | 2 of 4 positive (under the minimum) | 6 of 6 positive | 8 of 10 positive | Sources |
| PraiseAI steps, agents & MCP | 5 of 5 positive | 4 of 8 positive | 9 of 13 positive | Sources |
| ConcernTask cost | 6 of 8 raise it | 6 of 7 raise it | 12 of 15 raise it | Sources |
| ConcernComplex logic | 4 of 4 raise it (under the minimum) | 4 of 5 raise it | 8 of 9 raise it | Sources |
| ConcernRun failures | 2 of 4 raise it (under the minimum) | 1 of 3 raise it (under the minimum) | 3 of 7 raise it | Sources |
| ConcernGovernance & data | 4 of 4 raise it (under the minimum) | 0 of 2 raise it (under the minimum) | 4 of 6 raise it | Sources |
| ConsensusHeavy workflows move off | 3 supporting (under the minimum) | 4 supporting (under the minimum) | 7 supporting (below threshold) | Sources |
| DisagreementShould a team keep its automations on Zapier or move them to n8n, Make, or code? | Stay on Zapier 2, Move workflows off 6 | Stay on Zapier 1, Move workflows off 8 (under the minimum) | Stay on Zapier 3, Move workflows off 14 | Sources |
| Current readEvidence mix | 45 sources | 40 sources | 68 sources | Sources |
GILD's checks of claims against official documentation, kept apart from the source counts.
