Google Cloud Storage Enhanced icon

Google Cloud Storage Enhanced

Use the Google Cloud Storage API

Actions10

Bucket → Create

AI-generated

Overview

The node "Google Cloud Storage Enhanced" provides enhanced integration with Google Cloud Storage, allowing users to manage buckets and objects programmatically within n8n workflows. Specifically, the Bucket - Create operation enables users to create new storage buckets in a specified Google Cloud project with detailed configuration options.

This node is beneficial for automating cloud storage management tasks such as provisioning new buckets with custom access controls, lifecycle policies, encryption settings, and more. For example, it can be used to automatically create buckets for new projects or environments, enforce organizational policies on bucket configurations, or prepare buckets for hosting static websites.

Properties

Name Meaning
Authentication Method of authentication to use: either Service Account or OAuth2.
Project ID The Google Cloud project identifier under which the bucket will be created.
Bucket Name The name of the bucket to create.
Projection Controls the set of properties returned by the API. Options: All Properties (full) or No ACL (noAcl).
Predefined Access Control Collection of predefined access control options applied during bucket creation:
- Predefined ACL: e.g., Authenticated Read, Private, Project Private, Public Read, Public Read/Write.
- Predefined Default Object ACL: e.g., Authenticated Read, Bucket Owner Full Control, Private, etc.
Additional Parameters Collection of optional metadata parameters to customize the bucket:
- Access Control (ACL)
- Billing configuration
- CORS settings
- Custom placement config
- Data locations
- Default event-based hold
- Default object ACL
- Encryption config
- IAM configuration
- Labels (key/value pairs)
- Lifecycle rules
- Location (default "US")
- Logging config
- Retention policy
- Recovery Point Objective (RPO)
- Storage class (default "STANDARD")
- Versioning config
- Website config
Enable Object Retention Boolean flag to permanently enable object retention on the bucket, preventing deletion or modification of objects subject to retention policies.

Output

The output JSON contains the full response from the Google Cloud Storage API representing the newly created bucket resource. This includes all configured properties such as bucket name, location, storage class, access controls, labels, lifecycle rules, and other metadata.

If the operation succeeds, the output JSON reflects the current state of the bucket as stored in Google Cloud Storage.

The node does not output binary data for this operation.

Dependencies

  • Requires valid Google Cloud credentials, either via a Service Account or OAuth2 authentication method.
  • The node uses Google Cloud Storage REST API endpoints; thus, network connectivity to Google APIs is required.
  • Proper permissions are needed on the provided project and credentials to create buckets.
  • No additional environment variables are explicitly required beyond standard n8n credential setup.

Troubleshooting

  • Common Issues:

    • Insufficient permissions: The authenticated user or service account must have the necessary roles to create buckets in the specified project.
    • Invalid bucket name: Bucket names must follow Google Cloud Storage naming conventions (e.g., globally unique, no uppercase letters).
    • Misconfigured parameters: Providing invalid JSON or unsupported values in additional parameters may cause API errors.
    • Network or API quota limits: Temporary failures due to network issues or exceeding Google Cloud API quotas.

  • Error Messages:

    • "Permission denied": Check that the credentials have the correct IAM roles for bucket creation.
    • "Invalid bucket name": Verify the bucket name meets Google Cloud Storage naming rules.
    • "Bad Request" or validation errors: Review the additional parameters for correctness and supported formats.
    • "Quota exceeded": Monitor and adjust API usage or request quota increases in Google Cloud Console.

To resolve errors, verify credentials, validate input parameters, and ensure compliance with Google Cloud Storage API requirements.

Links and References

Discussion