• Custom n8n node
  • Files & Storage
  • AI-agent tool

SeaweedFS storage

Store and retrieve files in SeaweedFS (S3-compatible) object storage.

How it works in practice

Documents kept safely in storage you own

How we apply it

We use it as the document store behind our automations: downloaded bank statements, split invoices and generated reports are archived in self-hosted storage, kept per customer.

This node manages buckets and files on a SeaweedFS S3 endpoint directly from n8n: create, list and delete buckets, upload and download binary data, list objects by prefix, read metadata and copy objects within or between buckets. It speaks plain S3, so it also fits other S3-compatible stores that you point it at with a custom endpoint.

We wanted a lightweight, self-hosted document store for workflow artefacts that does not tie a client to a cloud vendor: downloaded statements, split invoices, generated reports. Handing a file between workflows through a bucket also keeps large binaries out of execution data. The node signs requests with its own AWS Signature V2 implementation, and the credential has a test button in n8n.

In practice it archives downloaded bank statements and generated reports into an internal bucket, keeps a document set per customer and lists it by prefix, and moves processed files from an inbox bucket to an archive bucket. It is in 11 production workflows, mostly upload and download.

Limits: only Signature V2 is implemented, so some modern S3 servers that require V4 will not work. There are no presigned URLs and no multipart upload.

For your technical team: it installs from npm as

n8n-nodes-kt-seaweedfs

What it means for you

  • No lock-in to a cloud vendor

  • Big files do not weigh the automation down

  • Every document has one clear home

Want SeaweedFS storage in your n8n?

Tell us what the workflow has to do and what it connects to. We will say whether this node covers it as it stands, what we would add, and when a different approach is the better one.