Create Bucket
Creates a new bucket in Google Cloud Storage.
Common Properties
- Name - The custom name of the node.
- Color - The custom color of the node.
- Delay Before (sec) - Waits in seconds before executing the node.
- Delay After (sec) - Waits in seconds after executing node.
- Continue On Error - Automation will continue regardless of any error. The default value is false.
info
If the ContinueOnError property is true, no error is caught when the project is executed, even if a Catch node is used.
Inputs
- GCS Client Id - The client identifier obtained from the Connect node.
- Project Id - The Google Cloud project ID where the bucket will be created.
- Bucket Name - The name for the new bucket to be created.
Options
- Labels - Key-value pairs to label the bucket for organizational purposes.
- Access Control Type - The access control type for the bucket:
- Uniform - Uniform access control for all objects in the bucket
- Fine-grained - Individual access control for each object in the bucket
- Storage Class - The storage class for the bucket:
- Standard - For frequently accessed data
- Nearline - For data accessed less than once per month
- Coldline - For data accessed less than once per quarter
- Archive - For data accessed less than once per year
How It Works
The Create Bucket node creates a new bucket in Google Cloud Storage. When executed, the node:
- Validates the provided inputs (GCS Client Id, Project Id, Bucket Name)
- Uses the existing storage client connection
- Configures bucket attributes including access control, storage class, and labels
- Creates the new bucket in the specified Google Cloud project
Requirements
- A valid GCS Client Id from a successful Connect node execution
- Valid Google Cloud Project Id
- Unique bucket name that follows Google Cloud Storage naming conventions
- Proper permissions to create buckets in the specified project
Error Handling
The node will return specific errors in the following cases:
- Empty or invalid GCS Client Id
- Empty or invalid Project Id
- Empty or invalid Bucket Name
- Bucket name that already exists
- Invalid bucket naming conventions
- Insufficient permissions to create buckets
- Google Cloud Storage service errors
Usage Notes
- Bucket names must be globally unique across all of Google Cloud Storage
- Bucket names must follow specific naming rules (lowercase letters, numbers, dashes, and dots)
- The Access Control Type determines how permissions are managed for objects in the bucket
- Storage Class affects pricing and data retrieval performance
- Labels can be used for cost allocation and organization
- Once created, some bucket properties like location cannot be changed
- The bucket will be created in the default location unless specified otherwise in the project settings
- Make sure the authenticated account has the necessary permissions to create buckets