k6 Cloud to Domo Integration
AI-first ETL from k6 Cloud into Domo. Governed entities, incremental sync, typed landing tables.
How Datrise loads k6 Cloud into Domo
Datrise syncs k6 Cloud's test runs, thresholds, checks, metrics, virtual users, and response times 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
k6 Cloud: Load testing runs and performance thresholds.
Domo: Cloud BI platform combining data integration and executive dashboards.
How k6 Cloud entities map to Domo
| k6 Cloud entity | Domo object | Notes |
|---|---|---|
| test runs | k6_cloud_test_runs | id PK · custom fields → flattened columns for Magic ETL |
| thresholds | k6_cloud_thresholds | id PK · linked to k6_cloud_test_runs |
| checks | k6_cloud_checks | id PK · linked to k6_cloud_test_runs |
| metrics | k6_cloud_metrics | id PK · linked to k6_cloud_test_runs |
FAQ
How does Datrise handle k6 Cloud'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 k6 Cloud to Domo sync stay up to date?
It runs incrementally — Datrise uses partitioned dataset updates rather than full replaces.
Related pipelines
More destinations for k6 Cloud
Early access
Connect k6 Cloud 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.