I am seeing that in some workflows I developed are been failing and when I review it could appear that in some if node when it take the else path, the next node not received input data … I am getting crazy or loosing my mind but when I put another IF node in the else path and this last node go by true path, the issue is solved… I mean, when IF validate something like, If a != b then … , else … (this part no deliver input data to the following node)… But if I put another if the issue is fixed: If a != b then … else if a == b then (then issue is fixed)
@Adan_Palma , you are referencing the previous nodes with $('<node_name>).item.json... syntax. That implies automatic inference of the paired items. This is fine until the pairing is broken which could be caused by the branching nodes such as “IF” and “Switch” or custom node, for example.
In the later case, n8n needs some help from you to know what item you are referring to. If the output of the refered node has only one item, replace .item. with .first(<output_branch_index>).. By default, “<output_branch_index>” refers to the first output, which implies index 0 and could be omitted.
For example, it you reference the “IF”'s false output, you would refer to it as $('<node_name>).first(1).json.... See Output of other nodes | n8n Docs for more details.