Skip to main content

Read Object

Reads the content of an object (file) from a Google Cloud Storage bucket.

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.
  • Bucket Name - The name of the bucket containing the object to read.
  • Object Name - The name of the object (file) to read.

Output​

  • Content - The content of the object as a string.

How It Works​

The Read Object node retrieves the content of an object (file) from a Google Cloud Storage bucket. When executed, the node:

  1. Validates the provided inputs (GCS Client Id, Bucket Name, Object Name)
  2. Uses the existing storage client connection
  3. Reads the entire content of the specified object
  4. Returns the content as a string

Requirements​

  • A valid GCS Client Id from a successful Connect node execution
  • Valid bucket name that exists in Google Cloud Storage
  • Valid object name that exists in the specified bucket
  • Proper permissions to read objects in the specified bucket

Error Handling​

The node will return specific errors in the following cases:

  • Empty or invalid GCS Client Id
  • Empty or invalid Bucket Name
  • Empty or invalid Object Name
  • Bucket does not exist
  • Object does not exist
  • Insufficient permissions to read the object
  • Google Cloud Storage service errors
  • Object is too large to read into memory

Usage Notes​

  • The output Content is the raw content of the file as a string
  • For binary files, the content will be read as-is and may not be human-readable
  • Large files may consume significant memory when read
  • This node is best suited for text files, configuration files, or small binary files
  • For large binary files, consider using other methods or streaming approaches
  • Object names can include folder-like paths (e.g., "folder/subfolder/file.txt")
  • Make sure the authenticated account has the necessary permissions to read objects
  • The operation reads the entire file content at once