- Integrations
- /
- Onfleet
- /
- with Gmail
Connect Onfleet to Gmail in two minutes.
Real-time triggers from Onfleet, ready-made actions in Gmail. Filter, transform, and route without writing a line of code.
Workflows fire when something happens in Onfleet.
- Onfleet Task CompletedWebhook
- Onfleet Task CreatedWebhook
- Onfleet Task FailedWebhook
- Onfleet Task StartedWebhook
- Onfleet Worker Duty ChangeWebhook
Workflows do something in Gmail, instantly.
- Add Labels to MessageAPI
- Create DraftAPI
- Create LabelAPI
- Delete DraftAPI
- Delete LabelAPI
- Delete MessageAPI
Pick the way that fits your stack.
Pair pages are mirrored. Each direction gets its own dedicated page.
When something happens in Onfleet, do it in Gmail.
5 Onfleet triggers wired to 27 Gmail actions. Most-used pairing: Onfleet Task Completed → Add Labels to Message.
Or fire it the other way around.
1 Gmail triggers wired to 2 Onfleet actions downstream.
See Gmail → Onfleet →Common Onfleet → Gmail workflows.
Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.
Fires when a driver completes a delivery. Payload includes proof-of-delivery (signature URL, photo URL), completion time, notes. For "delivered → notify customer, log to order record" cascading workflows.
Fires when a driver completes a delivery. Payload includes proof-of-delivery (signature URL, photo URL), completion time, notes. For "delivered → notify customer, log to order record" cascading workflows.
Fires when a driver completes a delivery. Payload includes proof-of-delivery (signature URL, photo URL), completion time, notes. For "delivered → notify customer, log to order record" cascading workflows.
Fires when a driver completes a delivery. Payload includes proof-of-delivery (signature URL, photo URL), completion time, notes. For "delivered → notify customer, log to order record" cascading workflows.
Fires when a new delivery task is created. Useful for "log to delivery tracking spreadsheet" or "send pre-delivery SMS to recipient" workflows.
Fires when a new delivery task is created. Useful for "log to delivery tracking spreadsheet" or "send pre-delivery SMS to recipient" workflows.
Fires when a new delivery task is created. Useful for "log to delivery tracking spreadsheet" or "send pre-delivery SMS to recipient" workflows.
Fires when a new delivery task is created. Useful for "log to delivery tracking spreadsheet" or "send pre-delivery SMS to recipient" workflows.
Fires when the driver marks a stop as unsuccessful (customer unavailable, refused, damaged). The high-signal CS hook — fires before the customer ever calls in to complain.
Connect Onfleet and Gmail in five steps.
No code, no glue, no half-day setup. Each step is one click.
- 1ConnectAuthorize Onfleet and Gmail
Open Tiny Command, authorize Onfleet and Gmail once each. Both connections are available to every workflow on your account.
- 2TriggerPick a Onfleet trigger
Drop the Onfleet → Onfleet Task Completed trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/onfleet.trigger-task-completed - 3TransformAdd a filter or AI step
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
- 4ActionAdd the Gmail action
Drop the Gmail → Add Labels to Message action below it. Map fields from the Onfleet payload into the Gmail inputs.
google-gmail.add-labels - 5PublishPublish and forget
Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.
Questions about Onfleet + Gmail.
How long does it take to connect Onfleet and Gmail on Tiny Command?
Is the Onfleet ↔ Gmail integration real-time?
Can I filter or transform data between Onfleet and Gmail?
What Onfleet events can trigger a Gmail workflow?
Do I need a paid plan to use Onfleet with Gmail?
What if I want Gmail → Onfleet instead?
Other apps that pair well with Onfleet.
Wire Onfleet to Gmail in 2 minutes.
Free tier available. No credit card. No onboarding call.