Connect Gmail to Google Vertex AI in two minutes.
Real-time triggers from Gmail, ready-made actions in Google Vertex AI. Filter, transform, and route without writing a line of code.
Workflows do something in Google Vertex AI, instantly.
Pick the way that fits your stack.
Pair pages are mirrored. Each direction gets its own dedicated page.
When something happens in Gmail, do it in Google Vertex AI.
1 Gmail triggers wired to 3 Google Vertex AI actions. Most-used pairing: New Email → Embed Text.
Or fire it the other way around.
0 Google Vertex AI triggers wired to 27 Gmail actions downstream.
- Use any trigger in the catalog as the upstream.
Common Gmail → Google Vertex AI workflows.
Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.
Fires when a new email is received in Gmail. Returns full email content; enable "Include Attachments" to automatically download all file attachments.
Fires when a new email is received in Gmail. Returns full email content; enable "Include Attachments" to automatically download all file attachments.
Fires when a new email is received in Gmail. Returns full email content; enable "Include Attachments" to automatically download all file attachments.
Connect Gmail and Google Vertex AI in five steps.
No code, no glue, no half-day setup. Each step is one click.
- 1ConnectAuthorize Gmail and Google Vertex AI
Open TinyCommand, authorize Gmail and Google Vertex AI once each. Both connections are available to every workflow on your account.
- 2TriggerPick a Gmail trigger
Drop the Gmail → New Email trigger onto the canvas. TinyCommand auto-registers the webhook.
POST /v1/webhooks/google-gmail.trigger-email-received - 3TransformAdd a filter or AI step
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
- 4ActionAdd the Google Vertex AI action
Drop the Google Vertex AI → Embed Text action below it. Map fields from the Gmail payload into the Google Vertex AI inputs.
vertex-ai.embed-text - 5PublishPublish and forget
Hit Publish. TinyCommand runs it in production from second one. Watch the run-log fill up.