Binary Data Upload with HTTP-Request node causes error: ENOENT: no such file or directory ... .metadata'

Questions
1

Hi,
I’m using n8n 1.44.1 with a postgres, separat worker and N8N_DEFAULT_BINARY_DATA_MODE=filesystem

I upload a file with a webhook and that data is shown as binary data in my workflow. I want to upload that file to an external endpoint using the “HTTP Request” node.
I want to upload it with the options “Send Body”: true
Body Content-Type: n8n Binary File
Input Data FIled Name: audio_file (the name of the binary file)

This is the error i get when doing this:
ENOENT: no such file or directory, open ‘/home/node/.n8n/binaryData/workflows/aqzw2KAKfcn2HoWE/executions/7636/binary_data/7807822e-11fd-444a-a933-9973f5c1387b.metadata’

To me it looks like as if it is going to look for a *.metadata file in the filesystem but this file is not created. I checked the documentation and I’m not clear it it should be created at all.

Please share your workflow

Is there another way to upload a binary data like in cur --data-binary ?

2

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:
3

Hi @Andreas_Pointner

did you also set the other variable N8N_BINARY_DATA_STORAGE_PATH to specify the path?

1 Like
4

Hi @ria,

no because I want to keep the data in the pre-configured path (default value).

The only solution I come up with is to use Body Content Type “Form-Data” and then include the “n8n Binary File” as only parameter.
But for me, it makes no sense to do it this way if the “Body Content Type” “n8n Binary File” is available.

Could the .metadata file be a relict from previous times?

5

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.