Per-pair page

Connect Gmail to Runway in two minutes.

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

Connect Gmail and Runway See reverse direction

Trigger app

Gmail as the trigger

Workflows fire when something happens in Gmail.

New EmailWebhook

Action app

Runway as the action

Workflows do something in Runway, instantly.

Both directions

Pick the way that fits your stack.

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

Gmail → Runway

When something happens in Gmail, do it in Runway.

1 Gmail triggers wired to 4 Runway actions. Most-used pairing: New Email → Runway Aleph (Video Edit).

New Email

Runway → Gmail

Or fire it the other way around.

0 Runway triggers wired to 27 Gmail actions downstream.

Use any trigger in the catalog as the upstream.

See Runway → Gmail →

How it works

Connect Gmail and Runway in five steps.

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

1
Connect
Authorize Gmail and Runway
Open Tiny Command, authorize Gmail and Runway 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 Runway action
Drop the Runway → Runway Aleph (Video Edit) action below it. Map fields from the Gmail payload into the Runway inputs.
runway.generate-aleph
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 + Runway.

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

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

Is the Gmail ↔ Runway integration real-time?

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

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

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

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

What if I want Runway → Gmail instead?

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