The n8n stack I use for every client - and why

Automation architecture should survive contact with reality: schema drift, partial failures, humans changing their minds mid-quarter. I default to a spine that is boring where it must be reliable—Airtable for operational truth at human speed, n8n as the orchestration layer, Supabase when data needs auth, constraints, and portable ownership.

n8n wins here because the graphs stay inspectable. Non-developers can reason about what happens when a webhook fires; engineers can step in when retries, branching, and secrets get serious. It’s glue that doesn’t pretend it isn’t glue.

The pattern is always the same: model the workflow as the business actually runs it, then automate the seams—notifications, enrichment, dedupe, writebacks—not the soul of the work. That’s how stacks stay maintainable across industries.