Notice: This page requires JavaScript to function properly.
Please enable JavaScript in your browser settings or update your browser.
Aprende Passing and Transforming Data | Introduction to n8n
n8n Overview

Passing and Transforming Data

Desliza para mostrar el menú

Understanding how data moves between nodes is essential to building effective workflows in n8n. When you connect nodes, the output from one node becomes the input for the next. Data flows in a structured format—typically as an array of items, where each item is a JavaScript object containing fields and values. This allows you to process, transform, and route information as your workflow progresses.

Below is a simple data flow diagram to illustrate how data is passed from one node to another:

[Trigger Node] ---> [Set Node] ---> [Merge Node] ---> [Next Node]

In this diagram, the trigger node starts the workflow and outputs data. The set node can modify or add fields, and the merge node combines data from multiple sources before sending it forward. Each node receives the data array, processes it, and passes the modified array to the next node. This consistent structure makes it easy to chain together complex operations.

Set Node
expand arrow

Use this node to add new fields, remove fields, or modify existing data. For instance, you might want to rename a field or add a timestamp before sending data to another service;

Merge Node
expand arrow

This node allows you to combine data from two different branches in your workflow. It is useful when you need to enrich data from one source with details from another, such as adding user information to an order record;

SplitInBatches Node
expand arrow

Use this node to process large arrays of data in smaller, manageable chunks. This is especially helpful when working with services that have rate limits or when you want to avoid timeouts by processing items in batches.

Note
Note

A common pitfall when transforming data is assuming that all items have the same structure or that required fields always exist. This can lead to errors if a node tries to access a missing field. To avoid this, always check your data structure and use conditional logic where necessary. Another issue is overwriting important fields unintentionally when using the set node. Review your field names carefully to prevent accidental data loss.

data-transformation-workflow.json

data-transformation-workflow.json

¿Todo estuvo claro?

¿Cómo podemos mejorarlo?

¡Gracias por tus comentarios!

Sección 1. Capítulo 6

Pregunte a AI

expand

Pregunte a AI

ChatGPT

Pregunte lo que quiera o pruebe una de las preguntas sugeridas para comenzar nuestra charla

Sección 1. Capítulo 6
some-alt