Work that runs itself.
Production n8n pipelines with idempotency locks, dead-letter queues, and schema contracts. 600+ built across the book of work; 500+ still running in production.
Automation Multi-Client n8n for Agencies: Isolate Credentials or Inherit Incidents
Agencies isolate n8n by instance or paid Projects — folders are not tenancy, and hosting client credentials needs a verified license check with n8n.
Automation Production n8n: The Handbook for Automations That Survive Contact With Reality
How to run n8n in production: idempotency, dead-letter queues, schema contracts, approvals, and the ROI filter that decides what deserves a workflow.
Automation Who Owns the Automation When the Builder Leaves
When the builder leaves, automations survive only if a named owner, a half-page runbook, and company-owned credential handoff are already in place.
Automation Why Your Automation Broke on a Tuesday
Six hundred workflows in, the failures are boringly predictable. Four structures prevent almost all of them, and none of them are exciting.
Automation Airtable as an Automation Backend: Fine Until Rate Limits Become the Product
Airtable works as an automation backend until the 5 req/s ceiling and plan record caps force you to move the system of record — stop patching forever.
Automation n8n vs Make vs Zapier in 2026: Choosing the Rail, Not the Logo
A practical 2026 comparison of n8n, Make, and Zapier for agencies and ops teams — when each wins, where each breaks, and how to choose without hype.
Automation Idempotency Keys in n8n: Stop Double-Charging, Double-Emailing, Double-Everything
How to implement idempotency keys in n8n so duplicate webhooks cannot double-charge, double-email, or double-create CRM records.
Automation Migrate Zapier to n8n Without a Big-Bang Cutover
Migrate Zapier to n8n with dual-run, webhook URL remaps, credential remaps, and a documented rollback — rebuild by hand; no official importer to trust.
Automation Dead Letter Queues for Automations: Where Failed Work Goes to Be Fixed
How to build dead-letter queues for n8n automations so failed work is quarantined, visible, and replayable — instead of lost in retry storms.
Automation Cron vs Webhook: Pick the Trigger That Matches the Failure Mode
Choose cron vs webhook by failure mode: webhooks miss when subscriptions die; schedules miss when the job never runs — hybrid reconciliation covers both.
Automation Schema Contracts Between Tools: The API Discipline Most Automations Skip
Why automations need schema contracts between tools, how to validate JSON in n8n, and how to stop silent nulls from poisoning your CRM.
Automation Staging for n8n: Prove Failure Cases Before Customers Feel Them
n8n has no built-in staging env — use a second instance or project, separate credentials, pinned data, and a promotion checklist before production edits.