So when i try to send a binary file via a webhook the binary file is not getting read, I have not changed anything regarding my workflow or the type of information that gets send. What can be the problem? I am on 2.13.4. I believe the problem is that binary files are not getting read properly.
Can you please check if the RAW Body option is enabled. You can try turn it OFF to check if that works. Or In filesystem binary sotrage mode N8N_DEFAULT_BINARY_DATA_MODE=filesystem when a binary file arrives via Webhook, n8n attempts to rename or move it from a temp folder to the execution folder for each node that references it. Only the first rename will be successful , rest of the attempts will show No such file or Directory. Temporarily if you are on selfhosted docker, switch back to in-memory mode to confirm, if this is the case. Keep me posted what you find.
Thanks for the reply, RAW body is off. I am on n8n cloud, so i cant change the n8n filesystem unfortunatly. Do you have any idea what other problems it could be?Probably one other area to check. There is a chance webhook can fail to include the binary property in its output. The body fields will parse fine but the file will be completly missing. This will cause the downstreame nodes to error with No Binary File Found. Please check, i cant think of other options for now.
welcome to the n8n community @Evert
On n8n Cloud 2.13.4, check your webhook Content-Type header (needs multipart/form-data for binaries). Also verify binary.propertyName matches your file field name from sender. Test with Postman first.
It looks like the file isn’t being sent or read properly, even though you didn’t change anything. This can happen if the content type is wrong, the file isn’t in the right format, or there’s a small issue in the latest version. Sometimes it’s also because the file is too large or the webhook is reading it differently now. You can try sending a smaller file, double-check the content type, or convert the file to Base64 and see if that works.