Orbit Love → Birst
AI-first ETL from Orbit Love into Birst. Governed entities, incremental sync, typed landing tables.
How Datrise loads Orbit Love into Birst
Datrise syncs Orbit Love's records, events, and configuration objects into Birst as warehouse tables for Birst's automated star schema. Flexible or custom fields land in flattened columns, and timestamps such as created, updated, and status changes are typed as date/time dimensions.
Sync is incremental: Datrise uses incremental refresh of the source tables Birst ingests, so re-runs update only what changed. Date-partitioned facts. Birst builds its own semantic layer, so Datrise lands conformed, well-keyed tables it can automate against.
Ideal for networked, governed enterprise BI.
Endpoints
Orbit Love: SaaS or API data source for analytics and warehouse sync.
Birst: Cloud BI with networked analytics and enterprise semantic layers.
How Orbit Love entities map to Birst
| Orbit Love entity | Birst object | Notes |
|---|---|---|
| records | orbit_love_records | id PK · custom fields → flattened columns |
| events | orbit_love_events | date/time dimensions events |
| configuration objects | orbit_love_configuration_objects | id PK · linked to orbit_love_records |
FAQ
How does Datrise handle Orbit Love's custom fields in Birst?
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 Birst types.
How does the Orbit Love to Birst sync stay up to date?
It runs incrementally — Datrise uses incremental refresh of the source tables Birst ingests.
Related pipelines
More destinations for Orbit Love
Early access
Connect Orbit Love to Birst 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.