DatriseAI-first ETL

ConfigCat to Redash Integration

AI-first ETL from ConfigCat into Redash. Governed entities, incremental sync, typed landing tables.

How Datrise loads ConfigCat into Redash

Datrise syncs ConfigCat's feature flags, settings, environments, config values, evaluations, and targeting rules 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

ConfigCat: Feature flag and remote configuration service.

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

How ConfigCat entities map to Redash

ConfigCat entityRedash objectNotes
feature flagsconfigcat_feature_flagsid PK · custom fields → flattened columns for query results
settingsconfigcat_settingsid PK · linked to configcat_feature_flags
environmentsconfigcat_environmentsid PK · linked to configcat_feature_flags
config valuesconfigcat_config_valuesid PK · linked to configcat_feature_flags

FAQ

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

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

Related pipelines

Early access

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