ActionGCP Cloud FunctionsUpdated June 2026

How do I invoke a GCP Cloud Function?

Short answer: You can call cloud function in GCP Cloud Functions by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the GCP Cloud Functions Call Cloud Function action to a workflow, map its 3 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Call Cloud Function in GCP Cloud Functions — start free All 2 GCP Cloud Functions actions

Call Cloud Function in GCP Cloud Functions — start free

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
Function URL trigger_url	string	Required	HTTPS trigger URL for the function. Find in GCP Console → Cloud Functions → function → Trigger tab.
Method method	options	Optional	–
Request Body payload	object	Optional	JSON body. Ignored for GET.

Sample request

{
  "trigger_url": "https://my-function-abc-uc.a.run.app",
  "method": "{{trigger.method}}",
  "payload": "{{trigger.payload}}"
}

Returns

{
  "ok": true,
  "result": "..."
}

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

FAQ

Questions about Call Cloud Function.

What does the Call Cloud Function action do in GCP Cloud Functions?

Invokes an HTTP-triggered Cloud Function with a JSON payload. For workflows that need Python/Node logic that's better expressed in code than in workflow steps — image processing, ML inference, GCP-API-heavy operations.

What inputs does Call Cloud Function require?

Required: Function URL. 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 Call Cloud Function support batch operations?

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

How do I invoke a GCP Cloud Function?

The fields this action accepts.

Apps that pair well as the trigger for Call Cloud Function.

Questions about Call Cloud Function.

Other GCP Cloud Functions actions.