Connector library

Implemented source Data, Storage & Cloud APIs

Google Cloud Storage connector.

Retrieve bucket and object metadata, list objects by prefix and store a small JSON document without overwriting an existing live object using Cloud Storage JSON API v1.

Connector download

Download Google Cloud Storage

Versioned ZIP for your CXFabric tenant.

Use this connector in a flow

  1. Register the ZIP in your tenant, or add a new version if the connector is already installed.
  2. Create or select a credential if the action requires one.
  3. In a Draft flow, add an available action, choose its version, connect it, and map inputs.
  4. Test the step and flow; review output and failures before activation.

See readme.md in the ZIP for settings and limitations.

Version
v0.2.0.1 Choose version
Release
2026-10-03
Package
Implemented source
Schema credentials
Bearer token
Connection settings
API Base URL
Package size
8 KB
SHA-256
eaf0236d54bcd01892956f1a39bf90af794c4f76be45ffab32bd21e7f4299749

Version history

What's new

  1. v0.2.0.1Latest · 2026-10-03 · Implemented source

    Improves action labels, mapping hints and connection groups while retaining the existing parameter keys, types, defaults, credentials and result contracts.

  2. v0.2.0.0Earlier · 2026-10-03 · Implemented source

    Retrieve bucket and object metadata, list objects by prefix and store a small JSON document without overwriting an existing live object using Cloud Storage JSON API v1.

  3. v0.1.1.0Earlier · 2026-10-02 · Starter scaffold

    Retained immutable historical scaffold archive.

Included in this version

Included actions

Implemented in v0.2.0.1. Use a separate flow trigger; no webhook trigger is included.

Get bucket metadata

Retrieve bucket location, storage class and uniform-access settings.

Get object metadata

Retrieve metadata for the latest live object, or a selected generation.

List object metadata

Retrieve one page of object metadata matching an optional exact prefix.

Create JSON object

Store a small JSON document only when no live object with that name exists.

Vendor API

API and access

Implementation considerations
  • Confirm private networking, credentials, region, bucket/container scope, file-size limits, and lifecycle rules.
  • Keep object keys, versions, checksums, and destination paths in the workflow payload.
  • Use customer-owned storage for sensitive files and generated artifacts.

Support

Need help with Google Cloud Storage?

Tell us what you need to connect or change.