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