Deputy to Redash Integration
AI-first ETL from Deputy into Redash. Governed entities, incremental sync, typed landing tables.
How Datrise loads Deputy into Redash
Datrise syncs Deputy's employees, shifts, timesheets, locations, leave requests, and pay rates into Redash as SQL tables Redash queries and visualizes. Flexible or custom fields land in flattened columns for query results, and timestamps such as created, updated, and status changes are typed as temporal columns.
Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts for scheduled queries. Redash caches query results on a schedule, so Datrise keeps tables incrementally fresh so cached dashboards reflect reality.
Ideal for lightweight, query-driven dashboards.
Endpoints
Deputy: Workforce scheduling and timesheet management.
Redash: Open-source SQL client for queries, visualizations, and dashboards.
How Deputy entities map to Redash
| Deputy entity | Redash object | Notes |
|---|---|---|
| employees | deputy_employees | id PK · custom fields → flattened columns for query results |
| shifts | deputy_shifts | id PK · linked to deputy_employees |
| timesheets | deputy_timesheets | id PK · linked to deputy_employees |
| locations | deputy_locations | id PK · linked to deputy_employees |
FAQ
How does Datrise handle Deputy's custom fields in Redash?
Flexible values are stored as flattened columns for query results, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Redash types.
How does the Deputy to Redash sync stay up to date?
It runs incrementally — Datrise uses incremental refresh of the connected tables.
Related pipelines
More destinations for Deputy
Early access
Connect Deputy to Redash 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.