GPer-pair page

Connect Gmail to Gumlet in two minutes.

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

Connect Gmail to Gumlet — start free See reverse direction

Trigger app

Gmail as the trigger

Workflows fire when something happens in Gmail.

New EmailWebhook

Action app

Gumlet as the action

Workflows do something in Gumlet, instantly.

Both directions

Pick the way that fits your stack.

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

GGmail → Gumlet

When something happens in Gmail, do it in Gumlet.

1 Gmail triggers wired to 3 Gumlet actions. Most-used pairing: New Email → Upload Video to Gumlet.

New Email

GGumlet → Gmail

Or fire it the other way around.

0 Gumlet triggers wired to 27 Gmail actions downstream.

Use any trigger in the catalog as the upstream.

See Gumlet → Gmail →

How it works

Connect Gmail and Gumlet in five steps.

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

1
Connect
Authorize Gmail and Gumlet
Open TinyCommand, authorize Gmail and Gumlet 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. TinyCommand 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 Gumlet action
Drop the Gumlet → Upload Video to Gumlet action below it. Map fields from the Gmail payload into the Gumlet inputs.
gumlet.create-upload
5
Publish
Publish and forget
Hit Publish. TinyCommand runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about Gmail + Gumlet.

How long does it take to connect Gmail and Gumlet on TinyCommand?

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

Is the Gmail ↔ Gumlet integration real-time?

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

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

What Gmail events can trigger a Gumlet 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 Gumlet?

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

What if I want Gumlet → Gmail instead?

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