tyntec SMS connector
Set up the tyntec SMS connector in Kaivo: authentication, configuration, the 3 BigQuery tables it syncs, and answers to common questions.
tyntec SMS connector pricing, tier and credits on kaivo.ioKaivo is a fully managed data platform that syncs your tyntec SMS data into a Google BigQuery warehouse and keeps it up to date automatically. There is no pipeline to build and no infrastructure to run, so you can spend your time analysing your survey and email data instead of moving it.
What is the tyntec SMS connector
Section titled “What is the tyntec SMS connector”Sync your tyntec SMS data into BigQuery with Kaivo to analyse SMS sending volume, delivery, contacts, and messaging costs.
| Category | Surveys & Email |
|---|---|
| Authentication | API key |
| Setup | Self-service |
Getting started with the tyntec SMS connector
Section titled “Getting started with the tyntec SMS connector”- Sign up for Kaivo and create a workspace.
- Connect your tyntec SMS account.
- Choose which tables to sync.
- Wait for the initial sync to finish.
- Query your data in BigQuery or your favourite AI or BI tool.
Authenticating tyntec SMS
Section titled “Authenticating tyntec SMS”Authenticate with your Tyntec API Key.
| Field | Description |
|---|---|
| Tyntec API Key | |
| Your Tyntec API Key, found under API Settings in your tyntec account. See here |
|
Tables and columns synced from tyntec SMS
Section titled “Tables and columns synced from tyntec SMS”Kaivo syncs 3 tables from tyntec SMS into a dedicated dataset in your BigQuery warehouse. Click any table to see its columns and types.
contacts (3 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
size |
INT64 |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: contacts__contacts
Section titled “Subtable: contacts__contacts”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
company_address |
STRING |
|
company_name |
STRING |
|
contact_email |
STRING |
|
contact_name |
STRING |
|
contact_phone |
STRING |
|
contact_title |
STRING |
|
friendly_name |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
phones (3 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
size |
INT64 |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: phones__provisioning_requests
Section titled “Subtable: phones__provisioning_requests”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
account_id |
STRING |
|
contact_id |
STRING |
|
friendly_name |
STRING |
|
request_id |
STRING |
|
status |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
registrations (3 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
size |
INT64 |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: registrations__provisioning_requests
Section titled “Subtable: registrations__provisioning_requests”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
account_id |
STRING |
|
contact_id |
STRING |
|
friendly_name |
STRING |
|
request_id |
STRING |
|
status |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
How the tyntec SMS sync works
Section titled “How the tyntec SMS sync works”After the first load, Kaivo keeps your BigQuery warehouse up to date for you. Where tyntec SMS supports it, each sync pulls only new and changed records so it stays fast; otherwise it refreshes the whole table. Every record keeps its original ID, so you won’t get duplicate rows.
Frequently asked questions
Section titled “Frequently asked questions”How long does the initial sync take for tyntec SMS?
Section titled “How long does the initial sync take for tyntec SMS?”It depends on how much history is in your tyntec SMS account. Most initial syncs finish within minutes, while large accounts can take a few hours. After that, syncs only fetch new and changed records, so they’re much faster.
Can I sync only some tables or columns?
Section titled “Can I sync only some tables or columns?”Yes. You pick which tables to sync when you set up the connection and can change the selection later. Tables you don’t select are never copied to your warehouse.
What happens when tyntec SMS’s schema changes?
Section titled “What happens when tyntec SMS’s schema changes?”New fields are never added automatically. You choose which fields to sync, so data you haven’t selected (sensitive personal data, for example) never lands in your warehouse. When a new field appears, it becomes available for you to add. What happens to removed or renamed fields depends on a table’s sync mode: full-refresh tables always match what’s currently in tyntec SMS, so dropped fields disappear, while incremental tables keep their existing columns and history, so an old field stays and newly added fields fill in over time.
How do I handle GDPR or data deletion requests?
Section titled “How do I handle GDPR or data deletion requests?”Your data lives in your own Kaivo-managed BigQuery warehouse, so the most direct option is to delete or anonymise specific records right in BigQuery. If you delete data in tyntec SMS instead, full-refresh tables drop it on the next sync, while incremental tables keep it, so you would remove the row in BigQuery or ask us to run a full refresh. To remove everything, delete the tyntec SMS connector in Kaivo and all of its synced data is deleted with it.
Common use cases for tyntec SMS data
Section titled “Common use cases for tyntec SMS data”SMS volume
Section titled “SMS volume”Use phones and registrations to track messaging activity over time.
Contact view
Section titled “Contact view”Use contacts to understand who you message.
Cost analysis
Section titled “Cost analysis”Bring SMS data into BigQuery to track spend alongside your other channels.
Use tyntec SMS data in your AI and BI tools
Section titled “Use tyntec SMS data in your AI and BI tools”Once tyntec SMS data lands in your Kaivo-managed BigQuery warehouse, you can explore it with AI tools or any BI tool that connects to BigQuery. Here’s how the most common destinations work with tyntec SMS data.
Claude
Section titled “Claude”Use Kaivo’s MCP server to give Claude secure, workspace-scoped access to your data. Setup guide →
Power BI
Section titled “Power BI”Microsoft’s BI tool with a native BigQuery connector. Supports direct query and scheduled refresh. Setup guide →
Data Studio
Section titled “Data Studio”Free Google BI tool with native BigQuery support. One-click connection to your Kaivo warehouse; great for SMB teams on Google Workspace. Setup guide →
Tableau
Section titled “Tableau”The premium analytics standard, with native BigQuery integration. Setup guide →
Google Sheets
Section titled “Google Sheets”Use Connected Sheets to query BigQuery directly from a spreadsheet, with no SQL. Setup guide →
Connect via Power Query’s BigQuery connector. Setup guide →
Metabase
Section titled “Metabase”Open-source BI tool with strong BigQuery support. Setup guide →
See our pricing page for tyntec SMS connector pricing and plan details.