Hi everyone, I’m experiencing an odd issue with the Read/Write Files from Disk node in n8n. Here’s the situation:
When I test the workflow using “Execute Node” in the editor, everything runs perfectly. The node reads files as expected.
However, when I activate the workflow and use the production webhook URL, the Read/Write Files from Disk node fails to do its job. Everything else in the workflow (like other nodes or steps) works fine, but this specific node fails or returns no data.
Would you mind doing ctl a, ctl c on your entire workflow. Creating a new forums reply, click ‘</>’ and paste the copied workflow into the field that appears?
So we can see more context.
Could we see some error/output logs as well that help indicate the issue?
When running multiple n8n containers (Editor, Webhook, Workers) in a queue or high-availability setup, you must ensure that each container has access to the same files and folders. In particular, if you are using the “Read/Write Files” node, mount the same volume(s) with the same paths on all containers that need file access. This way, when a workflow is triggered and executed on different containers, the file paths will remain valid, and the files will be found consistently. Without this shared volume setup, “file not found” or missing binary data errors often appear.