Tyntec SMS to Birst Integration
AI-first ETL from Tyntec SMS into Birst. Governed entities, incremental sync, typed landing tables.
How Datrise loads Tyntec SMS into Birst
Datrise syncs Tyntec SMS's SMS messages, recipients, delivery reports, senders, countries, and message costs 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
Tyntec SMS: Global SMS delivery and message status callbacks.
Birst: Cloud BI with networked analytics and enterprise semantic layers.
How Tyntec SMS entities map to Birst
| Tyntec SMS entity | Birst object | Notes |
|---|---|---|
| SMS messages | tyntec_sms_sms_messages | id PK · custom fields → flattened columns |
| recipients | tyntec_sms_recipients | id PK · linked to tyntec_sms_sms_messages |
| delivery reports | tyntec_sms_delivery_reports | id PK · linked to tyntec_sms_sms_messages |
| senders | tyntec_sms_senders | id PK · linked to tyntec_sms_sms_messages |
FAQ
How does Datrise handle Tyntec SMS'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 Tyntec SMS 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 Tyntec SMS
Early access
Connect Tyntec SMS 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.