Zapier in 5 minutes

Issue #16 - The default glue for GTM stacks — and the bill that sneaks up on you

What it is

Zapier acts as connective tissue, shuttling data between systems without requiring engineering support. You set up a trigger in one app — a new form fill, a deal stage change, a Slack message — and Zapier fires one or more actions in other apps in response. Zapier offers integrations for more than 9,000 apps and helps you easily move data between them to automate repetitive tasks. No API keys, no deployment pipeline, no waiting for an engineer to be unblocked. For a RevOps person or SDR leader who needs two tools talking to each other this afternoon, that matters.

Where it sits in the stack

Zapier lives in the orchestration/automation layer — it's not a data provider, enrichment tool, or outreach sender. Zapier connects tools but does not provide data, buying signals, or insights of its own.

Clay enriches the data, HubSpot manages the pipeline, Smartlead sends the email — but Zapier orchestrates the workflows between them. It most commonly pairs with or replaces point-to-point native integrations, and it tends to get swapped out for Make or n8n when workflows get complex enough to need visual canvases, loops, or volume that makes the task pricing sting.

Three workflows people actually run

1. Inbound lead routing and CRM enrichment A prospect fills out a demo form (Typeform, HubSpot Forms, etc.). Zapier fires immediately: it pushes the raw lead into your CRM (HubSpot or Salesforce), calls an enrichment API (Clearbit, Apollo, or a webhook into Clay) to pull firmographics, then writes the enriched fields back to the contact record. A final step posts a Slack alert to the right AE channel based on the company's industry or employee count — a Paths step handles the routing logic, and since Paths doesn't count as a task, the branching is free. One of the highest-ROI Zapier use cases is triggering data enrichment automatically: a new inbound lead arrives, Zapier sends the email to an enrichment API to pull firmographic data, enriched data writes back to the CRM, and based on enrichment results, the lead is routed to the right sales team or sequence. Count your tasks carefully here: each write-back action is a separate task.

2. Signal-to-sequence enrollment You're watching for buying signals — a job change on LinkedIn (via a tool like Surfe or a webhook), a G2 review posted by a target account, or a Slack community mention. Zapier catches the trigger, checks against a Zapier Table (no task cost) to see if this contact was already touched in the last 30 days, then either enrolls them in an Outreach or Instantly sequence or skips them. The Table lookup and filter steps are free; only the sequence enrollment action burns a task. Launch outreach workflows the moment buyer activity happens. Send follow-ups from your CRM, alert reps when prospects engage, and create tasks after calls or demos. Start outreach sequences when deals advance, forms convert, or meetings end so reps never miss the right moment to follow up.

3. Post-demo follow-up automation A Calendly meeting ends. Zapier triggers off the event completion, pulls the meeting title and attendee email, runs an AI by Zapier step to draft a follow-up email summary using the built-in model (costs 1 task; upgrading to Claude costs 5 tasks — see the pricing section), creates a follow-up task in your CRM, and posts the AI draft into a Slack thread for the AE to review and send manually. Turn completed demos into follow-up tasks, recap emails, and next-step reminders without extra admin work. A practical note: put your filters before action steps, not after. A filter placed after an action pays for that action on records it then discards; the same filter placed first does not. One client reportedly cut their monthly task burn by ~30% just by reordering steps.

What it costs

Zapier pricing in 2026 is structured into four tiers: Free (100 tasks per month, 2-step Zaps only), Professional from $29.99 per month (750 tasks, unlimited multi-step Zaps), Team from $103.50 per month (2,000 tasks, shared workspaces), and Enterprise (custom).

Annual billing saves 33% across all paid plans. On the annual Professional plan, that's $19.99/month for 750 tasks.

The gotchas:

• Task multiplication. Each action step in a Zap counts as one task when it runs successfully. A 5-step Zap uses 5 tasks per trigger.

Your 750 tasks translate to only 150 workflow runs if you're using multi-step automation — which is the entire point of using Zapier.

• AI steps cost more tasks. Zapier includes a range of AI models. The default AI model costs one task per run, just like any other action. An Advanced AI by Zapier step counts as three tasks, and a Premium step (e.g., Claude) counts as five.

• MCP calls are expensive. Zapier MCP connects AI clients (Claude, ChatGPT, Cursor) to 9,000+ apps through a single auth layer, available on all plans — but each successful MCP tool call costs 2 tasks. This is the key gotcha if you're routing AI agent actions through Zapier MCP at volume.

• Pay-per-task billing is on by default. Pay-per-task billing is enabled by default if you joined Zapier after January 2024. If you joined before this date, you may need to opt in. If you exceed your plan's task limit, you'll automatically switch to pay-per-task billing for the remainder of your pay period.

Task overages cost 1.25x your base rate.

This sounds reasonable until a misconfigured Zap loops. A common pattern in reviews involves surprise invoices of $400–$1,200 from runaway automations — a Zap that accidentally triggers itself repeatedly, burning through tasks before anyone notices.

• The Pro → Team jump is brutal. The jump from Professional ($29.99 for 750 tasks) to Team ($103.50 for 2,000 tasks) is painful. You're paying 3.4x more for 2.7x more tasks.

• Premium apps require paid plans. Salesforce, some HubSpot features, and similar enterprise connectors are gated behind paid tiers. Paths (if/then branching) and Formatter are Professional plan only.

Pricing verified 2026-07-10 — check the source before buying.

Who it's for (and who should skip it)

Use it if your team is non-technical, you need something working today, and your workflows stay simple — under 3–4 action steps, running fewer than a few hundred times a month. You can ship a working integration in an afternoon instead of waiting weeks for an engineering sprint. When your GTM engineering stack needs a new connection, Zapier is often the fastest path. It's also genuinely useful as a prototyping layer before you commit to a custom build.

Skip it (or at least limit it) if you're running high-volume outbound. Zapier's pricing model charges per task — each step in a Zap counts. For high-volume GTM workflows enriching 5,000 contacts or scoring 10,000 leads, Zapier becomes expensive fast. At 10,000 tasks/month you're looking at ~$600/month; Make handles equivalent volume for around $29/month. If you have a technical person on the team who can tolerate a steeper setup curve, Make or self-hosted n8n will cost a fraction of the price at scale. Many mature teams keep Zapier for the simple stuff so ops teams can maintain it without engineering support — and move the heavy lifting elsewhere.

Sources

zapier.com/pricing · zapier.com/solutions/sales · help.zapier.com – pay-per-task billing · help.zapier.com – Zap limits · nocode.mba – Zapier pricing 2026 · syncgtm.com – Zapier review · eesel.ai – Zapier subscription plans · automationatlas.io – Zapier pricing explained · factors.ai – Zapier vs Make vs n8n for GTM

Rate today's issue (one tap): 🔥 Loved it · 👍 Useful · 😐 Meh · 👎 Miss

Want a tool covered? Request it here - most-requested tool gets covered every Friday.

Pricing verified against live sources. Spot an error? Just reply - a human reads every response.