S3 n8n integrationAutomate S3 with n8n.

Creates a bucket on the storage backend behind the credential. It lands in the region set on that credential unless the call says otherwise.

• Name: the bucket name, often an expression such as {{ $json.account_slug }} when one workflow provisions storage per account.
• ACL: the canned ACL applied at creation, from Authenticated Read to Public Read Write. Private keeps the bucket closed to anonymous callers.
• Region: only needed when the bucket belongs somewhere other than the credential's region.

Hands a bucket name to the server and the bucket goes away. There is no confirmation step in the node, so whatever the expression resolves to is what gets destroyed.

• Name: the name of the bucket to delete, typed in or pulled from an earlier item with {{ $json.Name }}.

Returns the buckets the access key can see, one n8n item per bucket. Handy as a first step when a workflow has to know what already exists before it writes anything.

• Return All: on, n8n pages through the API until every bucket has come back; off, it stops at Limit.
• Limit: the ceiling on how many buckets come back when Return All is off.

Filters the keys inside one bucket on the server side, which is as close to a query as this node gets. The response carries the matching object keys rather than their contents.

• Bucket Name: the bucket being searched.
• Prefix: limits the answer to keys starting with this string, such as invoices/2025/.
• Delimiter: the character used to group keys, which is how a flat key space reads like folders.
• Start After: the key to start listing from, useful for resuming a long scan.

Duplicates an object from one location to another without the bytes travelling through n8n. Both paths start with a slash and the bucket name, then the object key.

• Source Path: bucket and key of the original, in the form /bucket/my-image.jpg.
• Destination Path: where the copy goes, same format, for example /bucket/my-second-image.jpg.
• Metadata Directive: Copy keeps the source metadata, Replace swaps in what the request provides.
• Storage Class: the class the copy is written to, from Standard down to Deep Archive.

Targets one object by its key and removes it from the bucket. On a versioned bucket the call can aim at a specific version instead of the current one.

• Bucket Name: the bucket holding the object.
• File Key: the full key of the object, folder prefix included.
• Version ID: an optional field in Options that points the deletion at one version.

Pulls one object out of the bucket and hands it to the rest of the workflow as binary data, ready for a node that emails, parses or re-uploads it.

• Bucket Name: where the object lives.
• File Key: the key to fetch, typically {{ $json.Key }} coming from Get many files.
• Put Output File in Field: the name of the output binary field the file is placed in, which the next node has to point at.

Walks the contents of a bucket and returns one item per object, with its key and metadata. Pair it with Download a file when the workflow needs the bytes too.

• Bucket Name: the bucket to list.
• Folder Key: narrows the listing to one folder instead of the whole bucket.
• Fetch Owner: off by default in the listing response, turn it on to get the owner field on each key.
• Return All: on, every object comes back; off, Limit caps the batch.

Writes a file into the bucket, either from a binary field produced upstream or from text typed into the node. This is the operation most S3 workflows are built around.

• Bucket Name: the destination bucket.
• File Name: the name the object takes, such as hello.txt.
• Input Binary Field: the input binary field holding the file, fed by Read/Write Files from Disk or HTTP Request.
• Binary File: off, the node uses File Content, the text you provide, instead of a binary field.
• ACL: on Wasabi, permissions must be set through this dropdown rather than the grant toggles.

Folders in S3 are a naming convention rather than real directories, and this operation writes the key that makes one show up in the console and in listings.

• Bucket Name: the bucket the folder goes into.
• Folder Name: the folder's own name, without the parent path.
• Parent Folder Key: the folder you want to create this one inside, which is how nesting is expressed.
• Storage Class: from Standard to Reduced Redundancy, depending on what gets stored there.

Removes a folder from a bucket by its key. Since folders are keys, the operation is about the structure rather than about the individual objects a workflow may have put there.

• Bucket Name: the bucket concerned.
• Folder Key: the key of the folder to drop, parent path included.

Lists the folders inside a bucket, one item each, so a workflow can loop over them without knowing the structure ahead of time.

• Bucket Name: the bucket to explore.
• Folder Key: restricts the answer to what sits under one folder.
• Return All: on, the node pages through everything; off, Limit sets the maximum returned.
• Fetch Owner: adds the owner field to each key in the result.