Zapier Reviews & Product Details

Zapier has been great for my internal testing and personal productivity use. The UI is super simple and non-technical, I could connect Slack, Gmail and Drive in minutes without any code to get alerts for test results and bug reports. It integrates with almost everything we use, performance is reliable with instant triggers, and the free tier is enough for my QA needs so ROI is excellent. Onboarding was very easy with ready-made templates, support is helpful, and its AI features for suggesting next steps and formatting data save a lot of manual work. Review collected by and hosted on G2.com.

What I dislike about Zapier is that the pricing can get expensive quickly if you have a lot of tasks or need multi-step Zaps. For free plan, there's also a delay in trigger time - my Slack alerts sometimes come after 10-15 mins instead of instantly, and some advanced features like custom logic are limited to higher plans. Review collected by and hosted on G2.com.

Zapier's copilot is a nice touch; it makes setting up workflows easier and less likely to fail. Zapier has embraced the AI era and has made additions and adjustments to the platform. There is quite a bit that can be done with AI, including integrating AI tools with other apps. Zapier has changed from being an integration and automation tool to being an AI platform, "the world’s most connected AI platform." The YT channel is still up and current, with a lot of content about AI and what is happening in the world today. Review collected by and hosted on G2.com.

I first discovered Zapier years ago, before AI became a part of everyday life and an integral part of computing infrastructure. At that time Zapier was innovative and enabled integration and automation that was difficult to do without advanced programming skills. But at present there are mainstream AI tools that can do what Zapier does that are easier to use. The rapid change in the technology landscape has also pushed me to improve my skills. I am now able to interact with APIs directly, such that I do not need Zapier as much. Review collected by and hosted on G2.com.

I am still incredibly happy with Zapier, and they have certainly improved the integrations. Zapier Copilot is what we use most. No more sifting through emails manually and answering tedious quote requests; everything gets done for you. You just set the rules, the do's and don'ts. It connects seamlessly to all the apps our team uses: Gmail, Drive, Google Calendar, Sheets, Forms, Docs, and Stripe, and best of all, Zapier connects to ChatGPT and thousands of more apps. Review collected by and hosted on G2.com.

I still have a bit of an issue with the cost, but it can actually be worth it when you realise the hours you gain from all the automated workflows. Once you have the hang of it, it's pretty impressive. Review collected by and hosted on G2.com.

One thing new I have started liking about Zapier is its AI features like Copilot and Zapier Agents. Copilot lets you just describe what you want in plain language, and it builds the automation for you. Zapier Agents go a step further and can handle multi-step tasks on their own without me setting up every single step manually. This has made building and managing automations much faster and easier than before. Review collected by and hosted on G2.com.

One thing I feel Zapier can improve is handling more complex logic, like loops or advanced branching, which sometimes needs workarounds or extra steps to set up. Apart from that, it works well for my day-to-day use and I haven't faced any major issues. Review collected by and hosted on G2.com.

Zapier remains a key tool for connecting different platforms and automating processes without relying on complex developments. I increasingly value the ease of building flows between CRM, forms, email, databases, and other tools we use in operations. I also find Zapier's evolution towards artificial intelligence and the possibility of incorporating more advanced agents and automations within business processes very interesting. Review collected by and hosted on G2.com.

My main opportunity for improvement remains the price, especially for companies in Latin America. When processes begin to scale, task consumption increases rapidly, and the cost can become a limitation for automating more areas of the company. It would be very valuable to have more competitive pricing plans or schemes for emerging markets and for users who handle a high volume of automations. Review collected by and hosted on G2.com.

Zapier has been a hero for many automations that I had to build to remove toil in software development teams. It has served me well over time with things like syncing project management tools with code repositories, sending reminders to Slack with informed data from databases and email, sending notifications when updates happen in third-party providers, and, more recently, building agents to optimize daily operations in different areas of the business. What I like best is the thousands of integrations they have; even if a platform is very niche, you can integrate it with generic nodes like an HTTP request. On the other hand, something I love is the user experience: really easy to use without a lot of knowledge, even in the first interaction with the platform, easy to get started; being able to execute step by step, debug the data, and have real data in each step to emulate and play with to get the result you are looking for is something that I find really valuable.

Finally, my next step is to start using the MCP. I heard many good comments, but it's something I haven't used yet, but it will be in the next couple of weeks Review collected by and hosted on G2.com.

The operators to modify data or flows are not very obvious. For example, to map data in a certain format, there are nodes that help you do it pretty easily, but you can't find them by name. I usually implement scripts with JS or Python code to fix my data, but later I notice that it is much simpler to do it with a simple node that already does it for me. Also, when I tried to get support, it was really hard to explain the issue due to the nature of the problem, and I had to iterate on it a lot to explain myself. This is not a platform problem, is more like a user experience issue where the tools are already available but are not obvious to you Review collected by and hosted on G2.com.

What I like most about Zapier is how it saves me from doing the same tasks repeatedly. For example, I can set up a workflow where a new file uploaded to Google Drive automatically triggers a notification in Slack or an email alert through Gmail. This means I don’t have to keep checking for updates manually. I also find the app integrations and ready-made templates useful because they make automation accessible even without coding knowledge. Some advanced workflows take a little time to figure out, but once everything is running smoothly, Zapier makes managing everyday tasks much easier and more organized. Review collected by and hosted on G2.com.

My biggest frustration with Zapier is that the costs can increase quickly as I add more steps to a workflow or automate more tasks. For example, a simple automation might seem affordable at first, but connecting several apps and adding extra actions can make it more expensive than expected. I also find advanced workflows a bit tricky when I need multiple conditions or custom logic, as figuring out the right setup can take time. Another annoyance is that triggers on the free plan may be delayed, so a Slack notification doesn't always arrive when I expect it. I'd also appreciate clearer information about task usage, so I can avoid unexpected charges as my automations grow. Review collected by and hosted on G2.com.

What I love most about Zapier is how easy it makes it to create automations. I also really like its databases, and I’ve tried the MCP as well—it’s been incredible. I’ve experimented with other automation platforms, but Zapier is always the one I come back to because it feels so simple and intuitive to use. Overall, it’s genuinely amazing. Review collected by and hosted on G2.com.

The one thing I’m not a huge fan of is the pricing model, especially how usage is calculated based on each step. With our current plan, we don’t usually use up all of our monthly usage, but knowing that every additional step counts sometimes makes us hesitate before creating a new flow. I’d personally prefer a pricing model that gives us a bit more freedom to experiment and build automations without having to think as much about usage. Review collected by and hosted on G2.com.

The idea of automation, not Zapier's billing or support when it went wrong. Any company can be good when there's no issue. Review collected by and hosted on G2.com.

Being in sales and not a tech, I set up an automation, my first 2 months well under my allowance. Was then hit with a $438 overage bill on a plan that costs me about $100 a month. More than 400% of my monthly plan. Scenario — My Zaps used 1,309 tasks for the month. Would never have breached my 2,000-task limit on their own. The rest came from new AI helper in Muse, from programmatic / MCP calls made by my AI assistant while checking and cleaning up my CRM. Given this is all new, I had no knowledge these AI checks were going through Zapier, let alone consuming paid tasks. Was an honest mistake. No intent to benefit, no intent to game the system. Just an error from someone who doesn't do tech. Zapier did not care about intent. Their reasoning was error only: usage occurred, therefore you pay. They then pointed to a 1 off exception from a few months earlier for a completely different looping issue and used that to refuse any goodwill on this. A completely different cause. 1. No accountability? 3 times asked to speak to a manager — a named person, with their position in the company stated, so someone is actually accountable. What I got back was "the team responsible has reviewed it" and "the decision is final". That is the whole thesis: hide behind a "team" so no one in the organisation is accountable. Since then, Arthur Sargeant, Global Support Manager, has replied & confirmed full amount payable Zapier’s company policy. 2. No personal communication. It's email only, every reply reads like AI, Global Support manager included— templated, unemotive and no empathy. I'm sure any reply to this review will read the same way. 3. Their plans. The plan looks simple until an error happens. Then, in my experience, they wait for that error to occur and the only solution offered is to pay the overage and upgrade. 4. Beware. If you are not a tech expert, do not trust that the plan limit means what you think it means. Review collected by and hosted on G2.com.

What I like best about Zapier is that it lets me link up all our disjointed SaaS tools without needing an in-house IT team or a developer to write custom code. I’m the Business Development & Operations Manager at Veridian BioLabs, a small biotech firm out in Houston working on preclinical research and new biomolecules. We’re lean, no dedicated IT staff, and I’m constantly testing different platforms, juggling lab project coordination, vendor follow-ups, and BD outreach. Before Zapier, every handoff between our tools meant manual copying, pasting, and a ton of extra admin work that pulled me away from higher-priority stuff.

The no-code setup is such a lifesaver for us. We work with sensitive research and client data, so I need automations I can build, tweak, and audit myself. A few weeks back, we set up a zap tied to our CRM. Whenever a new biotech lead fills out our contact form requesting a preclinical study Review collected by and hosted on G2.com.

For starters, error alerts are really basic, and they don’t give me the detailed audit context I absolutely need for our biotech workflows. When a zap fails, the notification is super vague — it just says something didn’t run successfully. It doesn’t break down whether it’s a permissions issue, a field format that got rejected, or a compliance restriction from one of our research and document tools. A couple weeks back, I built a zap meant to automatically log new vendor paperwork and submissions straight into our secure document repository. It failed overnight, and I didn’t spot the alert until mid-morning the next day. When I hopped into the logs to investigate, the records were sparse. I couldn’t quickly tell if it was just a random one-time glitch, or if there was an underlying problem that would keep dropping vendor documents moving forward. That’s really stressful working in preclinical research. Every record needs to be traceable and audit-ready, and gaps like this can create headaches if we get asked to show our documentation trail later.

I also find the advanced conditional logic clunky to build and keep up with. Simple, single-trigger zaps work perfectly fine, no complaints there. But once I start adding multiple branching rules — like sorting incoming inquiries to separate general sales questions from leads asking for full preclinical study feasibility reviews — the whole workflow gets messy really fast. The interface doesn’t lay out all the logic in a clean, easy-to-follow way. If I step away from it and come back a month later to tweak a rule, I end up spending a bunch of time retracing every filter and condition I set up originally. It’s way too easy to accidentally mess up a rule, and route sensitive contact or lab-related information into the wrong folder or team inbox. That’s a risk we simply can’t take at Veridian BioLabs. We don’t have an IT team to double-check every automation I build, so any misconfiguration falls directly on me to catch. Review collected by and hosted on G2.com.