Okta to GoodData Integration
AI-first ETL from Okta into GoodData. Governed entities, incremental sync, typed landing tables.
How Datrise loads Okta into GoodData
Datrise syncs Okta's users, groups, applications, system log events, factors, and group memberships 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
Okta: Identity provider for SSO and user lifecycle.
GoodData: Composable analytics platform with headless BI and embedded dashboards.
How Okta entities map to GoodData
| Okta entity | GoodData object | Notes |
|---|---|---|
| users | okta_users | id PK · custom fields → flattened columns |
| groups | okta_groups | id PK · linked to okta_users |
| applications | okta_applications | id PK · linked to okta_users |
| system log events | okta_system_log_events | date dimensions events |
FAQ
How does Datrise handle Okta'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 Okta to GoodData sync stay up to date?
It runs incrementally — Datrise uses incremental refresh of the connected tables.
Related pipelines
More destinations for Okta
Early access
Connect Okta 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.