GCP Cloud Functions
GCP Cloud Functions serverless invocation
Google Cloud Functions is the GCP serverless compute service — equivalent to AWS Lambda, with first-class integration to other GCP services (Pub/Sub triggers, Cloud Storage triggers, Firestore triggers, HTTP triggers). Tiny Command exposes two actions, no triggers (Cloud Functions are themselves the trigger destination): Call Function (invoke an HTTP-triggered Cloud Function with a JSON body, get the response), List Functions (every Cloud Function in the connected project + region). The connection uses a Google Cloud service-account key with cloudfunctions.functions.invoke permissions plus the project ID and region. The Call Function pattern is the standard "delegate heavy/specific logic to Cloud Functions" workflow shape — when a Tiny Command workflow needs Python ML inference, complex image processing, or GCP-API-heavy work that's better expressed in code than in workflow steps, push the work to a Cloud Function. For "fire a Cloud Function from a workflow event" patterns, this connector is the right path.
Do anything GCP Cloud Functions can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| Call Cloud Function | 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. |
| List 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. |
Pre-built GCP Cloud Functions workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
AI-triage every GCP Cloud Functions event, ping the right channel only when it matters.
Every event matching a filter, appended to a running spreadsheet.
Turn GCP Cloud Functions into a Notion-backed source of truth, auto-tagged.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect GCP Cloud Functions once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every GCP Cloud Functions field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the GCP Cloud Functions integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect GCP Cloud Functions to Tiny Command?
What GCP Cloud Functions triggers does Tiny Command support?
What GCP Cloud Functions actions can I run from a workflow?
Is the GCP Cloud Functions integration real-time?
Do I need to write code to use GCP Cloud Functions with Tiny Command?
How much does the GCP Cloud Functions integration cost?
More other apps people connect.
Same category as GCP Cloud Functions, ordered by how often teams pair them. Hover the carousel to pause.
Do more with GCP Cloud Functions.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
