Skip to content

Google Cloud

Manage Google Cloud core services: list projects, run Compute Engine instances, manage Cloud Storage buckets and objects, deploy Cloud Functions, create Cloud SQL instances, and publish to Pub/Sub. There are no Firestore or BigQuery operations, and none that pull from or acknowledge a Pub/Sub subscription.
Nodes Google Cloud (actions), Google Cloud Trigger (polling)
Auth Service-account key (recommended), or Google sign-in
Availability Limited release. Not yet in the palette for customer workspaces.

Connecting

A service account lets workflows run without anyone's personal Google account. The credential dialog offers it first for Google Cloud.

  1. In Google Cloud Console, open IAM & Admin → Service Accounts and create a service account.
  2. Grant it the IAM roles the workflow needs, for example Storage Object Admin for uploads or Pub/Sub Publisher for publishing.
  3. Under Keys, add a JSON key and download it.
  4. In Flero, choose Service Account and paste the whole JSON file into Service account key (JSON).
  5. Click Test Connection. Flero mints a token from the key and calls Google with it. Google's own error, such as "Invalid JWT Signature", is shown when it fails.

Flero mints a fresh access token from the key whenever one is needed. There is no refresh token and no sign-in to expire. What the workflow can do is set by the service account's IAM roles.

Google sign-in

Sign in as a user with your own Google OAuth app. The default scope is https://www.googleapis.com/auth/cloud-platform. cloud-platform.read-only is enough for the list and get operations. Flero asks Google for offline access, so the credential stays connected.

The Flero-managed Sign in with Google is not yet offered in customer workspaces, because the managed Google app is still in Google's review.

Operations

Area Operations
Projects List projects
Compute Engine List zones, List instances, Create instance, Get instance, Delete instance
Cloud Storage List buckets, Create bucket, List objects, Upload object
Cloud Functions List locations, List functions, Create function
Cloud SQL List instances, Create instance
Pub/Sub List topics, Create topic, Get topic, Publish message, List subscriptions, Create subscription

Each operation goes to the right Google host automatically, so the credential does not need a service name.

Publish message expects each message's data to be base64. Expressions cannot encode, so build the messages in a Code node first. The published message IDs are in output.data.messageIds.

Triggers

The Google Cloud Trigger polls the list operations, every 5 minutes by default.

Common errors

Symptom Check
Test fails with "Invalid JWT Signature" The key was edited or revoked. Download a new JSON key.
403 / PERMISSION_DENIED The service account or user lacks an IAM role for that resource.
400 on Publish message A message's data is not base64.

Found something out of date? This page lives in the Flero docs content set.