Connect Gmail to Klaviyo in two minutes.
Real-time triggers from Gmail, ready-made actions in Klaviyo. Filter, transform, and route without writing a line of code.
Workflows do something in Klaviyo, 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 Klaviyo.
1 Gmail triggers wired to 5 Klaviyo actions. Most-used pairing: New Email → Create Campaign.
Or fire it the other way around.
2 Klaviyo triggers wired to 27 Gmail actions downstream.
See Klaviyo → Gmail →Common Gmail → Klaviyo 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.
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 Klaviyo in five steps.
No code, no glue, no half-day setup. Each step is one click.
- 1ConnectAuthorize Gmail and Klaviyo
Open TinyCommand, authorize Gmail and Klaviyo 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 Klaviyo action
Drop the Klaviyo → Create Campaign action below it. Map fields from the Gmail payload into the Klaviyo inputs.
klaviyo.create-campaign - 5PublishPublish and forget
Hit Publish. TinyCommand runs it in production from second one. Watch the run-log fill up.