What is the difference between the Set node and the Code node in n8n? +
The Set node is a visual, no-code way to add, modify, or remove fields from your data items. You map input fields to output fields using a point-and-click interface — no programming required. The Code node lets you write custom JavaScript or Python to process data with full programming flexibility. Use the Set node for simple field mapping and renaming. Use the Code node when you need loops, conditionals, mathematical calculations, string manipulation, or logic that can't be expressed in the Set node's UI.
When should I use the IF node vs the Switch node in n8n? +
Use the IF node when you have a binary decision — the data either meets a condition (true output) or doesn't (false output). For example: "Is the email domain @gmail.com? Yes → path A, No → path B." Use the Switch node when you need to route data to one of multiple different paths based on a value. For example: routing based on a status field that could be "new", "pending", "approved", or "rejected" — each value goes to a different branch. The Switch node is essentially a multi-output IF node.
What does the SplitInBatches node do in n8n and when do I need it? +
The SplitInBatches node processes a large array of items in smaller chunks (batches). You need it when: (1) you're hitting API rate limits — by processing 10 items at a time with a Wait node between batches, you avoid exceeding limits; (2) you have hundreds or thousands of items to process and want to avoid memory issues; (3) you need to add delays between API calls. Without SplitInBatches, n8n processes all items simultaneously, which can overwhelm rate-limited APIs or cause memory problems with very large datasets.
How does the HTTP Request node work in n8n? +
The HTTP Request node makes HTTP calls to any REST API or web endpoint. You configure the URL, method (GET, POST, PUT, DELETE, PATCH), headers, query parameters, and request body. It supports all common authentication methods: API Key (header or query param), Bearer Token, Basic Auth, OAuth2, and Digest Auth. The response is automatically parsed — JSON responses become structured data items you can use in subsequent nodes. This is the most versatile node in n8n, as it lets you connect to virtually any API that isn't covered by a dedicated integration node.