Per-pair page

Connect Gmail to Onfleet in two minutes.

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

Connect Gmail and Onfleet See reverse direction

Trigger app

Gmail as the trigger

Workflows fire when something happens in Gmail.

New EmailWebhook

Action app

Onfleet as the action

Workflows do something in Onfleet, instantly.

Create Onfleet TaskAPI
List Onfleet TasksAPI

Both directions

Pick the way that fits your stack.

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

Gmail → Onfleet

When something happens in Gmail, do it in Onfleet.

1 Gmail triggers wired to 2 Onfleet actions. Most-used pairing: New Email → Create Onfleet Task.

New Email

Onfleet → Gmail

Or fire it the other way around.

5 Onfleet triggers wired to 27 Gmail actions downstream.

See Onfleet → Gmail →

Popular pairings

Common Gmail → Onfleet workflows.

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

Showing 2 of 2 combinations

When new email in Gmail, create onfleet task in Onfleet.

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 onfleet tasks in Onfleet.

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 Onfleet in five steps.

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

1
Connect
Authorize Gmail and Onfleet
Open Tiny Command, authorize Gmail and Onfleet 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 Onfleet action
Drop the Onfleet → Create Onfleet Task action below it. Map fields from the Gmail payload into the Onfleet inputs.
onfleet.create-task
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 + Onfleet.

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

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

Is the Gmail ↔ Onfleet integration real-time?

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

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

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

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

What if I want Onfleet → Gmail instead?

Build it the same way, in reverse. There's a dedicated /integrations/onfleet/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