Instatus to GoodData Integration
AI-first ETL from Instatus into GoodData. Governed entities, incremental sync, typed landing tables.
How Datrise loads Instatus into GoodData
Datrise syncs Instatus's incidents, components, incident updates, subscribers, status page views, and uptime history into GoodData as warehouse tables GoodData maps into its logical data model. Flexible or custom fields land in flattened columns, and timestamps such as created, updated, and status changes are typed as date dimensions.
Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts. GoodData's LDM maps datasets by keys, so Datrise lands stable primary and foreign id columns to keep the model valid.
Ideal for embedded, multi-tenant analytics.
Endpoints
Instatus: Fast status pages with incident timelines and subscribers.
GoodData: Composable analytics platform with headless BI and embedded dashboards.
How Instatus entities map to GoodData
| Instatus entity | GoodData object | Notes |
|---|---|---|
| incidents | instatus_incidents | id PK · custom fields → flattened columns |
| components | instatus_components | id PK · linked to instatus_incidents |
| incident updates | instatus_incident_updates | id PK · linked to instatus_incidents |
| subscribers | instatus_subscribers | id PK · linked to instatus_incidents |
FAQ
How does Datrise handle Instatus's custom fields in GoodData?
Flexible values are stored as flattened columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native GoodData types.
How does the Instatus to GoodData sync stay up to date?
It runs incrementally — Datrise uses incremental refresh of the connected tables.
Related pipelines
More destinations for Instatus
Early access
Connect Instatus to GoodData 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.