ActionGCP Cloud FunctionsUpdated May 2026

What Cloud Functions exist in this project?

Short answer: Drop the "GCP Cloud Functions → List Cloud Functions" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 2 GCP Cloud Functions actions

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Project ID project_id	string	Required	my-gcp-project
Region location	string	Required	Region (or `-` for all regions).

Sample request

{
  "project_id": "my-gcp-project",
  "location": "us-central1"
}

Returns

{
  "functions": [
    {
      "name": "projects/my-project/locations/us-central1/functions/my-func",
      "state": "ACTIVE",
      "serviceConfig": {
        "uri": "https://my-func-abc-uc.a.run.app"
      }
    }
  ]
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for List Cloud Functions.

Any of these apps can fire this action as part of a workflow.

Gmail → GCP Cloud Functions

1 Gmail triggers

Slack → GCP Cloud Functions

13 Slack triggers

Google Sheets → GCP Cloud Functions

2 Google Sheets triggers

HubSpot → GCP Cloud Functions

18 HubSpot triggers

FAQ

Questions about List Cloud Functions.

What does the List Cloud Functions action do in GCP Cloud Functions?

Returns all Cloud Functions in the project+region with name, runtime, trigger type. Useful for inventory and for resolving function URLs at workflow setup.

What inputs does List Cloud Functions require?

Required: Project ID, Region. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if GCP Cloud Functions returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does List Cloud Functions support batch operations?

Yes. Run List Cloud Functions inside a Loop node to process arrays. Tiny Command handles GCP Cloud Functions's rate limits automatically so you don't have to throttle manually.

More actions