Home
...
Triggers
t Google Storage

t Google Storage

Available triggers

The Google Storage component enables integration with Google Cloud Storage service, facilitating the monitoring and retrieval of objects stored in Google Cloud buckets. As a trigger, it can be configured to detect and consume files from buckets, monitor changes, and process objects automatically. The integration supports reading different file types, as well as filtering by object name and continuous processing of new items added to the bucket.

URI Syntax: google-storage:bucketName

Main Fields

Path parameters

Name	Description	Default	Type
`bucketName` (common)	(required) Bucket name or ARN.	—	String

Query parameters

Name	Description	Default	Type
`serviceAccountKey` (common)	The service account key that can be used as a credential for the Storage client. Can be loaded from classpath, file, or URL.	—	String

Example

IMPORTANT
Before running the integration flow, import the Google Cloud service account key to a config map. This key will be used as a resource in the integration:
The "key.json" file contains the service account credentials in JSON format. In Integrations, this key will be configured as a Resource file.
Read more about Resources files.

The flow continuously monitors the sensedia-test-bucket bucket. The credentials are in the key.json resource.

When it detects files in the bucket, the content and name are displayed in the log and then automatically deleted (default behavior of the deleteAfterRead=true parameter).

Result

NOTE

Each flow execution makes the file content available in the message body (${body}) and the object metadata in the headers (${headers}), which can be manipulated according to the integration needs.

By default, files are deleted from the bucket after processing, as the deleteAfterRead parameter defaults to true. To keep files in the bucket, configure deleteAfterRead: false in the parameters.

How happy are you with this page?

t Google Pub/Sub

t Mail