Hi, I’m having an issue with my n8n workflow. My Webhook node receives a PNG image and I want to send it to an API via the HTTP Request node. However, I get the following errors:
Cannot read properties of undefined (reading ‘value’)
How can I ensure that the binary file from the Webhook node is correctly passed to the HTTP Request node so that this error is resolved?
Thank you!
Hey @nina1 !welcome to n8n.
Does this image helps you ?
The HTTP Request node expects the correct binary property name in the “Input Data Field Name” (or “Binary Property” in some versions). By default, when a file is uploaded via a Webhook node, the binary property is often named data.
Set Send Body to true.
Choose Body Content Type as n8n Binary File (or multipart/form-data if the API expects form data).
In Input Data Field Name, enter the exact name of the binary property (e.g., data the orange text from output).
Do not use an expression or add extra text—just the property name as it appears in the Webhook node output.
Cheers!
Hi! @Parintele_Damaskin Thanks for the image. Yes, I checked the field names several times and made sure they match everywhere, but I still keep getting the same error.
If you have any nodes between the Webhook and HTTP Request nodes (like Set, Merge, or Code), these can strip or fail to propagate the binary data unless configured to include it. For example, in a Set node, you must enable “Include Binary Data” or “Include Other Input Fields” to ensure the binary data is passed along…
Can you share the part of the workflow or images ?
Can’t see the Webhook data as well…
If your webhook sends a data URL like data:image/png;base64,…, first strip the prefix and convert to a proper binary file (e.g. with Convert to File), passing only the raw base64 string…
Pin the data in that execution, and share the workflow here (CTRL+A select, copy and paste the json).
Or I need images to see the output of Webhook and how you configure the HTTP node.
Cheers!
Ok, did you wrote data or data0 in your HTTP node Input Data Field Name?
According to your image, you need to write exactly the orange text (in your case data0) into that field of HTTP node.
What I understood is that n8n automatically renumbers the files (like data0, data1…) and after any change, the number might change again. To keep it fixed, you need to pin the file first and then set the HTTP node to use that fixed number.I think…
When a node outputs binary, it chooses a fixsed property name (for egxample data) and sticks with it unless:
You expllicitly channge it (e.g. via Code node / Convert to File / Extract From File), or
A node is configured to output into a different field name
Some nodes (like Webhook v2) append an index when multiple files come in the same request (e.g. data0, data1), but that’s defined by the node and the HTTP request, not by “renumbering after any change”…
I’m not entirely sure why this error got resolved now, but it’s probably because the file was pinned or the node correctly recognized the field name, which fixed the issue.
It depends on the version of n8n and nodes , but I think the binary can have data0 as default when is single file, my version has simple data when 1 item, and data_0 when there are more.
Glad that your issue was solved !
Cheers!
Thank you for your help
