Hi everyone,
I’m running into a persistent ENOENT error on a Webhook node when handling multipart uploads, and I’m trying to understand if this is a known limitation or if I’m missing something.
Setup
n8n version: 2.4.8 (self-hosted)
OS: Linux
Use case: SAP sends documents via CMIS Browser Binding (createDocument)
This results in a multipart/form-data HTTP request (cannot be changed on the SAP side)
Files are usually ~5–10 MB
The request fails directly in the Webhook node, before any workflow logic runs
Stack trace excerpt:handleFormData
BinaryDataService.copyBinaryFile
FileSystemManager.copyByFilePath
lstat ‘/tmp/…’
So n8n clearly goes through handleFormData, writes a temp file, and then fails when trying to access it.
What we already tried
We already configured binary filesystem storage and restarted n8n.
Additionally, we set a fixed temp directory.
The directory exists, is writable, and persistent.
However, the error still references /tmp/…, which suggests that the Webhook/multipart handling process is still using /tmp and not the configured TMPDIR.
Share the output returned by the last node
ENOENT: no such file or directory, lstat ‘/tmp/…’