ActionGCP Cloud FunctionsUpdated May 2026

How do I invoke a GCP Cloud Function?

Short answer: Drop the "GCP Cloud Functions → Call Cloud Function" 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
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.

Triggered by

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

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 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. Tiny Command handles GCP Cloud Functions's rate limits automatically so you don't have to throttle manually.

More actions