Per-pair page

Connect Gmail to Hunter in two minutes.

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

Connect Gmail and Hunter See reverse direction

Trigger app

Gmail as the trigger

Workflows fire when something happens in Gmail.

New EmailWebhook

Action app

Hunter as the action

Workflows do something in Hunter, instantly.

Both directions

Pick the way that fits your stack.

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

Gmail → Hunter

When something happens in Gmail, do it in Hunter.

1 Gmail triggers wired to 4 Hunter actions. Most-used pairing: New Email → Hunter Domain Search.

New Email

Hunter → Gmail

Or fire it the other way around.

0 Hunter triggers wired to 27 Gmail actions downstream.

Use any trigger in the catalog as the upstream.

See Hunter → Gmail →

How it works

Connect Gmail and Hunter in five steps.

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

1
Connect
Authorize Gmail and Hunter
Open Tiny Command, authorize Gmail and Hunter once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a Gmail trigger
Drop the Gmail → New Email trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/google-gmail.trigger-email-received
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 Hunter action
Drop the Hunter → Hunter Domain Search action below it. Map fields from the Gmail payload into the Hunter inputs.
hunter.domain-search
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 Gmail + Hunter.

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

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

Is the Gmail ↔ Hunter integration real-time?

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

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

What Gmail events can trigger a Hunter workflow?

Any of the 1 Gmail triggers, including "New Email". Each fires in real time when the matching event happens in Gmail.

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

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

What if I want Hunter → Gmail instead?

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