ActionGCP Cloud FunctionsUpdated September 2026
What Cloud Functions exist in this project?
Short answer: You can list cloud functions in GCP Cloud Functions by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the GCP Cloud Functions List Cloud Functions action to a workflow, map its 2 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
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.
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 run history shows the failed step with its input and the error message GCP Cloud Functions returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does List Cloud Functions support batch operations?
Run List Cloud Functions inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within GCP Cloud Functions's rate limits.
More actions