ConfigCat to Domo Integration

How Datrise loads ConfigCat into Domo

Datrise syncs ConfigCat's feature flags, settings, environments, config values, evaluations, and targeting rules into Domo as datasets in Domo's cloud store via connector. Flexible or custom fields land in flattened columns for Magic ETL, and timestamps such as created, updated, and status changes are typed as date/time columns.

Sync is incremental: Datrise uses partitioned dataset updates rather than full replaces, so re-runs update only what changed. Domo dataset partitions keyed on load date. Domo stores its own copy of data, so Datrise sends incremental partitions to avoid re-uploading whole datasets.

Ideal for all-in-one cloud BI with built-in ETL.

Endpoints

ConfigCat: Feature flag and remote configuration service.

Domo: Cloud BI platform combining data integration and executive dashboards.

How ConfigCat entities map to Domo

ConfigCat entity	Domo object	Notes
feature flags	`configcat_feature_flags`	id PK · custom fields → flattened columns for Magic ETL
settings	`configcat_settings`	id PK · linked to configcat_feature_flags
environments	`configcat_environments`	id PK · linked to configcat_feature_flags
config values	`configcat_config_values`	id PK · linked to configcat_feature_flags

FAQ

How does Datrise handle ConfigCat's custom fields in Domo?

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

How does the ConfigCat to Domo sync stay up to date?

It runs incrementally — Datrise uses partitioned dataset updates rather than full replaces.

Related pipelines

Early access

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