Skip to content

docs: Document Read/Write Files node availability on n8n Cloud (DOC-854)#4688

Merged
its-imad merged 2 commits into
mainfrom
DOC-854/readwrite-files-available-on-cloud
May 22, 2026
Merged

docs: Document Read/Write Files node availability on n8n Cloud (DOC-854)#4688
its-imad merged 2 commits into
mainfrom
DOC-854/readwrite-files-available-on-cloud

Conversation

@its-imad
Copy link
Copy Markdown
Collaborator

Summary

  • Remove the outdated "Self-hosted n8n only" admonition: the Read/Write Files from Disk node is now available on n8n Cloud.
  • Expand the File locations section with deployment-specific guidance:
    • Cloud: file access is restricted to /home/node/, filesystem is ephemeral, with a pointer to cloud-storage nodes for persistent file handling.
    • Self-hosted: notes on N8N_RESTRICT_FILE_ACCESS_TO and the upcoming n8n 2.0 default of ~/.n8n-files.
  • Add a note flagging that the node's default UI field placeholders aren't applicable on Cloud.

Linear: DOC-854

Verification

Tested on a real Cloud workspace before writing:

  • Write/Read round-trip succeeds for paths under /home/node/ and relative paths.
  • Write to /tmp/, /data/ returns an access error (Cloud uses N8N_RESTRICT_FILE_ACCESS_TO=/home/node).

Test plan

  • Local preview renders both subsections without broken links.
  • Vale: no new warnings introduced (two pre-existing Vale.Spelling errors on Picomatch's/globbing in unchanged content).
  • Cloud-team review of the Cloud-specific guidance (separate Slack ping for misleading placeholders + error message — likely a separate engineering ticket).

Follow-ups (not in this PR)

  • Engineering: surface a clearer "path not allowed" error on Cloud (today it reads "The file or directory does not exist", which is misleading).
  • Engineering: deployment-aware UI placeholders for the node's path fields.

The node is now available on n8n Cloud. Remove the outdated 'self-hosted
only' note and expand the File locations section with deployment-specific
guidance: Cloud's /home/node/ allow-list, filesystem ephemerality and
recommended cloud-storage alternatives, plus self-hosted notes on
N8N_RESTRICT_FILE_ACCESS_TO and the upcoming n8n 2.0 default.
@its-imad its-imad added the author:doc-team Contribution from n8n docs team. label May 21, 2026
@netlify
Copy link
Copy Markdown

netlify Bot commented May 21, 2026

Deploy Preview for n8n-docs ready!

Name Link
🔨 Latest commit a4b2fa4
🔍 Latest deploy log https://app.netlify.com/projects/n8n-docs/deploys/6a1045832a7e850008ba0ba4
😎 Deploy Preview https://deploy-preview-4688--n8n-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Copy link
Copy Markdown
Contributor

@cubic-dev-ai cubic-dev-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 1 file

Architecture diagram
sequenceDiagram
    participant Cloud as n8n Cloud Instance
    participant Filesystem as Cloud Filesystem (/home/node/)
    participant Node as Read/Write Files Node
    participant User as User (Workflow Editor)
    participant Storage as Cloud Storage Node (AWS S3, Google Drive, FTP)

    Note over Cloud,Node: Cloud Deployment – File Access Flow

    User->>Node: Configure File(s) Selector or File Path
    alt Cloud deployment
        Node->>Filesystem: Access path under /home/node/
        alt Path is in /home/node/
            Filesystem-->>Node: Read/Write success
            Node-->>User: Return file data or confirm write
        else Path is outside /home/node/ (e.g., /tmp/, /data/)
            Filesystem-->>Node: Access error (misleading "File not found")
            Node-->>User: Return error
        end
    else Self-hosted deployment
        Note over Node,User: N8N_RESTRICT_FILE_ACCESS_TO controls allowed paths
        Node->>Filesystem: Access configured or unrestricted path
        Filesystem-->>Node: Read/Write result
        Node-->>User: Return file data or error
    end

    Note over User,Storage: Cloud Ephemeral Filesystem – Persistent Storage Alternative
    User->>Node: Write file to /home/node/
    Node->>Filesystem: Write data (ephemeral)
    Filesystem-->>Node: Success
    Node-->>User: Confirm write
    Note over Filesystem: File may vanish on restart/redeploy
    User->>Storage: Use cloud storage node for persistent files
    Storage-->>User: Reliable storage outside ephemeral filesystem
Loading

Re-trigger cubic

@cloudflare-workers-and-pages
Copy link
Copy Markdown

cloudflare-workers-and-pages Bot commented May 21, 2026

Deploying n8n-docs with  Cloudflare Pages  Cloudflare Pages

Latest commit: a4b2fa4
Status: ✅  Deploy successful!
Preview URL: https://a085295d.n8n-docs-d9c.pages.dev
Branch Preview URL: https://doc-854-readwrite-files-avai.n8n-docs-d9c.pages.dev

View logs

@its-imad
Copy link
Copy Markdown
Collaborator Author

Opened two follow-up Nodes issues to track the product-side changes separately from this docs PR:

NODE-5113 for the misleading Cloud error message when the path is outside the allowed paths

NODE-5114 for the Cloud-incompatible default placeholders in the node UI

Keeping this PR focused on documenting current behavior and constraints.

@its-imad its-imad self-assigned this May 21, 2026
@github-actions
Copy link
Copy Markdown

No description provided.

@its-imad its-imad merged commit 742395c into main May 22, 2026
9 checks passed
@its-imad its-imad deleted the DOC-854/readwrite-files-available-on-cloud branch May 22, 2026 12:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author:doc-team Contribution from n8n docs team.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants