Google Cloud Storage Enhanced icon

Google Cloud Storage Enhanced

Use the Google Cloud Storage API

Overview

The Google Cloud Storage Enhanced node allows you to interact with Google Cloud Storage directly from your n8n workflows. It supports operations on both buckets and objects, such as creating, updating, retrieving, and deleting them. This node is beneficial for automating file storage tasks, managing backups, or integrating cloud storage into data pipelines.

Practical examples:

  • Automatically upload files to a bucket when new data arrives.
  • List all objects in a bucket for further processing.
  • Delete outdated files from storage as part of a cleanup workflow.

Properties

Name Type Meaning
Authentication options Select the authentication method: Service Account or OAuth2. Determines credential type.

Note: The node also supports additional properties (such as "Resource", "Operation", "Bucket Name", etc.) depending on the selected resource and operation, but only "Authentication" was provided in your input.

Output

  • The node outputs a JSON object (or an array of JSON objects) representing the result of the performed operation.
  • If an error occurs and "Continue On Fail" is enabled, the output will include a JSON object with an error field containing the error message.
  • For object download operations, binary data may be included in the output, representing the downloaded file.

Dependencies

  • Google Cloud Storage API: Requires access to a Google Cloud project with the appropriate permissions.
  • Credentials:
    • Service Account: Requires a service account key with access to Google Cloud Storage.
    • OAuth2: Requires OAuth2 credentials configured for Google Cloud Storage access.
  • n8n Configuration: Credentials must be set up in n8n under the names googleApi (for Service Account) or googleCloudStorageOAuth2Api (for OAuth2).

Troubleshooting

Common Issues:

  • Invalid Credentials: Ensure that the correct authentication method and credentials are used.
  • Insufficient Permissions: The service account or OAuth2 user must have the necessary roles (e.g., Storage Admin).
  • Incorrect Parameters: Double-check required fields like bucket name or object name.

Error Messages:

  • "error": "Request had insufficient authentication scopes"
    Resolution: Update your credentials to include the required scopes.
  • "error": "Not Found"
    Resolution: Verify that the specified bucket or object exists.
  • "error": "Permission denied"
    Resolution: Check IAM permissions for the authenticated user/service account.

Links and References

Discussion