I’m requesting the creation of official FileRun nodes for n8n. These nodes should support core FileRun file-management functions such as uploading files, downloading files, listing directories, moving/copying files, managing metadata, sharing links, and handling authentication through the FileRun API. The goal is to allow n8n workflows to interact directly with FileRun without relying on manual HTTP Request configurations.
The idea is:
I’m requesting the creation of official FileRun nodes for n8n. These nodes should support core FileRun file-management functions such as uploading files, downloading files, listing directories, moving/copying files, managing metadata, sharing links, and handling authentication through the FileRun API. The goal is to allow n8n workflows to interact directly with FileRun without relying on manual HTTP Request configurations.
My use case:
FileRun is widely used as a lightweight file management and secure sharing platform, especially in teams that need an on-prem or self-hosted alternative to cloud file storage. Integrating FileRun with n8n would allow workflows such as:
Automatically uploading output files from various workflows (PDF generation, reports, backups, logs).
Syncing files between FileRun and other storage systems (S3, Azure Files, Google Drive, internal NAS).
Auto-organizing uploaded files using rules, tags, folder structures, and metadata.
Creating automated share links and distributing them through Slack, Teams, email, or ticketing systems.
Triggering downstream automation whenever new files arrive in FileRun.
Using FileRun as a central repository for AI workflows, document processing, and ETL operations.
These use cases currently require manual HTTP nodes, which is error-prone, time-consuming, and not user-friendly for non-technical users.
I think it would be beneficial to add this because:
Official FileRun nodes would significantly reduce integration complexity and make automation more accessible for users who rely on FileRun as their primary file repository. FileRun has a well-defined, documented API that supports a broad range of operations, making it straightforward to build robust nodes.
Adding FileRun would also expand n8n’s ecosystem to cover another large segment of self-hosted file-management users—similar to how n8n already supports Nextcloud, S3, and other storage platforms. There is strong community overlap between users who self-host n8n and those using FileRun.
Any resources to support this?
- Official FileRun API documentation:
The API - FileRun Documentation - Additional technical references:
FileRun Developer Guide
404 Not Found - FileRun Documentation
Are you willing to work on this?
I’m happy to help test the nodes, provide feedback, and validate functionality in real-world workflows. I will also upvote this request and encourage others to support it. However, I am not currently able to develop the node myself. The main developer who built this is Vlad Roman - EMAIL: [email protected]