Simplesat connector
Set up the Simplesat connector in Kaivo: authentication, configuration, the 4 BigQuery tables it syncs, and answers to common questions.
Simplesat connector pricing, tier and credits on kaivo.ioKaivo is a fully managed data platform that syncs your Simplesat 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 Simplesat connector
Section titled “What is the Simplesat connector”Sync your SimpleSat survey data into BigQuery with Kaivo to analyse customer satisfaction, question trends, and support quality over time.
| Category | Surveys & Email |
|---|---|
| Authentication | API key |
| Setup | Self-service |
Getting started with the Simplesat connector
Section titled “Getting started with the Simplesat connector”- Sign up for Kaivo and create a workspace.
- Connect your Simplesat 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 Simplesat
Section titled “Authenticating Simplesat”Authenticate with your API Key.
| Field | Description |
|---|---|
| API Key | |
| Your Simplesat API key, created under Settings → API keys (Owner or Admin access required; the key is shown only once). |
|
Configuring the Simplesat connector
Section titled “Configuring the Simplesat connector”When you set up the connector, you provide:
| Field | Description |
|---|---|
| Start Date | |
| Any data before this date will not be fetched. |
|
Tables and columns synced from Simplesat
Section titled “Tables and columns synced from Simplesat”Kaivo syncs 4 tables from Simplesat into a dedicated dataset in your BigQuery warehouse. Click any table to see its columns and types.
answers (16 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
choice |
STRING |
|
choice_label |
STRING |
|
created |
STRING |
|
follow_up_answer |
STRING |
|
id |
FLOAT64 |
|
modified |
STRING |
|
published_as_testimonial |
BOOL |
|
question__id |
FLOAT64 |
|
question__metric |
STRING |
|
question__text |
STRING |
|
response_id |
FLOAT64 |
|
sentiment |
STRING |
|
survey__id |
FLOAT64 |
|
survey__name |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
questions (10 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
id |
FLOAT64 |
|
metric |
STRING |
|
order |
FLOAT64 |
|
rating_scale |
BOOL |
|
required |
BOOL |
|
survey__id |
FLOAT64 |
|
survey__name |
STRING |
|
text |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: questions__choices
Section titled “Subtable: questions__choices”| 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. |
value |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: questions__rules
Section titled “Subtable: questions__rules”| 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. |
action |
STRING |
|
question__id |
FLOAT64 |
|
question__required |
BOOL |
|
question__text |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: questions__rules__conditions
Section titled “Subtable: questions__rules__conditions”| 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. |
value |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: questions__rules__question__choices
Section titled “Subtable: questions__rules__question__choices”| 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. |
value |
JSON |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: questions__rules__question__rules
Section titled “Subtable: questions__rules__question__rules”| 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. |
value |
JSON |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
responses (12 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
created |
STRING |
|
customer__email |
STRING |
|
customer__id |
FLOAT64 |
|
id |
FLOAT64 |
|
ip_address |
STRING |
|
modified |
STRING |
|
survey__id |
FLOAT64 |
|
survey__name |
STRING |
|
ticket__external_id |
STRING |
|
ticket__id |
FLOAT64 |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: responses__answers
Section titled “Subtable: responses__answers”| 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. |
choice |
STRING |
|
choice_label |
STRING |
|
follow_up_answer |
STRING |
|
follow_up_question__id |
FLOAT64 |
|
follow_up_question__metric |
STRING |
|
follow_up_question__text |
STRING |
|
id |
FLOAT64 |
|
question__id |
FLOAT64 |
|
question__metric |
STRING |
|
question__text |
STRING |
|
sentiment |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: responses__customer__tags
Section titled “Subtable: responses__customer__tags”| 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. |
value |
JSON |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
surveys (8 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
brand_name |
STRING |
|
id |
FLOAT64 |
|
metric |
STRING |
|
name |
STRING |
|
survey_token |
STRING |
|
survey_type |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
How the Simplesat sync works
Section titled “How the Simplesat sync works”After the first load, Kaivo keeps your BigQuery warehouse up to date for you. Where Simplesat 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 Simplesat?
Section titled “How long does the initial sync take for Simplesat?”It depends on how much history is in your Simplesat 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 Simplesat’s schema changes?
Section titled “What happens when Simplesat’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 Simplesat, 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 Simplesat 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 Simplesat connector in Kaivo and all of its synced data is deleted with it.
Common use cases for Simplesat data
Section titled “Common use cases for Simplesat data”Satisfaction trends
Section titled “Satisfaction trends”Use responses and answers to track CSAT and sentiment over time.
Question analysis
Section titled “Question analysis”Join questions with answers to see how customers rate each area.
Support context
Section titled “Support context”Bring satisfaction data into BigQuery to connect it to your support activity.
Use Simplesat data in your AI and BI tools
Section titled “Use Simplesat data in your AI and BI tools”Once Simplesat 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 Simplesat 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 Simplesat connector pricing and plan details.