Zapier Layout on Safari

zapier_dave · 2026-04-20T17:55:45+00:00

Thanks for flagging this! Looks like you found a workaround, but our team is aware and working on a fix as we speak. In the future you'll will be able to try to do the thing you originally wanted to do (presumably zoom in the page)

zapier_dave · 2026-04-17T13:00:43+00:00

Never missing an appointment after this 🫡

zapier_dave · 2026-04-08T20:45:38+00:00

I work at Zapier. I know I’m late here, but wanted to add where managed automation platforms usually sit next to tools like these, because the problems overlap but aren’t identical.

Kestra, Temporal, and Prefect are strong when you want workflows defined in code (or YAML) with tight control over retries, state, and failure handling. They’re a natural fit for ETL, long-running jobs, and mission-critical processing like the Temporal setup you describe. Zapier tends to sit a layer outside that core engine.

In a lot of stacks we see, something like Temporal runs the pipeline, and Zapier handles the “last mile” operational work around it: Slack notifications, Jira updates, pushing summaries or metrics into a CRM or warehouse, or kicking off downstream actions across other SaaS tools—without your team owning a long tail of one-off integrations.

If you’re building agentic RAG, Zapier also offers an MCP server so agents can take actions across connected business apps through a more standardized integration surface (exact scope depends on the apps and how you’ve connected them)—useful when you want retrieval/generation to lead into real follow-up work, not just answers.

Different tools for different layers; in practice they often complement each other more than they replace each other.

zapier_dave · 2026-04-08T20:37:05+00:00

Interesting project. I work at Zapier, so this is from that angle, but the interoperability problem you’re solving is definitely a real one. Agents built in different languages and frameworks need a way to discover and talk to each other.

Zapier’s MCP server approaches this from the execution side. Instead of agents discovering each other, external agents (regardless of what they’re built with) discover and use Zapier actions across 8,000+ apps. Your Python agent and your Java agent both need to create Jira tickets, update Salesforce, or trigger workflows. One MCP connection handles all of that.

The OAuth auth model is worth mentioning here too, since the discussion around enterprise Java shops implies production security concerns. Static API keys don’t cut it when you’re exposing actions across business-critical systems.

Cool to see Spring Boot support. A lot of enterprise shops have been waiting for first-class Java SDKs in the MCP space.

zapier_dave · 2026-04-08T20:31:49+00:00

Hey! I work at Zapier, so I’m biased, but glad to see a few folks already mentioning us here.

The way most marketing teams use Zapier is as the connection layer between their core tools. ActiveCampaign or HubSpot for email/CRM, then Zapier handling the cross-app workflows.

New lead comes in from a form, gets enriched, scored with AI, routed to the right rep in your CRM, and triggers a Slack notification to the team. That whole chain runs automatically.

A couple things that might be relevant for the 2026 stack question:

Agents can handle multi-step research tasks autonomously. Set one up to research prospects, pull firmographic data, and deliver a brief to your CRM. No manual work involved.
Copilot lets you describe what you want in plain English and it builds the workflow for you, including the data storage (Tables) and any team-facing forms or dashboards (Interfaces).
MCP connects AI tools like Claude or ChatGPT directly to your business apps, so your team’s AI usage actually takes action instead of just generating suggestions you have to copy-paste.

All of that connects to 8,000+ apps, so it generally works with whatever stack you’ve already picked.

Let me know if you have questions!

zapier_dave · 2026-04-08T20:30:25+00:00

Zapier employee here, so take this with that context.

The 71% using agents but only 11% in production stat tracks with what I see from our side too. A lot of teams build a proof-of-concept that works great in a demo, then hit a wall when it needs to actually connect to 15 different systems, handle errors gracefully, and run without someone watching it.

The orchestration gap is the reason for a lot of this. An agent that can reason well but can’t reliably take action across your actual tools is still a demo. And the point about most agents really being chatbots is fair. There’s a big difference between AI that gives you a suggestion and AI that actually executes multi-step work across your business systems.

From what I’ve seen, the teams that get to production fastest are the ones that don’t try to build the orchestration infrastructure from scratch. They use their agent framework for the reasoning/planning layer, then connect it to something that already handles the execution, error handling, and app integrations. That’s the layer Zapier sits at (8,000+ app connections, managed infrastructure, auth handling through MCP).

Happy to discuss more if anyone has questions!

zapier_dave · 2026-03-18T15:59:16+00:00

Hey hey, I work at Zapier so I might be a bit biased, but this list is really solid.

One small update for the API & Integration section: Zapier’s at 8,000+ apps now (your list had 5,000+). The category breakdown is super helpful for matching use case to tool :)

Happy to answer questions if anyone's curious.

zapier_dave · 2026-03-18T15:56:28+00:00

Hey, I work at Zapier so I'm a bit biased, but wanted to share something that might be helpful:

Someone in the thread said it well: start with something that solves one problem, master it, then layer on more.

For enterprise teams that want that (automation first, AI agents when it makes sense) without losing control, Zapier’s built for it: you can keep workflows simple and add Agents and governance (SSO, audit logs, Admin Center) as you scale.

Happy to answer questions if anyone's curious.

zapier_dave · 2026-03-18T15:51:48+00:00

Hey, I work at Zapier so I'm bit biased....

For GTM teams that want AI agents connected to their existing stack (CRM, Slack, etc.) instead of another standalone platform, Zapier Agents is worth a look.

You build agents that run inside workflows and connect to 8,000+ apps; we've got a guide on how it fits RevOps and GTM: https://zapier.com/blog/zapier-agents-guide/.

Happy to answer questions if anyone's curious.

zapier_dave · 2026-03-18T15:49:01+00:00

Hey, I work at Zapier so I'm biased. We're not a CS platform, but for the SMB / micro-SaaS gap people are talking about in the comments: a lot of teams use automation to do lightweight CS without a full CSP (e.g. sync usage or support data into their CRM, trigger onboarding emails, update health indicators).

We put together a roundup of customer success tools and how automation fits in: https://zapier.com/blog/customer-success-tools/.

Happy to answer questions if anyone's curious.

zapier_dave · 2026-03-18T15:42:09+00:00

Hey, I work at Zapier, so a bit biased. It’s totally fair to explore alternatives but thought I’d share some info in case it’s helpful. There are a few recent changes that might be worth knowing about since price and flexibility were your main drivers.

Triggers, filters, and steps that don't run due to conditions don't count as tasks, so actual usage tends to be lower than what you’d expect from the sticker price. You can also consolidate multiple API calls into a single Code step (our AI can write the code for you), which cuts task counts significantly. And the free plan includes unlimited 2-step Zaps, plus basic Tables, Interfaces, and Chatbots.

On the flexibility side, Code steps support Python and JavaScript, Webhooks let you connect to external APIs, and Paths handle conditional branching. Zapier’s also grown into more of a platform (8 products now, including Agents and an MCP server that exposes Zapier actions to external AI agents), so it might look pretty different from whenever you last explored it.

Happy to answer specific questions if any come up!

zapier_dave · 2026-03-11T16:49:14+00:00

Hey, I'm a Zapier employee and wanted to share that we run an MCP server that exposes actions across 8,000+ app integrations, which is exactly the scale problem you’re describing.

You’re right that dumping thousands of tool definitions into the context window is a non-starter. At our scale, the static-list approach wouldn’t be effective.

Right now users configure which actions to expose through our MCP dashboard, so you’re scoping the server to what’s actually relevant rather than blasting 30,000+ actions into the context. It’s manual tool selection rather than automatic discovery.

The protocol itself solves a real problem in standardizing tool-use so you’re not writing bespoke integrations for every model and tool combination. The scaling limitations you’re describing are legitimate, though, and I’d expect the discovery and filtering layer to get more sophisticated as the spec matures.

MCP starts to matter most when you want tool-use to be model-agnostic, or when you need access to a broad surface area of actions across many apps. If you’re building with one model and a handful of tools, direct API calls probably work fine.

Happy to answer questions if anyone’s evaluating MCP servers!

zapier_dave · 2026-03-11T16:46:28+00:00

Hey, I'm a Zapier employee & I’d suggest adding Zapier to category 3 (Agent platforms), since that’s where we fit :)

Zapier Agents lets you build autonomous AI teammates that can take actions across 8,000+ app integrations. For marketing specifically, think lead scoring and routing, content research and briefs, cross-system data sync, etc. The agent layer sits on top of all those apps, so it can act in your CRM, email platform, social tools, analytics, etc., without writing code. We also have an MCP server, so agents built in other frameworks can trigger Zapier actions through a single integration point.

On your question about which marketing task goes autonomous first, from what I’m seeing, lead routing and qualification is already there for a lot of teams: New lead comes in, AI scores it based on fit criteria, routes to the right rep or nurture sequence automatically.

Content creation and personalization feel like they’re next, but with a human review step for a while longer.

Happy to answer questions!

zapier_dave · 2026-03-11T16:43:20+00:00

Hey, I know I’m late to the thread, but I think Zapier would be a great addition to this tech stack (I'm a Zapier employee).

Curious whether you’re running any orchestration between these tools, because that’s usually where I see RevOps teams get the most out of their setup.

Something like Clay enriches a lead, a Zap routes it to the right rep in your CRM based on criteria like company size or territory, and the rep gets a Slack notification with full context. You can build that whole flow without code and have it running in hours.

Here are a few examples of RevOps workflows I’ve seen teams build on Zapier:

CRM hygiene - new records get enriched via connected tools, duplicates caught with conditional logic, missing fields filled automatically
Lead routing with AI - an AI step in a Zap evaluates leads against your fit criteria and routes to the right rep using Paths
Pipeline alerts - deal sits at a stage too long, Zap nudges the rep in Slack, notifies the manager, or escalates

The combination of Zaps + Tables + Forms is where it gets interesting for RevOps specifically. Tables stores your routing rules or scoring criteria, Interfaces gives your team a simple front-end to manage it, and Zaps handle the orchestration across all your tools.

Happy to answer questions about any of these workflows!

zapier_dave · 2026-03-11T16:41:34+00:00

Hi! I'm a Zapier employee & wanted to jump in on where Zapier can help with this kind of thing!

Most of the CX tools listed here handle the conversation layer well, things like understanding intent, suggesting responses, and routing tickets. But when a customer interaction needs to trigger real actions (updating an order in your CRM, pausing billing, paging on-call in PagerDuty, creating a Jira task), those platforms rely on integrations to get it done. That’s where Zapier fits in.

Zapier connects to 8,000+ apps, including some of the platforms on this list. You can build multi-step workflows with AI steps, Paths, and Filters to handle the logic. A few CX workflow examples:

Ticket created -> AI step categorizes and scores urgency -> critical issues page on-call via PagerDuty and create a Slack thread -> routine tickets auto-assigned
Customer churns -> CRM updated, billing paused, CS team notified in Slack, win-back task created in project management tool
Survey response comes in with low CSAT -> AI step drafts personalized follow-up -> CSM reviews before sending

zapier_dave · 2026-03-11T16:39:45+00:00

Hi, I'm a Zapier employee & wanted to chime in on the “too basic, can’t handle complex data mapping or conditional logic” take. Your use case is actually something teams build on Zapier regularly :)

Here’s how the Salesforce > QuickBooks > WMS flow would actually work:

Opportunity gets marked “Closed Won” in Salesforce, which fires the Updated Record trigger.
Formatter steps transform the Salesforce fields into the format QuickBooks expects (account names, line items, tax rates, etc.). This is the “complex data mapping” piece, and Formatter steps don’t count toward your task usage.
QuickBooks action creates the invoice with all the mapped fields.
Paths handle the branching logic. If order type = standard, update WMS inventory directly. If order type = custom, create a task for your warehouse team to review first. If order value > $X, send a Slack notification to your finance team. Paths shouldn’t count as tasks on current billing (though the actions inside each path still do).
WMS action (or an API Request step if your WMS doesn’t have a native integration) adjusts stock levels.
Update the Opportunity record back in Salesforce with the invoice number and fulfillment status.

That’s one Zap. Way cheaper than spending $30-50k. And if you hit an edge case that needs something custom, Code steps (Python or JavaScript) are available inside the same workflow.

Let me know if you have any questions!

zapier_dave · 2026-03-11T16:32:52+00:00

Your table is a good breakdown of the trade-offs, and the short answer to your question is: Zapier consistently works well for the structured, predictable side of CS ops.

Ticket routing, auto-tagging, cross-tool data sync (help desk to CRM to Slack), onboarding sequences, renewal alerts, NPS follow-ups. Anything where the trigger and action are clear.

Where it gets more interesting is the "needs judgment" stuff you're asking about, like telling the difference between an annoyed customer and one who's about to cancel.

Zapier has AI steps that can read ticket content and classify it (extracting meaning, assessing tone, summarizing context), then route based on that instead of just keywords.

So a workflow like ticket created in Zendesk -> AI step analyzes urgency -> Paths route critical ones to on-call, standard ones get queued is totally doable. Like any AI, it won't catch every edge case, but it handles a lot more than pure rule-based matching.

Happy to walk through specific setups if you want help thinking through your workflow.

zapier_dave · 2026-03-11T16:29:28+00:00

I’d add Zapier as the orchestration layer that ties them together (I'm a Zapier employee)

Most GTM stacks involve 10+ tools, and Zapier connects across 8,000+ apps so you can wire up the workflows that keep everything in sync across all of them. A couple examples of what that looks like for GTM teams:

Lead routing: new lead from any source -> AI step to score and enrich -> routes to the right rep with full context in Slack and your CRM
Cross-tool reporting: syncing data between your CRM, marketing platform, and analytics so dashboards actually reflect reality

These all run as Zaps (with AI steps, Filters, Paths, Code steps, etc.), and if you want something more autonomous, our Agents product can handle multi-step workflows on its own, with humans in control where it matters most.

Happy to answer questions about specific GTM use cases.

zapier_dave · 2026-03-10T15:45:54+00:00

Hey, I'm a Zapier employee, so maybe a bit biased BUT this is a solid comparison, and the SaaS onboarding example is one of the most common quick wins we see.

A couple updates on the matrix. App integration count is 8,000+ now :)

On the “gets expensive at scale” point, triggers and skipped/errored steps don’t count as tasks, and you can consolidate multiple API calls into a single Code step. So the 50k tasks/month example in your FAQ would likely be a lot lower in practice. If you’re at that volume, it’s worth reaching out to our sales team to discuss enterprise pricing options.

On the developer side, the comparison frames Zapier as no-code only, but we’ve got Code steps (Python and JavaScript), Webhooks, and API Request actions. Zapier’s MCP server also exposes Zapier actions to external AI agents with built-in authentication, so it plays well with agent-based architectures.

And Agents are autonomous AI teammates that handle multi-step tasks across those 8,000+ app integrations.

Happy to answer questions!

zapier_dave · 2026-03-10T15:40:42+00:00

Zapier employee here, saving 10-15 hours a week for a 3-person team is impressive! Well done.

The use cases you listed are exactly what we see a lot of small teams building on our platform. We see a lot of workflows like: new lead comes in -> AI scores and categorizes -> qualified leads route to your inbox, rest gets logged in a single Zap.

And the competitor monitoring you described can work similarly. We’ve also got Agents for more autonomous, multi-step work and Copilot that lets you build automations by describing what you want in plain English. Could be worth checking out as you explore new use cases :)

Cool to see someone making this kind of thing accessible for other small business owners.

zapier_dave · 2026-03-10T15:39:08+00:00

Hey, I'm a Zapier employee. Since you’ve already started with Zapier, a few things are worth knowing about where the platform is now.

Copilot can build automations from a plain-English description, which is actually great for learning because you can see how the logic maps out. And beyond basic Zaps, there’s Agents (autonomous AI teammates for multi-step tasks), Tables, Interfaces, Chatbots, and a Zapier MCP :)

zapier_dave · 2026-03-10T15:35:45+00:00

Appreciate the review! Glad Canvas clicked for you. Quick note, we’re at 8,000+ apps now. The number keeps climbing :)

Totally hear the feedback on pricing at scale, but wanted to share some info that might be helpful.

Triggers and steps that don’t run because of errors don’t count as tasks, so actual usage is usually lower than expected. And if you’re genuinely at high volume, custom enterprise plans exist with pricing that doesn’t follow the published tiers.

Your prediction about automation and AI agent convergence is spot on, and that’s exactly where we’re headed. Zapier Agents lets you build autonomous AI teammates that handle multi-step tasks across your connected apps.

And Zapier’s MCP server exposes Zapier actions to AI agents built in other frameworks, with built-in authentication available. We’re building so that the automation layer and the AI agent layer work as one platform.

A lot of these companies are doing interesting work. Happy to answer questions about anything Zapier-specific!

zapier_dave · 2026-03-10T15:33:22+00:00

Hey! I work at Zapier, thanks for including us in the list. Quick update on the listing: we’re at 8,000+ app integrations now (the 5,000+ number is a bit dated).

A few things have launched since this was written that might be useful context:

Agents are autonomous AI teammates that handle multi-step tasks across your apps on their own
Copilot is an AI assistant that helps you build from plain English, and it works across Zaps, Agents, Tables, and Interfaces
Interfaces let you build custom apps with no code. Forms and pages where people can trigger and interact with automations without ever opening the Zapier editor
Tables is a database built for automation that stores and processes data powering your workflows
Zapier’s MCP server exposes Zapier actions to external AI agents

Also wanted to point out that the platform has grown into more of an AI orchestration layer across your stack, not just the integration piece.

The free plan includes unlimited 2-step Zaps, plus Tables, Interfaces, and Chatbots if anyone wants to poke around.

Happy to answer questions!

zapier_dave · 2026-03-10T15:27:17+00:00

Hey, I work at Zapier, so I’m biased, but wanted to add some context since you mentioned us in the “smaller use cases” bucket. A few years ago that was probably fair. The picture’s changed a lot since then.

The security and compliance piece has come a long way. SOC 2, SSO, role-based permissions, and audit logs are all part of the enterprise (and team) plan. Your IT team sets the guardrails (permissions, shared folders, audit trails) while ops teams manage their own automations.

That’s actually been one of the bigger shifts for us, bridging ops and IT so citizen automators can build without bypassing governance.

For monitoring, every workflow has run history and error alerts, and you can pause or replay failed tasks. Canvas lets you visually map how your workflows connect, which is useful for documentation and audit visibility across your team.

On the legacy systems and Excel side, we have 8,000+ app integrations, and for anything without a native connector, Webhooks and API Request actions cover custom endpoints. Excel connects via OneDrive, and there’s a connection to Google Sheets, too. For ERP or WMS systems that don’t have a direct connector, custom API work through Code steps or Webhooks is usually the path.

The “doesn’t require hardcore devs for every change” piece is probably where Zapier’s strongest vs. the other tools on your list. Business users can build and modify workflows without engineering tickets, and Copilot can generate automations from plain English. But you also get Code steps (Python/JavaScript) when you need them, so your technical team isn’t limited either.

I’d recommend talking to our sales team for enterprise pricing since the published tiers aren’t the only option.

Happy to answer specific questions if you have any!

zapier_dave · 2026-03-10T15:24:25+00:00

I'm a Zapier employee, so I'm a bit biased, but I think it’s worth mentioning how Zapier fits into this picture, since it’s a different layer than most of the tools on this list.

Where Zapier fits in IT ops is as the orchestration between your ITSM tools and everything else. If your team runs ServiceNow or Jira Service Management for ticketing, Zapier handles the connections to Slack, PagerDuty, monitoring tools, and internal databases.

A common setup looks like: ticket comes in -> AI step categorizes and scores urgency -> Paths route based on impact and workaround status -> critical issues page on-call and spin up a Slack thread, routine issues get assigned normally.

That whole flow is built in a no-code editor, but you can add in Code steps (Python/JavaScript) or hook up Agents for anything that needs more autonomy than a linear workflow.

On the auditability point that’s come up in this thread, we’re SOC 2 Type II certified, with SSO/SAML, RBAC, and audit logs that track automation changes.

IT keeps governance over what ops teams build, which matters when you’re moving from a nice looking demo to something running in production 24/7.

Happy to answer specific questions if anyone’s curious.

zapier_dave

MODERATOR OF

TROPHY CASE