MPer-pair page

Connect Gmail to Mux in two minutes.

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

Connect Gmail to Mux — start free See reverse direction

Trigger app

Gmail as the trigger

Workflows fire when something happens in Gmail.

New EmailWebhook

Action app

Mux as the action

Workflows do something in Mux, instantly.

Connect Gmail to Mux — start free

Both directions

Pick the way that fits your stack.

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

MGmail → Mux

When something happens in Gmail, do it in Mux.

1 Gmail triggers wired to 3 Mux actions. Most-used pairing: New Email → Create Mux Asset from URL.

New Email

MMux → Gmail

Or fire it the other way around.

0 Mux triggers wired to 27 Gmail actions downstream.

Use any trigger in the catalog as the upstream.

See Mux → Gmail →

Popular pairings

Common Gmail → Mux workflows.

Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.

Showing 3 of 3 combinations

When new email in Gmail, create mux asset from url in Mux.

Fires when a new email is received in Gmail. Returns full email content; enable "Include Attachments" to automatically download all file attachments.

When new email in Gmail, get mux asset in Mux.

Fires when a new email is received in Gmail. Returns full email content; enable "Include Attachments" to automatically download all file attachments.

When new email in Gmail, list mux assets in Mux.

Fires when a new email is received in Gmail. Returns full email content; enable "Include Attachments" to automatically download all file attachments.

How it works

Connect Gmail and Mux in five steps.

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

1
Connect
Authorize Gmail and Mux
Open TinyCommand, authorize Gmail and Mux 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 Mux action
Drop the Mux → Create Mux Asset from URL action below it. Map fields from the Gmail payload into the Mux inputs.
mux.create-asset-from-url
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 + Mux.

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

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

Is the Gmail ↔ Mux integration real-time?

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

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

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

No. Both integrations come on every plan, including Free, which includes 1,000 credits a month with no credit card. Each workflow step uses 1 credit, and paid plans include more credits and team seats when you need them.

What if I want Mux → Gmail instead?

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

Other apps that pair well with Gmail.

Gmail + Slack

Communication

Gmail + Google Sheets

Spreadsheets & Databases

Spreadsheets & Databases

Connect Gmail to Mux — start free