EPer-pair page

Connect Exa to Gmail in two minutes.

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

Connect Exa and Gmail See reverse direction

Trigger app

Exa as the trigger

Workflows fire when something happens in Exa.

Exa has no triggers yet. Use the catalog's universal Webhook trigger as the upstream.

Action app

Gmail as the action

Workflows do something in Gmail, instantly.

See all 27 actions →

Both directions

Pick the way that fits your stack.

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

EExa → Gmail

When something happens in Exa, do it in Gmail.

0 Exa triggers wired to 27 Gmail actions.

EGmail → Exa

Or fire it the other way around.

1 Gmail triggers wired to 4 Exa actions downstream.

New Email

See Gmail → Exa →

How it works

Connect Exa and Gmail in five steps.

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

1
Connect
Authorize Exa and Gmail
Open Tiny Command, authorize Exa and Gmail once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a Exa trigger
Drop the Exa → New event trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/exa.event
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 Gmail action
Drop the Gmail → Add Labels to Message action below it. Map fields from the Exa payload into the Gmail inputs.
google-gmail.add-labels
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 Exa + Gmail.

How long does it take to connect Exa and Gmail on Tiny Command?

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

Is the Exa ↔ Gmail integration real-time?

Yes. Both Exa and Gmail 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 Exa and Gmail?

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 Gmail.

What Exa events can trigger a Gmail workflow?

Use Tiny Command's universal Webhook trigger to receive Exa events, then run any of the 27 Gmail actions downstream.

Do I need a paid plan to use Exa with Gmail?

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

What if I want Gmail → Exa instead?

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