I spent a month inside Zapier's free tier so you don't have to. Here are the actual numbers, where they bite, and the moment I switched to self-hosting n8n on a $6 VPS.

The hard limits, no marketing

Pulled straight from the Zapier docs (and tested against my own account):

A task is one successful action. Trigger checks don't count. Filters and Formatter wouldn't count either — except you can't use them.

What 100 tasks/month feels like

Quick math: if your Zap fires hourly, that's 24 × 30 = 720 tasks/month. Done in 4 days. If it fires on every new email — 50/day average — done in 2 days.

Realistic free-tier capacity:

• 1 Zap firing 3x/day → 90 tasks/month ✓
• 1 Zap firing on form submissions, ~3/day → 90 tasks/month ✓
• 1 Zap firing on every Shopify order in a real store → blown by day 5 ✗

When you hit the cap, runs aren't lost — they're held, queued in your Zap History. They replay when the month resets. So for batchable, non-time-critical stuff, the limit is annoying but survivable. For real-time alerts, it's fatal.

The 2-step thing is the actual killer

People focus on the 100-task limit. The 2-step limit is worse.

Two steps means: one trigger + one action. No filter ("only continue if amount > $100"). No formatter ("convert timestamp to ISO"). No path ("if VIP customer, route to sales; else, ignore").

Real automations need conditionals. Without them you get this anti-pattern:

Typeform submission → Create HubSpot contact

…where now every form submission creates a contact, including bots, duplicates, and the 3 internal team members testing the form. You can't filter them out in Zapier Free.

The "fix" is splitting logic into multiple Zaps, but each runs separately and you can't share state — you're just paying tasks twice and getting worse logic.

15-minute polling, in case you forgot what slow feels like

Polling triggers (most non-instant apps) check for new data every 15 minutes on Free. Pro drops to 2 minutes.

What this means in practice:

9:00 — lead fills out form
9:14 — Zapier checks, sees lead, runs Zap
9:14 — Slack alert fires

A 14-minute delay for a "real-time" alert. If you're competing for response time on leads (and you are), you've already lost.

Instant triggers (Stripe, Shopify, GitHub, a few others) bypass polling — they push to Zapier, which pushes to you. But most apps don't expose instant triggers on Free.

What "premium apps" actually locks out

Zapier's premium-app list includes: Salesforce, QuickBooks, ShipStation, PayPal, Magento, Microsoft Dynamics, Webhooks by Zapier, certain Stripe triggers, and a long tail of others.

The webhooks one is the kicker. If your stack relies on receiving webhook events from any service that doesn't have a native Zapier integration — and most niche/regional services don't — you literally cannot build the integration on Free. You need Pro.

Free vs Pro: the real cost gap

In 2026, there is no "Starter" plan anymore. The jump is Free → Pro, and Pro is $19.99/month billed annually or $29.99 monthly. That gets you 750 tasks, multi-step Zaps, premium apps, webhooks, filters, paths, formatter, 2-minute polling, autoreplay. Team is $103.50/mo for 2,000 tasks and 25 seats.

If you actually need automation that works, Pro is the floor. If you don't actually need it, Free is fine forever.

The "screw it, I'll host it myself" option

If you're reading dev.to, you probably know n8n — open-source, self-hostable, no task counter, no two-step limit, real webhooks, code nodes. Here's the entire setup:

# docker-compose.yml
version: "3.8"

services:
  n8n:
    image: docker.n8n.io/n8nio/n8n:latest
    restart: unless-stopped
    ports:
      - "5678:5678"
    environment:
      - N8N_HOST=n8n.yourdomain.com
      - N8N_PROTOCOL=https
      - N8N_PORT=5678
      - WEBHOOK_URL=https://n8n.yourdomain.com/
      - GENERIC_TIMEZONE=Europe/Kyiv
      - N8N_BASIC_AUTH_ACTIVE=true
      - N8N_BASIC_AUTH_USER=admin
      - N8N_BASIC_AUTH_PASSWORD=${N8N_PASSWORD}
      - DB_TYPE=postgresdb
      - DB_POSTGRESDB_HOST=postgres
      - DB_POSTGRESDB_DATABASE=n8n
      - DB_POSTGRESDB_USER=n8n
      - DB_POSTGRESDB_PASSWORD=${POSTGRES_PASSWORD}
    volumes:
      - n8n_data:/home/node/.n8n
    depends_on:
      - postgres

  postgres:
    image: postgres:16-alpine
    restart: unless-stopped
    environment:
      - POSTGRES_DB=n8n
      - POSTGRES_USER=n8n
      - POSTGRES_PASSWORD=${POSTGRES_PASSWORD}
    volumes:
      - postgres_data:/var/lib/postgresql/data

volumes:
  n8n_data:
  postgres_data:

Drop this on a $6/month Hetzner CX22 (or any VPS), point a subdomain at it, slap Caddy or Traefik in front for TLS, and you've got unlimited everything. The real cost is operational: you maintain it, back it up, update it. If you already run a VPS, this is a free upgrade. If you don't, the maintenance overhead probably isn't worth saving $20/month.

When Make's free tier beats Zapier's

If self-hosting feels like too much, Make.com's free plan is the obvious migration:

• 1,000 operations/month (10× Zapier)
• Unlimited scenarios
• Multi-step workflows
• Filters, routers, aggregators
• Real webhooks on free
• Minimum 15-minute scheduling (same as Zapier Free)

The cost is a UI that's more powerful and more confusing. Zapier optimised for "anyone can use it"; Make optimised for "anyone who's willing to learn can do anything." If you're a dev, Make's editor feels like home within an hour.

The decision tree

Are you just testing automation as a concept?
├── Yes → Stay on Zapier Free, set a 2-week timer, re-evaluate
└── No  → Do you already run a VPS?
         ├── Yes → Self-host n8n
         └── No  → Are most of your apps in Zapier's premium list?
                  ├── Yes → Zapier Pro ($19.99 annual)
                  └── No  → Make.com free tier

Most devs I know end up at n8n or Make. The Zapier Free → Pro path makes sense almost exclusively if your team already standardised on Zapier and your accounts are deeply integrated. For greenfield, the alternatives win on price/feature ratio.

When Free is genuinely enough

I don't want to sound like "always self-host." Zapier Free works for:

• Personal triage Zaps. Starred Gmail → Todoist task. Maybe 1 task/day.
• Form backup. Typeform → Google Sheet. Under 100 submissions/month.
• Side-project notifications. New Stripe customer → Slack DM, if you're under 100/month and Stripe's instant trigger covers you.
• Sandbox testing. Want to demo automation to a non-technical colleague? Zapier's UX is the best teaching tool.

Anything beyond that — anything with logic, premium apps, real volume, real-time needs — you'll outgrow it within the first month.

TL;DR

100 tasks/month + 2-step limit + 15-minute polling + no webhooks = a generous demo, not a production tool. For real work in 2026: Make.com Free if you want to stay no-code, n8n self-hosted if you have a VPS, Zapier Pro if your team is already locked in. The "Starter" tier is gone; the Free→Pro jump is the only path inside Zapier itself.

Originally published on trackstack.tech with a fuller decision framework and FAQ.