Firebolt to Redash Integration

How Datrise loads Firebolt into Redash

Datrise syncs Firebolt's databases, tables, aggregating indexes, query jobs, table schemas, and partitions 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

Firebolt: Cloud data warehouse tuned for fast analytics.

Redash: Open-source SQL client for queries, visualizations, and dashboards.

How Firebolt entities map to Redash

Firebolt entity	Redash object	Notes
databases	`firebolt_databases`	id PK · custom fields → flattened columns for query results
tables	`firebolt_tables`	id PK · linked to firebolt_databases
aggregating indexes	`firebolt_aggregating_indexes`	id PK · linked to firebolt_databases
query jobs	`firebolt_query_jobs`	id PK · linked to firebolt_databases

FAQ

How does Datrise handle Firebolt'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 Firebolt to Redash sync stay up to date?

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

Related pipelines

Early access

Connect Firebolt 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.