Typeform
Typeform is an online survey management solution.
Features
| Feature Name | Supported | Notes |
|---|---|---|
| Capture deletes | check | RESPONSE, RESPONSE_ANSWER, RESPONSE_ANSWER_CHOICE, and RESPONSE_VARIABLE tables. |
| History mode | check | FORM_HISTORY, FORM_FIELD_HISTORY, FORM_FIELD_CHOICE_HISTORY, FORM_HIDDEN_FIELD_HISTORY, FORM_LOGIC_HISTORY, LOGIC_ACTION_HISTORY, and LOGIC_ACTION_CONDITION_HISTORY tables. |
| Custom data | check | EVENT and RECIPIENT tables. |
| Data blocking | check | |
| Column hashing | check | |
| Re-sync | check | |
| API configurable | check | API configuration |
| Priority-first sync | ||
| Fivetran data models | ||
| Private networking | ||
| Authorization via API | check |
Supported deployment models
We support the SaaS Deployment model for the connector.
Setup guide
Follow our step-by-step Typeform setup guide to connect Typeform with your destination using Fivetran connectors.
Schema information
This schema applies to all Typeform connections.
Sync overview
Fivetran uses Typeform REST APIs to sync your data.
We re-import the following tables and their related entities in full to retrieve all data:
FORM_*_HISTORYFORM_FIELD_INSIGHTFORM_INSIGHTTHEMEWORKSPACE
You can sync the FORM_INSIGHT and FORM_FIELD_INSIGHT tables only for Typeform accounts with a business or enterprise plan.
The Typeform API does not provide information about deleted records for the following tables and their related entities:
FORM_FIELD_INSIGHTFORM_INSIGHTTHEMEWORKSPACE
However, as we re-import the complete tables, we can capture the deleted records. We add a _fivetran_deleted column in the destination tables to mark the records that were deleted in your source.
We perform incremental syncs to retrieve only the new responses from the RESPONSE table and related entities.
We cannot capture deleted responses because the Typeform API doesn’t provide any information about deleted records of the RESPONSE table.
Sync note
For the FORM_*_HISTORY tables, we use the lastUpdatedAt value in the FORM table's response as the _fivetran_start value.
For example, if you update a form's logic at 2021-07-27T08:51:00.000Z and then update the form's field at 2021-07-27T08:52:00.000Z, then during the sync, we consider 2021-07-27T08:52:00.000Z as the _fivetran_start value for the records of the FORM_FIELD_HISTORY and FORM_LOGIC_HISTORY tables.