Triggers: what starts the workflow
A trigger is the event that fires the automation. Every run begins with one.
- App events — a new row in Airtable, a new Stripe payment, a new Gmail message
- Webhooks — an inbound HTTP call from any system
- Schedules — every 5 minutes, every night at 2am, first of the month
- Manual — a button click for on-demand runs
Conditions: deciding what runs
Conditions let one workflow handle many cases without turning into a mess. They're the difference between a fragile automation and one that lasts years.
- Filters — stop the run entirely if data doesn't qualify
- Routers / branches — send different data down different paths
- Switches — pick one of many outcomes based on a single value
Actions: the actual work
Actions are the steps that do something in the outside world — send an email, create a record, call an API, post to Slack. Most workflows are 3–8 actions long.
Data mapping: passing values between steps
Data mapping is what makes multi-step workflows feel like magic. Each step exposes its output; later steps reference those outputs by name. Master this and you've mastered 80% of automation.
A real workflow, end to end
Here's what a lead-capture workflow looks like when you put it all together.
- Trigger — new Fillout submission
- Filter — only continue if the plan is Pro or Enterprise
- Action — create a contact in your CRM
- Action — add a row to the Airtable pipeline
- Router — Enterprise → book with sales; Pro → send onboarding email
- Action — post the result in Slack
Choosing the right tool for the workflow
Not every workflow belongs on every platform. Match the tool to the shape of the problem.
- Simple linear flows — Zapier is fastest to build
- Branching logic and iterators — Make is the sweet spot
- High-volume, cost-sensitive flows — Pabbly Connect stays flat as you scale
- Self-hosted or data-sensitive — n8n gives you full control
Common mistakes to avoid
Most broken workflows come from the same handful of mistakes.
- No error handling — silent failures are the most expensive kind
- Overloaded single workflow — split anything above ~15 steps
- Hard-coded values — put IDs and URLs in a config record instead
- No logging — you can't fix what you can't see