Per-pair page

Connect Gmail to GCP Cloud Functions in two minutes.

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

Connect Gmail and GCP Cloud Functions See reverse direction

Trigger app

Gmail as the trigger

Workflows fire when something happens in Gmail.

New EmailWebhook

Action app

GCP Cloud Functions as the action

Workflows do something in GCP Cloud Functions, instantly.

Call Cloud FunctionAPI
List Cloud FunctionsAPI

Both directions

Pick the way that fits your stack.

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

Gmail → GCP Cloud Functions

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

1 Gmail triggers wired to 2 GCP Cloud Functions actions. Most-used pairing: New Email → Call Cloud Function.

New Email

GCP Cloud Functions → Gmail

Or fire it the other way around.

0 GCP Cloud Functions triggers wired to 27 Gmail actions downstream.

Use any trigger in the catalog as the upstream.

See GCP Cloud Functions → Gmail →

How it works

Connect Gmail and GCP Cloud Functions in five steps.

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

1
Connect
Authorize Gmail and GCP Cloud Functions
Open Tiny Command, authorize Gmail and GCP Cloud Functions once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a Gmail trigger
Drop the Gmail → New Email trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/google-gmail.trigger-email-received
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 GCP Cloud Functions action
Drop the GCP Cloud Functions → Call Cloud Function action below it. Map fields from the Gmail payload into the GCP Cloud Functions inputs.
gcp-cloud-functions.call-function
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 Gmail + GCP Cloud Functions.

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

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

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

Yes. Both Gmail and GCP Cloud Functions 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 Gmail and GCP Cloud Functions?

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 GCP Cloud Functions.

What Gmail events can trigger a GCP Cloud Functions workflow?

Any of the 1 Gmail triggers, including "New Email". Each fires in real time when the matching event happens in Gmail.

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

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

What if I want GCP Cloud Functions → Gmail instead?

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