n8n Advanced Course (1/8) - Working with complex data flows

Summary

In this first video of the Niden advanced course, viewers learn how to master workflow creation by understanding node execution order, branching, merging, and looping. The tutorial explains how branches execute top-to-bottom and left-to-right, how to split data using If and Switch nodes, and how to merge branches effectively with options like append, choose, and combine. It also covers looping over items for large datasets or API rate limits and demonstrates data enrichment by merging contact information with company data. Through practical examples, users gain hands-on knowledge to build efficient, organized, and advanced workflows in Niden.

Takeaways

• 😀 In Niden workflows, nodes execute branch by branch, completing one branch before starting the next.
• 😀 Branch execution order follows top-to-bottom and left-to-right positioning on the canvas.
• 😀 The If Node splits data into two branches based on a true/false condition.
• 😀 The Switch Node can split data into multiple branches and assign a fallback branch.
• 😀 Multiple outputs from a single node send all items down each branch, following execution order.
• 😀 The Merge Node combines data from two branches with options: Append, Choose, or Combine.
• 😀 Append merges all items sequentially, Choose selects specific items, and Combine merges by field or position.
• 😀 Loop Over Items or Split in Batches nodes allow individual or batch processing, useful for API limits or multi-item nodes.
• 😀 Data enrichment can be achieved by merging branches using a common key, such as a domain extracted from an email.
• 😀 For workflows with dependent branches, it’s recommended to merge branches rather than change execution order.
• 😀 Green numbers next to nodes indicate loop iteration, and output items can be tracked per iteration.
• 😀 Understanding node execution, branching, merging, and looping is essential for advanced workflow building in Niden.

Q & A

What is the default execution order for nodes in a Niden workflow?

The default execution order is top-to-bottom and left-to-right. Each branch executes fully before moving to the next branch.

Can the node execution order be changed in Niden workflows?

Yes, it can be changed on a workflow basis, but it is not recommended. Instead, dependent branches should be merged to maintain proper execution.

What is the purpose of the If node in a workflow?

The If node splits input items into two distinct branches based on whether a condition is true or false.

How does the Switch node differ from the If node?

The Switch node can create multiple (n) branches, including a fallback branch, and distributes items among all branches, whereas the If node only splits into two branches.

What are the three merge options provided by the Merge node?

The Merge node provides three options: Append (concatenate items from both branches), Choose (select items from one branch), and Combine (merge items by field positions or all combinations, similar to SQL joins).

How does the Loop over Items node help in workflows?

The Loop over Items node allows processing of items individually or in batches. It is especially useful for nodes that output multiple items or when managing API rate limits.

How can merging by field be used for data enrichment?

Merging by field allows combining data from two branches using a key field (like domain) to match items. This enables enrichment of items, such as adding company information to contact data.

Why might merging by position be used instead of merging by field?

Merging by position can be useful for workflows that rely on sequential outputs, such as enriching items via API calls, where each input corresponds to an output in order.

How can multiple outputs from a single node be used?

Multiple outputs from a single node can create parallel branches, allowing execution of different sets of actions from the same source node.

How does the workflow indicate the iteration number when using Loop over Items?

Each node in the loop shows a green number next to the green check mark indicating the current iteration number for that loop.

What is the recommended approach when building workflows with branches that depend on each other?

It is recommended to merge branches before using their data rather than changing the node execution order, ensuring proper data flow and workflow integrity.

How can Loop over Items help with API rate limits?

By splitting input items into batches, the Loop over Items node can control the timing of API calls, preventing exceeding limits by spreading requests over time.