Hey everyone, I’m running into a bit of a problem with binary data in my workflow. I have a node at the beginning that handles binary data, but when I try to pull it later in the workflow using the expression field, it’s not coming through as binary. I can call the node and get the data, but it’s not in the binary format like I need it to be. Has anyone faced something similar or have any ideas on how to pass the binary data correctly through the workflow? Any help would be awesome!
Hey, unfortunately n8n doesn’t handle binary data that well yet. I solved a similar issue recently by saving the binary data to disk using Read/Write files from disk node, and then later reading it with the same node. Maybe this approach works for your workflow too?
An alternative to saving and then re-reading the file back described above is merging your node at the beginning with the one where you need the binary. Merge node will allow you to bring the binary to the place where you need it. It looks sort of ugly, but it works.
Here is a quick example:
3 Likes