n8n
Open-source and self-hostable, node-based — the choice when workflow logic needs to live in your own infra, or you need capabilities SaaS tools gate behind higher tiers.
Lesson 4 of 4
Low-Code/No-Code Automation
Automating a recurring ops task doesn't always mean writing a service — but knowing when it stops being "just a Zap" is its own skill.
The three big players
Same core idea, three different trade-offs between simplicity, power, and control.
Zapier
The most widely integrated SaaS automation tool — thousands of app integrations, a simple trigger→action model, easiest to get a non-technical teammate using.
Make
A visual, more powerful branching and routing model than Zapier's linear zaps, still fully hosted — a middle ground between Zapier's simplicity and n8n's control.
The core automation model
Learn this shape once and any specific tool's UI is just details.
Every one of these tools follows the same shape: a trigger fires — a new row, an incoming webhook, a schedule — one or more actions run in response, and data from earlier steps gets mappedinto later ones. A workflow with more than a few branches, needing real error handling and retries, or touching sensitive data, usually outgrows a visual builder fast — that's the point to write actual code instead of adding another branch.
Exercises
Look at the sanitized automation trace below, then work through both exercises.
Trigger: New row in "Support Escalations" sheet
→ Action 1: POST to Slack webhook (#escalations channel)
→ Action 2: Create Zendesk ticket (row.customer_email → ticket.requester)
→ Action 3 (conditional): If row.priority = "P1", page on-call via PagerDuty
Failure: Action 2 fails (Zendesk rate limit) → Action 3 never runs
(no retry configured — escalation silently incomplete)Concept check
Answer in your head first, then click a question to reveal the answer.
Scenario checklist
Work through the sample automation trace and check each item off. Progress is saved in your browser.
Go deeper
These primers are a starting point. Read the primary sources to build real fluency.
Training Notes
What building this project taught me.
This module closes the trail on purpose
Everything else in Applied AI/ML assumes you're writing code. This lesson is the opposite end of the spectrum — recognizing when a workflow genuinely doesn't need code, and when it has outgrown not needing it.
The trace below is a common real failure, not a contrived one
A workflow silently stopping partway through because a downstream step failed with no retry configured is one of the most common no-code automation incidents in practice.