Short answer: Drop the "GCP Cloud Functions → Call Cloud Function" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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. |
{"trigger_url": "https://my-function-abc-uc.a.run.app","method": "{{trigger.method}}","payload": "{{trigger.payload}}"}
{"ok": true,"result": "..."}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.