Google Cloud Storage n8n integrationAutomate Google Cloud Storage with n8n.

Creates a bucket in the Google Cloud project you name. That bucket becomes the destination every object operation later points at.

• Project ID: the project the bucket belongs to, taken from the project selector in the Google Cloud Console.
• Bucket Name: the name of the new bucket, reused as written in every object operation that follows.
• Location: where the bucket's data sits, one of the optional parameters and easier to set now than to revisit.
• Predefined ACL: a ready-made access rule for the bucket itself, from private to publicRead.

Removes a bucket from the project. The wording matters: the bucket has to be empty, so an object.getAll and object.delete pass normally runs first.

• Bucket Name: the bucket to remove, spelled exactly as it was created.
• Metageneration Match: a filter that lets the call go through only if the bucket's metageneration value matches the one you send, which stops a delete that fires against a bucket someone edited in between.

Returns the metadata of one bucket. Nothing is written, so it is the safe way to check a bucket's configuration before a workflow acts on it.

• Bucket Name: the bucket to read, often carried from an earlier node with an expression such as {{ $json.field }}.
• Projection: full returns All Properties, noAcl returns the metadata without the access control entries, which keeps the item lighter for the nodes downstream.

Lists the buckets of a project, one item per bucket, ready to loop over.

• Project ID: the project to inventory, the same identifier used when creating a bucket.
• Prefix: filters on bucket names, so a naming convention like a client code in front gives you that client's buckets and nothing else.
• Return All: on, n8n walks the API pages until every bucket has come back; off, it stops at the limit you set.

Changes the settings of an existing bucket without touching a single file inside it.

• Bucket Name: the bucket to modify.
• Labels: user provided labels in key and value pairs, the usual way to tag a bucket with an owner, an environment or a cost centre.
• Versioning: the bucket's versioning configuration, sent as JSON.

Writes a file into a bucket. It takes either a binary file already in the run or plain text composed in n8n.

• Bucket Name and Object Name: the destination and the file name, often built with an expression like {{ $json.field }}.
• Use Input Binary Field: turn it on when the content comes from a binary field, then name that field in Input Binary Field.
• File Content: the text to upload when there is no binary field, such as a CSV built in the workflow.
• Content Type: one of the Create Fields, it tells a browser what the file is.

Erases one file. Point it at a bucket and a name, and that entry is gone.

• Bucket Name: the bucket holding the file.
• Object Name: the exact name of the object, including any prefix that acts as a folder in the path.
• Generation: selects a specific revision of the chosen object, useful when a bucket keeps several versions of the same name.

Fetches one object, and you decide whether you want the file itself or the information about it.

• Bucket Name and Object Name: the file to read.
• Return Data: json gives the Metadata, media gives the Object Data, which is the file content.
• Put Output File in Field: the name of the output binary field the file lands in, so the next node can attach or transform it.

Lists what a bucket contains, as one item per object.

• Bucket Name: the bucket to browse.
• Prefix: keeps only the names that start with this value, which is how you list a single folder.
• Return All and Limit: all the pages, or a maximum number of results per run.
• Delimiter: returns results in a directory-like mode, using this value as the separator.

Rewrites the information attached to a file that is already stored. The bytes stay where they are.

• Bucket Name and Object Name: the object to edit.
• Cache Control: one of the Update Fields, it governs how the file is cached when it is served.
• Content Disposition: another Update Field, it drives how a browser presents the file.
• Metadata: custom JSON you attach to the object, the place to keep an internal reference.