Re-using binary data - Update?

[gleeballs]

Continuing the discussion from Re-using binary data:

@jan

However, we are rethinking binary data. We have wanted to change it for a while as it constantly causes confusion, and we would rather make it work like all other data in n8n. If it gets implemented as planned, something like the expression mentioned above would work.

Hi Jan,

Are there any updates to this or any announcements etc? Running into a few issues with binary data and it pulling through from previous nodes and wondered if anything had been implemented yet

[n8n]

It looks like your topic is missing some important information. Could you provide the following if applicable.

• n8n version:
• Database (default: SQLite):
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via (Docker, npm, n8n cloud, desktop app):
• Operating system:

[ihortom]

Hey @gleeballs , I don’t think any change since that time. What problem are you facing? There are a few techniques that could be applied depending on your use case.

For example, [onedrive via Graph HTTP] why binary don't upload if not exactly previous node? - #2 by ihortom.

[gleeballs]

the main ones I face are

1. getting binary data in an early node and then being able to use that several nodes down the workflow
2. how to reference it after and if / switch / loop nodes.

perhaps i just need to rethink the way i build workflows out and not get the binary data until just before i need it somehow