Per-pair page

Connect GCP Cloud Functions to Gmail in two minutes.

Real-time triggers from GCP Cloud Functions, ready-made actions in Gmail. Filter, transform, and route without writing a line of code.

Connect GCP Cloud Functions and Gmail See reverse direction

Trigger app

GCP Cloud Functions as the trigger

Workflows fire when something happens in GCP Cloud Functions.

GCP Cloud Functions has no triggers yet. Use the catalog's universal Webhook trigger as the upstream.

Action app

Gmail as the action

Workflows do something in Gmail, instantly.

See all 27 actions →

Both directions

Pick the way that fits your stack.

Pair pages are mirrored. Each direction gets its own dedicated page.

GCP Cloud Functions → Gmail

When something happens in GCP Cloud Functions, do it in Gmail.

0 GCP Cloud Functions triggers wired to 27 Gmail actions.

Gmail → GCP Cloud Functions

Or fire it the other way around.

1 Gmail triggers wired to 2 GCP Cloud Functions actions downstream.

New Email

See Gmail → GCP Cloud Functions →

How it works

Connect GCP Cloud Functions and Gmail in five steps.

No code, no glue, no half-day setup. Each step is one click.

1
Connect
Authorize GCP Cloud Functions and Gmail
Open Tiny Command, authorize GCP Cloud Functions and Gmail once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a GCP Cloud Functions trigger
Drop the GCP Cloud Functions → New event trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/gcp-cloud-functions.event
3
Transform
Add a filter or AI step
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
4
Action
Add the Gmail action
Drop the Gmail → Add Labels to Message action below it. Map fields from the GCP Cloud Functions payload into the Gmail inputs.
google-gmail.add-labels
5
Publish
Publish and forget
Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about GCP Cloud Functions + Gmail.

How long does it take to connect GCP Cloud Functions and Gmail on Tiny Command?

Under two minutes. Authorize GCP Cloud Functions and Gmail once each, drop the GCP Cloud Functions trigger and Gmail action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.

Is the GCP Cloud Functions ↔ Gmail integration real-time?

Yes. Both GCP Cloud Functions and Gmail expose webhooks, so events from one fire workflows in the other within seconds rather than on a polling interval.

Can I filter or transform data between GCP Cloud Functions and Gmail?

Yes. Add a Filter node to only pass through matching events, a Switch node to branch by value, or an AI / Code node to transform payloads before they hit Gmail.

What GCP Cloud Functions events can trigger a Gmail workflow?

Use Tiny Command's universal Webhook trigger to receive GCP Cloud Functions events, then run any of the 27 Gmail actions downstream.

Do I need a paid plan to use GCP Cloud Functions with Gmail?

No. There's a free tier that covers most GCP Cloud Functions+Gmail use cases without a credit card. Paid plans unlock higher run volumes and team features when you outgrow it.

What if I want Gmail → GCP Cloud Functions instead?

Build it the same way, in reverse. There's a dedicated /integrations/google-gmail/with/gcp-cloud-functions page with the reverse-direction triggers and actions.