Zapier's step limit forces a choice—here's how to make it
The coffee machine hisses in a corner office in Manchester, someone’s second monitor glows with a Zapier dashboard at 6:47 a.m., and a workflow that ran fine for eleven months just hit the five-step ceiling and stopped cold.
Zapier’s free and Starter tiers cap you at five steps—split, nest, or pay
When your automation grows past the step limit, the right move depends on task frequency and margin, not features.
Zapier’s free plan allows three-step Zaps; Starter gives you five. Hit that ceiling and you face three options: split the workflow into multiple Zaps that trigger each other, consolidate steps using webhooks or custom code, or upgrade to Professional at $74/month for twenty steps. Most operators pick wrong because they optimise for elegance instead of cost per task.
Splitting works when trigger volume is low and the handoff is clean—use a webhook or storage app as the bridge. Nesting Zaps inside Zaps burns two tasks per run (one to trigger, one to execute), so calculate whether doubling task consumption still beats the upgrade threshold. If you’re running 1,500 tasks a month on Starter’s 750 allowance and considering Professional’s 2,000, the break-even is clear: pay for headroom. But if your workflow fires twelve times a day and you’re nowhere near task limits, splitting costs you nothing but setup time.
The third path—consolidating via Code by Zapier or a single API call—only makes sense if you can script the middle steps into one action. Most can’t. The decision tree is task volume, then margin per conversion, then maintenance overhead. Zapier wants you to upgrade; sometimes you should, sometimes two three-step Zaps do the same work for free.
TACTIC
When Zapier filter conditions silently fail because field types don’t match
You set a filter to check whether a number exceeds 100, but Zapier receives it as text from your form platform. The Zap skips every time and logs no error—just “Filter did not pass.” Text-as-number comparisons, empty-string checks, and Boolean-as-text mismatches account for most silent filter failures. The fix is formatting steps before the filter or explicit type conversion, but diagnosing the mismatch means inspecting the raw task history and checking what Zapier actually received versus what your condition expected.
READER QUESTION
AI prompt templates drift when you reuse them across months—version control fixes it
A reader asked why the same ChatGPT prompt that produced sharp product descriptions in February now returns vague, generic copy in July. Context drift: models update, your product catalogue changes, competitor language shifts, and the template that worked six months ago no longer aligns with current inputs. The solution isn’t rewriting from scratch every time—it’s versioning prompts with dates, testing output against a reference set, and flagging when performance degrades. Treat prompts like code: track changes, document why you edited, and retire versions that no longer perform.
WORTH READING
Social media automation tokens expire silently—here’s the window for each platform
Your Buffer or Publer connection breaks without warning because Instagram’s OAuth token expired after sixty days, and the scheduler never told you until three weeks of posts failed to publish. Every platform sets its own token lifespan: Facebook’s lasts sixty days, LinkedIn’s is also sixty, Twitter’s (now X) varies by app tier, and YouTube’s refresh tokens theoretically never expire but can be revoked server-side. Most scheduling tools attempt silent renewal, but when that fails—often due to password changes or security reviews—your queue dies quietly. Knowing the expiry window lets you set calendar reminders to re-authenticate before the break, not after.
Know someone who would like this? Forward today’s email — every operator we reach is one closer to running an online business with a little less friction.