n8n
Duplicate data is the silent killer of automations — the same lead emailed twice, the same order processed twice, the same alert fired twice. The Remove Duplicates node is n8n’s purpose-built fix, and it does more than most people realize, including remembering what it has seen across separate runs. Removing
n8n
Sooner or later a built-in node won’t do exactly what you need — and that’s when the Code node earns its place. It lets you run JavaScript or Python directly inside a workflow to reshape data, do math, or build a payload no other node can. Here’s how
n8n
The Switch node is how you build “if this, go here; if that, go there” logic in n8n without stacking a dozen IF nodes. Where the IF node only gives you a true/false fork, the Switch node lets one node send each item down one of many outputs. This
n8n
Most n8n workflows fail not because a node breaks, but because the wrong data slips through. You pull 300 orders and only need the paid ones. You sync 1,000 contacts but only want the ones with an email. You process support tickets but only care about the high-priority ones.
n8n
Almost every useful automation eventually touches a date. You want to send a reminder three days from now, stamp an email with today's date, calculate how many days are left until a subscription renews, or fire a workflow at 9 AM in the customer's timezone. In
n8n
Sooner or later every n8n workflow needs to pull two streams of data back together — a customer record from your CRM joined with their orders from a database, or results from three APIs combined into one report. That's the job of the Merge node. Here's how
n8n
One of the most common beginner mistakes in n8n is trying to loop over an array manually when a single node already does it for you. The Split Out node takes a field that contains a list and turns each element into its own item — so the rest of your
n8n
Not every workflow should run start-to-finish in one burst. Sometimes you need to wait — an hour before a follow-up, a day before a reminder, or indefinitely until a human approves. That’s exactly what the n8n Wait node is for, and it’s one of the most underused nodes in
n8n
Every non-trivial workflow eventually needs to make a decision: if this, do that; otherwise, do something else. In n8n, that’s the job of the IF and Switch nodes. Get them right and your workflows stay readable; get them wrong and you end up with a tangle of duplicated branches.
n8n
n8n
n8n
Real automations rarely pull from one source. You're joining CRM records with enrichment data, combining rows from several sheets, or rolling many items into one summary. The Merge and Aggregate nodes are how you do that in n8n — and knowing which to reach for saves hours of confusion.