Best way to pass Trigger's binary data to HTTP Request after Switch?

Questions
,
1

Hi n8n community,

I have a workflow that starts with a trigger receiving a binary file (e.g., from a form). Later in the workflow, after a Switch node routes the execution based on some logic, I need to send that original binary file using an HTTP Request node (as form-data or binary body) to an external API.

I’m finding it difficult to reliably access the binary data from the trigger node at the input of the HTTP Request node after the Switch branch. Standard expressions referencing the trigger node’s binary data often result in ‘undefined’ or errors about missing binary files in the HTTP Request node’s input.

What is the most reliable and standard way in n8n (v1.83.2 Self Hosted) to ensure binary data from an early trigger node can be sent by an HTTP Request node that runs after a Switch node or other branching logic?

Any help or pointers would be greatly appreciated!

Thanks,
Mishel

Question - move binary file
Question - move binary file2229×1125 207 KB

2

The bare minimum would be to add a Merge node between AI and Switch. The Merge node would have input 1 from AI and input 2 from the earlier ocr http request. It’s ok that http request node will have two wires - to both ai and Merge.
Set merge mode to “combine by position”.

If this suggestion resolves your issue, please mark it as a :white_check_mark: Solution.

3

Hey olek,

Thanks for the quick reply.

I have another http request if the file is relevant i would need to pass different binary file again.

Any suggestions for this?

4

Not sure what your ask is.
Could you post your workflow using </> button here and describe your need using specific node names?

Also, is your initial question resolved or I misunderstood your objective?