Tyntec SMS to Redash Integration
AI-first ETL from Tyntec SMS into Redash. Governed entities, incremental sync, typed landing tables.
How Datrise loads Tyntec SMS into Redash
Datrise syncs Tyntec SMS's SMS messages, recipients, delivery reports, senders, countries, and message costs into Redash as SQL tables Redash queries and visualizes. Flexible or custom fields land in flattened columns for query results, and timestamps such as created, updated, and status changes are typed as temporal columns.
Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts for scheduled queries. Redash caches query results on a schedule, so Datrise keeps tables incrementally fresh so cached dashboards reflect reality.
Ideal for lightweight, query-driven dashboards.
Endpoints
Tyntec SMS: Global SMS delivery and message status callbacks.
Redash: Open-source SQL client for queries, visualizations, and dashboards.
How Tyntec SMS entities map to Redash
| Tyntec SMS entity | Redash object | Notes |
|---|---|---|
| SMS messages | tyntec_sms_sms_messages | id PK · custom fields → flattened columns for query results |
| 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 Redash?
Flexible values are stored as flattened columns for query results, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Redash types.
How does the Tyntec SMS to Redash sync stay up to date?
It runs incrementally — Datrise uses incremental refresh of the connected tables.
Related pipelines
More destinations for Tyntec SMS
Early access
Connect Tyntec SMS to Redash 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.