DatriseAI-first ETL

Onfleet to Spreadsheets Integration

AI-first ETL from Onfleet into Spreadsheets. Governed entities, incremental sync, typed landing tables.

How Datrise loads Onfleet into Spreadsheets

Datrise syncs Onfleet's tasks, workers, teams, destinations, delivery events, and recipients into Spreadsheets as a tab per source entity. Flexible or custom fields land in JSON-stringified cells for nested fields, and timestamps such as created, updated, and status changes are typed as ISO-8601 text or serial date cells.

Sync is incremental: Datrise uses refreshes the tab's rows each run, preserving header order, so re-runs update only what changed. Sheets caps out around the low millions of cells, so Datrise lands a curated column set rather than every raw field.

Ideal for lightweight, shareable reporting for non-technical teams.

Endpoints

Onfleet: Last-mile delivery dispatch and driver tracking.

Spreadsheets: Business-friendly spreadsheet destination for collaborative analysis.

How Onfleet entities map to Spreadsheets

Onfleet entitySpreadsheets objectNotes
tasksonfleet_tasksid PK · custom fields → JSON-stringified cells for nested fields
workersonfleet_workersid PK · linked to onfleet_tasks
teamsonfleet_teamsid PK · linked to onfleet_tasks
destinationsonfleet_destinationsid PK · linked to onfleet_tasks

FAQ

How does Datrise handle Onfleet's custom fields in Spreadsheets?

Flexible values are stored as JSON-stringified cells for nested fields, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Spreadsheets types.

How does the Onfleet to Spreadsheets sync stay up to date?

It runs incrementally — Datrise uses refreshes the tab's rows each run, preserving header order.

Related pipelines

Early access

Connect Onfleet to Spreadsheets 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.