DatriseAI-first ETL

Tyntec SMS to GoodData Integration

AI-first ETL from Tyntec SMS into GoodData. Governed entities, incremental sync, typed landing tables.

How Datrise loads Tyntec SMS into GoodData

Datrise syncs Tyntec SMS's SMS messages, recipients, delivery reports, senders, countries, and message costs 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

Tyntec SMS: Global SMS delivery and message status callbacks.

GoodData: Composable analytics platform with headless BI and embedded dashboards.

How Tyntec SMS entities map to GoodData

Tyntec SMS entityGoodData objectNotes
SMS messagestyntec_sms_sms_messagesid PK · custom fields → flattened columns
recipientstyntec_sms_recipientsid PK · linked to tyntec_sms_sms_messages
delivery reportstyntec_sms_delivery_reportsid PK · linked to tyntec_sms_sms_messages
senderstyntec_sms_sendersid PK · linked to tyntec_sms_sms_messages

FAQ

How does Datrise handle Tyntec SMS'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 Tyntec SMS to GoodData sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the connected tables.

Related pipelines

Early access

Connect Tyntec SMS 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.