Workflow Design
Structuring n8n workflows.
Articles in Workflow Design
- n8n Executions Panel: Debugging Failed Runs and Managing Data Retention — The Executions list is where every past workflow run lives -- and where most debugging actually happens. A guide to reading execution data, manually retrying a failed run, and the retention settings that determine how much history you keep.
- n8n Rate Limiting: Avoiding 429 Errors and API Throttling in Workflows — A workflow that works fine at 10 items falls over at 10,000 -- not from a bug, but from the third-party API pushing back. Here is how to build n8n workflows that respect rate limits instead of hoping they never get hit.
- n8n Filter Node vs IF Node: Choosing the Right Data-Reduction Logic — Both nodes evaluate a condition. Only one of them is built for narrowing down a list of items to the ones that matter -- using the other for that job works, but produces a messier workflow than necessary.
- n8n Respond to Webhook vs the Webhook Node: Building Synchronous APIs Without Silent 200s — The Webhook node decides when to answer; the Respond to Webhook node decides what to answer. The four response modes, the node's options, why a forgotten branch returns 200 rather than silence, and how to reply early for slow work.
- n8n Form Trigger: Internal Forms, Multi-Page Flows and Branching Without a Frontend — Use n8n's Form Trigger to host internal forms that start a workflow: element types, authentication, test and production URLs, a worked time-off request, multi-page branching with n8n Form nodes, and when a dedicated form tool is better.
- n8n Google Sheets Node: Reading, Writing, and Appending Rows in Workflows — Google Sheets is the most common landing spot for n8n automation output, and the node has more operation modes than people realize. A practical guide to Read, Append, Update, and Append or Update -- and the row-matching mistakes that corrupt a sheet quietly.
- Compensating Actions: What to Do When Step 3 of a 5-Step AI Automation Fails — A five-step automation that fails on step three doesn't leave you at step two — it leaves you with two completed side effects and no built-in way to undo them.
- Sequential vs Parallel AI Workflow Steps: When Parallelizing Actually Saves Time — Running every LLM call in a workflow sequentially is simple but slow, and running everything in parallel can silently break correctness. Here's how to decide when a parallel AI workflow step actually helps.
- n8n Static Data: Storing State Between Workflow Executions — A workflow that needs to remember "where it left off" between separate scheduled runs doesn't always need a full external database. n8n's static data feature covers a surprising amount of this need on its own.
- n8n Edit Fields (Set) Node: Modes, Pass-Through Fields, Dot Notation and Types — The renamed Set node explained: Manual Mapping and JSON Output modes, what happens to fields you didn't mention, dot notation, type conversion and binary data, migrating old Set nodes, and when to use another node.
- n8n Workflow Versioning: Tracking Changes Without Relying on Memory — n8n's built-in version history helps, but it's not a substitute for a durable, searchable record of what changed in a workflow and why. Here's what real versioning looks like in practice.
- n8n Wait Node: Resume a Paused Workflow via Webhook (resumeUrl) — Building an approval step that might not get a response for hours or days means the workflow can't just sit there blocking. The Wait node's webhook-resume mode is built exactly for this.
- n8n Environment Promotion: Moving Workflows From Dev to Production Safely — Copying a workflow from a dev n8n instance straight into production is how a hardcoded test URL or a dev-only credential ends up live. Here's a safer promotion pattern.
- n8n Expressions Explained: How Items Work and the Mistakes That Break Them — The data model behind n8n expressions ($json, $input, $('Node').item and .first(), $now) and fixes for the mistakes it explains: wrong node, missing fields, unexecuted branches, string numbers, hand-formatted dates and whole-list logic.
- n8n Binary Data: Working With Files, Images and PDFs (and Why They Disappear) — Files travel in a separate binary part of each n8n item. Where they live, the nodes that convert them (Extract From File, Convert to File, HTTP Request), why they disappear, reading bytes in a Code node, sending files to APIs, and the memory setting that matters for large files.
- n8n Loop Over Items (Split in Batches): When You Need It and How It Works — Most n8n nodes already process every item, so you often don't need a loop. When you do (rate limits, run-once nodes, memory, repeat-until), here's how Loop Over Items works, why it all runs in one execution, how to pace and how to make long jobs resumable.
- n8n Code Node (Formerly Function Node): Modes, Limits, Python and When to Use It — The Code node replaced Function and Function Item in n8n 0.198.0. Its two modes, its documented limits (no HTTP requests or file access, restricted modules), native Python vs the removed Pyodide mode, when code beats built-in nodes, and how to handle bad records and test logic.
- Debugging an n8n Workflow That Works Manually but Fails on Trigger — It's one of the most disorienting n8n bugs: click "Execute Workflow" and everything works, but the live trigger fails silently. It's almost always one of four specific causes.
- n8n Merge Node Patterns: Modes, Join Types and Why Items Disappear — Every Merge node mode (Append, Combine, SQL Query, Choose Branch), the five output types for matching fields and their SQL equivalents, the options behind most 'missing item' bugs (Fuzzy Compare, Multiple Matches), timing, and how Merge affects item linking.
- n8n Sub-Workflows: Building Reusable AI Automation Components — How to use n8n sub-workflows to turn repeated logic — API calls, LLM prompts, validation steps — into reusable components, so a fix or upgrade only has to happen in one place.