Onfleet to Looker Studio Integration

How Datrise loads Onfleet into Looker Studio

Datrise syncs Onfleet's tasks, workers, teams, destinations, delivery events, and recipients into Looker Studio as warehouse tables Looker Studio connects to. Flexible or custom fields land in flattened columns for chart fields, and timestamps such as created, updated, and status changes are typed as date dimension columns.

Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned tables to keep extract refresh fast. Looker Studio performs best on pre-aggregated tables, so Datrise lands tidy, report-shaped tables rather than raw API payloads.

Ideal for free, shareable dashboards on Google data sources.

Endpoints

Onfleet: Last-mile delivery dispatch and driver tracking.

Looker Studio: Google self-service dashboards and reporting (formerly Data Studio).

How Onfleet entities map to Looker Studio

Onfleet entity	Looker Studio object	Notes
tasks	`onfleet_tasks`	id PK · custom fields → flattened columns for chart fields
workers	`onfleet_workers`	id PK · linked to onfleet_tasks
teams	`onfleet_teams`	id PK · linked to onfleet_tasks
destinations	`onfleet_destinations`	id PK · linked to onfleet_tasks

FAQ

How does Datrise handle Onfleet's custom fields in Looker Studio?

Flexible values are stored as flattened columns for chart fields, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Looker Studio types.

How does the Onfleet to Looker Studio sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the connected tables.

Related pipelines

Early access

Connect Onfleet to Looker Studio the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.