Connect Gmail to Amplitude in two minutes.
Real-time triggers from Gmail, ready-made actions in Amplitude. Filter, transform, and route without writing a line of code.
Workflows do something in Amplitude, instantly.
- Export EventsAPI
- Identify UserAPI
- Send EventAPI
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 Amplitude.
1 Gmail triggers wired to 3 Amplitude actions. Most-used pairing: New Email → Export Events.
Or fire it the other way around.
0 Amplitude triggers wired to 27 Gmail actions downstream.
- Use any trigger in the catalog as the upstream.
Common Gmail → Amplitude 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 Amplitude in five steps.
No code, no glue, no half-day setup. Each step is one click.
- 1ConnectAuthorize Gmail and Amplitude
Open TinyCommand, authorize Gmail and Amplitude 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 Amplitude action
Drop the Amplitude → Export Events action below it. Map fields from the Gmail payload into the Amplitude inputs.
amplitude.export-events - 5PublishPublish and forget
Hit Publish. TinyCommand runs it in production from second one. Watch the run-log fill up.