Design a Zap: Trigger, Filter, and Actions on Paper First
Objective: Apply the lesson's 'map before you build' rule (Common Mistake 2) to design a complete Zap on paper, trigger, filter, and every action in order, before ever opening the Zapier interface.
You're the growth marketer at Mailchimp's own internal team, standardizing how new webinar registrants get routed into the right nurture sequence.
Write the full logic string first ('When X, AND if Y, then do A then B then C'), matching the lesson's Zap anatomy: one trigger, one filter, then ordered actions.
Before you start
What you'll need
Free path (everything below is enough to finish)
Free, fastest way to draft trigger/filter/action order without paying for a Zap you'll rebuild
Free plan (5 Zaps, 100 tasks/month) is enough to build and test one Zap from this spec
Paid upgrades (optional, faster/deeper)
Stay on Zapier's free plan until the spec's estimated task volume gets close to 100/month, then upgrade to Starter rather than switch tools mid-project.
Cheaper per-operation pricing once a single Zap needs more than a handful of branches
The process
1 step
Step 01 of 01
Every Zap follows the same shape: a Trigger app event, an optional Filter that stops irrelevant runs, then one or more Actions in sequence. The lesson's Mistake 2 is skipping this on-paper design step and discovering broken logic mid-build.
New Zoom webinar registrants need to reach the right nurture sequence, but only if they registered for the 'Growth Marketing' series, not any other webinar on the account.
Procedure
- Write the trigger: 'New registrant in Zoom webinar'
- Write the filter: 'Only continue if Webinar Name contains Growth Marketing'
- List Action 1: 'Create/update contact in Mailchimp'
- List Action 2: 'Add tag webinar-registered-growth to that contact'
- List Action 3: 'Enroll contact in the Growth Marketing nurture automation'
- Estimate monthly task volume: registrants/month x 3 action steps
Snowflake webinar Zap spec (excerpt) TRIGGER: New registrant, Zoom webinar 'Data Cloud Deep Dive' FILTER: Webinar Name contains 'Data Cloud' ACTION 1: Create/update contact in Marketo ACTION 2: Tag 'webinar-data-cloud' ACTION 3: Enroll in Data Cloud nurture sequence Estimated volume: 180 registrants/month x 3 actions = 540 tasks/month
Healthy
The filter line exists and names the exact field and value it checks, catching cross-webinar contamination before any action runs.
Unhealthy
Skipping straight to Action 1 with no filter line, so every registrant from every webinar gets the same nurture sequence.
What this means
A filter is not optional decoration; a missing filter is the single most common reason a Zap 'sort of works' but pollutes lists over time.
So what do I do about it?
| Symptom | Action | Effort |
|---|---|---|
| Multiple webinars share one trigger with no filter | Add a filter step naming the exact field/value before building any action | 5 min |
Final deliverable
A written Zap spec (trigger, filter, ordered actions, estimated monthly task volume) ready to build directly in Zapier with zero mid-build surprises.
See a reference example
Snowflake webinar Zap spec (excerpt) TRIGGER: New registrant, Zoom webinar 'Data Cloud Deep Dive' FILTER: Webinar Name contains 'Data Cloud' ACTION 1: Create/update contact in Marketo ACTION 2: Tag 'webinar-data-cloud' ACTION 3: Enroll in Data Cloud nurture sequence
Success criteria
You're done when you can:
- Spec includes a named filter condition, not just a trigger and actions
- Monthly task volume is estimated before the Zap is built