# Typeform (v2)
Information note **Typeform extraction is supported by Stitch**
This integration is powered by [Singer's](https://www.singer.io/) Typeform tap and certified by Stitch. [Check out and contribute to the repo on GitHub](https://github.com/singer-io/tap-typeform).
For support, contact [Support](https://community.qlik.com/t5/Support/ct-p/qlikSupport).
## Typeform integration summary
Stitch’s Typeform integration replicates data using the [Typeform Create](https://developer.typeform.com/create/) and [Responses](https://developer.typeform.com/responses/) APIs. Refer to the [Schema](https://help.qlik.com/en-US/stitch/integrations/saas/typeform#schema) section for a list of objects available for replication.
## Typeform feature snapshot
A high-level look at Stitch's Typeform (v2) integration, including release status, useful links, and the features supported in Stitch.
| **STITCH** | | | |
| --- | --- | --- | --- |
| **[Release status](https://help.qlik.com/en-US/stitch/integrations/identify-an-integration-version)** | Released on September 29, 2022 | **Supported by**
the Info icon
Indicates if the integration is supported by Stitch or the Singer community. | [Stitch](https://community.qlik.com/t5/Support/ct-p/qlikSupport) |
| **Stitch plan**
the Info icon
The type of Stitch plan required to use the integration. | Standard | **[API availability](https://help.qlik.com/en-US/stitch/developers/stitch-connect/guides/source-destination-reference)**
the Info icon
Indicates if the integration is available as a source in Stitch Connect. | the Success icon
This version of the integration is available via the API.
Indicates if Replication Methods can be defined by you for tables in the integration. | the Remove icon
Configurable Replication Methods are not supported for this integration. Stitch will use pre-defined replication methods for tables you set to replicate.
The ability to select individual tables for replication in the Stitch interface. If table selection is unavailable, all tables and all the columns they contain will be set to replicate by default. | the Success icon
This feature is supported for this version of the integration.
Supported | **Column selection**
the Info icon
The ability to select individual columns for replication in the Stitch interface. If column selection is unavailable, all columns will be set to replicate by default. | the Success icon
This feature is supported for this version of the integration.
Supported |
| **Select all**
the Info icon
Indicates if the integration supports selecting all available tables and columns. | the Success icon
Reports detailing the Loading phase of the replication process for a given integration. Includes the number of rows loaded for each table and error info, should an error occur. | the Success icon
This feature is supported for this version of the integration.
Supported |
## Connecting Typeform
### Step 1: Retrieve Typeform form IDs
Stitch’s Typeform will retrieve data only for the forms you specify in the Integration Settings page. In this step, you’ll retrieve the IDs of the forms you want Stitch to replicate.
1. In your Typeform account, navigate back to your workspaces.
2. On the workspace page, click on a form you want to include in Stitch. This should open the form’s edit page.
3. Look at the URL of the page in your browser. It should be similar to `https://admin.typeform.com/form/FrZ6iD/create`. The string between `form/` and `/create` is the form’s ID. In this example, the ID is `FrZ6iD`.
4. Copy the form ID somewhere handy.
5. Repeat steps 2-4 for every form you want to include in Stitch.
### Step 2: Add Typeform as a Stitch data source
1. [Sign into your Stitch account](https://app.stitchdata.com/).
2. On the Stitch Dashboard page, click the **Add Integration** button.
3. Click the **Typeform** icon.
4. Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your destination.
For example, the name “Stitch Typeform” would create a schema called `stitch_typeform` in the destination. **Note**: Schema names cannot be changed after you save the integration.
5. In the **Forms** field, enter a comma-separated list of the form IDs you retrieved in [Step 2](https://help.qlik.com/en-US/stitch/integrations/saas/typeform#retrieve-typeform-form-ids). For example:
* **Single form**: `FrZ6iD`
* **Multiple forms**: `FrZ6iD,f8nzFM`
### Step 3: Define the historical replication start date
The Sync Historical Data setting defines the starting date for your Typeform integration. This means that data **equal to or newer than this date** will be replicated to your data warehouse.
Change this setting if you want to replicate data beyond Typeform’s default setting of **1 year**. For a detailed look at historical replication jobs, check out the [Syncing Historical SaaS Data](https://help.qlik.com/en-US/stitch/replication/syncing-historical-saas-data-resetting-replication-keys) guide.
### Step 4: Create a replication schedule
Information note Replication schedules affect the time Extraction begins, not the time to data loaded. Refer to the [Replication Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling) documentation for more information.
In the **Replication Frequency** section, you’ll create the integration’s [replication schedule](https://help.qlik.com/en-US/stitch/replication/replication-scheduling). An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.
Typeform integrations support the following replication scheduling methods:
* [Replication Frequency](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/replication-frequency)
* [Anchor Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/anchor-scheduling)
* [Advanced Scheduling using Cron](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/advanced-scheduling) (Advanced or Premium plans only)
To keep your row usage low, consider setting the integration to replicate less frequently. See the [Understanding and Reducing Your Row Usage guide](https://help.qlik.com/en-US/stitch/getting-started/understanding-stitch-usage) for tips on reducing your usage.
### Step 5: Authorize Stitch
1. Next, you’ll be prompted to log into your Typeform account and approve Stitch’s access to your data. **Note that we will only ever read your data.**
2. Click **Authorize**.
3. Sign in with your Typeform account.
4. Click **Accept**.
### Step 6: Set objects to replicate
Information note **Is an object missing or not replicating?** Verify that the object meets the requirements for [selection](https://help.qlik.com/en-US/stitch/replication/extractions/data-selection/setting-tables-and-columns-to-replicate#selection-requirements) and [replication](https://help.qlik.com/en-US/stitch/replication/extractions/data-selection/setting-tables-and-columns-to-replicate#replication-requirements).
The last step is to select the tables and columns you want to replicate. [Learn about the available tables for this integration.](https://help.qlik.com/en-US/stitch/integrations/saas/typeform#schema)
**Note**: If a replication job is currently in progress, new selections won’t be used until the next job starts.
* Selection options
* Individual tables and columns
* All tables and columns
For Typeform integrations, you can select:
1. **Individual tables and columns**
2. **All tables and columns**
Click the tabs to view instructions for each selection method.
1. In the integration’s **Tables to Replicate tab**, locate a table you want to replicate.
2. To track a table, click the **checkbox** next to the table’s name. A blue checkmark means the table is set to replicate.
3. To track a column, click the **checkbox** next to the column’s name. A blue checkmark means the column is set to replicate.
4. Repeat this process for all the tables and columns you want to replicate.
5. When finished, click the **Finalize Your Selections** button at the bottom of the screen to save your selections.
Information note **Important**: Using the **Select All** feature will overwrite any previous selections. However, selections aren’t final until **Finalize Your Selections** is clicked. Clicking **Cancel** will restore your previous selections. Refer to the [Select All guide](https://help.qlik.com/en-US/stitch/replication/extractions/data-selection/setting-tables-and-columns-to-replicate#set-all-data-to-replicate) for more info about this feature.
1. Click into the integration from the Stitch Dashboard page.
2. Click the **Tables to Replicate** tab.
3. In the list of tables, click the box next to the **Table Names** column.
4. In the menu that displays, click **Track all Tables and Fields**:
The Track all Tables and Fields menu in the Tables to Replicate tabThe Track all Tables and Fields menu in the Tables to Replicate tab
5. Click the **Finalize Your Selections** button at the bottom of the page to save your data selections.
### Initial and historical replication jobs
After you finish setting up Typeform, its **Sync Status** may show as **Pending** on either the Stitch Dashboard or in the Integration Details page.
For a new integration, a **Pending** status indicates that Stitch is in the process of scheduling the initial replication job for the integration. **This may take some time to complete.**
Information note
**Initial replication jobs with Anchor Scheduling**
If using Anchor Scheduling, an initial replication job may not kick off immediately. This depends on the selected Replication Frequency and Anchor Time. Refer to the [Anchor Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling#job-scheduling-and-anchor-times) documentation for more information.
#### Free historical data loads
The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota.
Information note **Replication will continue after the seven days are over**. If you’re no longer interested in this source, be sure to **pause** or **delete** the integration to prevent unwanted usage.
## Typeform table reference
Information note
**Schemas and versioning**
Schemas and naming conventions can change from version to version, so we recommend verifying your integration’s version before continuing.
The schema and info displayed below is for **version 2** of this integration.
This is the latest version of the Typeform integration.
Information note
**Table and column names in your destination**
Depending on your destination, table and column names may not appear as they are outlined below.
For example: Object names are lowercased in Redshift (`CusTomERs` > `customers`), while case is maintained in PostgreSQL destinations (`CusTomERs` > `CusTomERs`). Refer to the [Loading Guide](https://help.qlik.com/en-US/stitch/replication/loading/destination-guides) for your destination for more info.
### answers
The `answers` table contains info about the answers submitted for the forms specified in the Integration Settings page. **Note**: There is no replication key for this table, it uses the replication key `submitted_at` from its parent stream [`submitted_landings`](https://help.qlik.com/en-US/stitch/integrations/saas/typeform#submitted-landings).
| **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Key-based Incremental |
| --- | --- |
| **Primary Keys ** | landing\_id
question\_id |
| **Useful links** | [Typeform documentation](https://developer.typeform.com/responses/ "Opens in new tab: Typeform documentation")
[answers schema on GitHub](https://github.com/singer-io/tap-typeform/blob/master/tap_typeform/schemas/answers.json "Opens in new tab: answers schema on GitHub")
[Typeform API method](https://developer.typeform.com/responses/reference/retrieve-responses "Opens in new tab: Typeform API method") |
answers table foreign keys
| Join answers with | on |
| --- | --- |
| [submitted_landings](https://help.qlik.com/en-US/stitch/integrations/saas/typeform#submitted-landings) | ``` answers.landing_id = submitted_landings.landing_id ``` |
| [unsubmitted_landings](https://help.qlik.com/en-US/stitch/integrations/saas/typeform#unsubmitted-landings) | ``` answers.landing_id = unsubmitted_landings.landing_id ``` |
| [questions](https://help.qlik.com/en-US/stitch/integrations/saas/typeform#questions) | ``` answers.question_id = questions.question_id ``` |
answers table schema
| **\_sdc\_form\_id**
STRING |
| --- |
| **answer**
STRING |
| **data\_type**
STRING |
| **landing\_id**
STRING |
| **question\_id**
STRING |
| **ref**
STRING |
| **submitted\_at**
DATE-TIME |
| **type**
STRING |
### forms
The `forms` table contains info about the forms (public and private) that are accesible by the user who authorized the integration in Stitch.
| **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Key-based Incremental |
| --- | --- |
| **Primary Key ** | id |
| **Replication Key ** | last\_updated\_at |
| **Useful links** | [Typeform documentation](https://developer.typeform.com/responses/ "Opens in new tab: Typeform documentation")
[forms schema on GitHub](https://github.com/singer-io/tap-typeform/blob/master/tap_typeform/schemas/forms.json "Opens in new tab: forms schema on GitHub")
[Typeform API method](https://developer.typeform.com/create/reference/retrieve-forms/ "Opens in new tab: Typeform API method") |
forms table foreign keys
| Join forms with | on |
| --- | --- |
| [questions](https://help.qlik.com/en-US/stitch/integrations/saas/typeform#questions) | ``` forms.id = questions.form_id ``` |
forms table schema
| **\_links**
OBJECT
This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand \_links
display
STRING
|
| --- |
| **created\_at**
DATE-TIME |
| **id**
STRING |
| **last\_updated\_at**
STRING |
| **self**
OBJECT
This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand self
href
STRING
|
| **settings**
OBJECT
This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand settings
is_public
BOOLEAN
is_trial
BOOLEAN
|
| **theme**
OBJECT
This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand theme
href
STRING
|
| **title**
STRING |
| **type**
STRING |
### questions
The `questions` table contains a list of question titles and IDs that can be used to link to [`answers`](https://help.qlik.com/en-US/stitch/integrations/saas/typeform#answers).
| **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Full Table |
| --- | --- |
| **Primary Keys ** | form\_id
question\_id |
| **Useful links** | [questions schema on GitHub](https://github.com/singer-io/tap-typeform/blob/master/tap_typeform/schemas/questions.json "Opens in new tab: questions schema on GitHub")
[Typeform API method](https://developer.typeform.com/create/reference/retrieve-form/ "Opens in new tab: Typeform API method") |
questions table foreign keys
| Join questions with | on |
| --- | --- |
| [forms](https://help.qlik.com/en-US/stitch/integrations/saas/typeform#forms) | ``` questions.form_id = forms.id ``` |
| [answers](https://help.qlik.com/en-US/stitch/integrations/saas/typeform#answers) | ``` questions.question_id = answers.question_id ``` |
questions table schema
| **attachment**
OBJECT
This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand attachment
href
STRING
properties
OBJECT
description
STRING
scale
NUMBER
type
STRING
|
| --- |
| **field\_type**
STRING |
| **form\_id**
STRING |
| **id**
STRING |
| **layout**
OBJECT
This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand layout
attachment
OBJECT
href
STRING
properties
OBJECT
description
STRING
scale
NUMBER
type
STRING
placement
STRING
type
STRING
|
| **name**
STRING |
| **options**
ARRAY
This is a nested data structure. If your destination doesn't natively support nested data, attributes will be denested into a subtable. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand options
label
STRING
|
| **properties**
OBJECT
This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand properties
allow_multiple_selection
BOOLEAN
allow_other_choice
BOOLEAN
alphabetical_order
BOOLEAN
button_text
STRING
choices
ARRAY
attachment
OBJECT
href
STRING
type
STRING
label
STRING
ref
STRING
currency
STRING
default_country_code
STRING
description
STRING
fields
ARRAY
hide_marks
BOOLEAN
labels
OBJECT
center
STRING
left
STRING
right
STRING
price
OBJECT
type
STRING
value
STRING
randomize
BOOLEAN
separator
STRING
shape
STRING
|
| **question\_id**
STRING |
| **ref**
STRING |
| **required**
STRING |
| **sub\_questions**
ARRAY
This is a nested data structure. If your destination doesn't natively support nested data, attributes will be denested into a subtable. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand sub\_questions
question_id
STRING
ref
STRING
title
STRING
|
| **title**
STRING |
| **type**
STRING |
| **validations**
OBJECT
This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>.
Click to expand validations
max_length
INTEGER
max_selection
INTEGER
max_value
INTEGER
min_selection
INTEGER
min_value
INTEGER
required
BOOLEAN
|
### submitted\_landings
The `submitted_landings` table contains info about submitted form landings.
**Note**: Data related to a form landing can be retrieved twice, once in `unsubmitted_landings` when it is unsubmitted and once in `submitted_landings` when it is submitted. In this case, they will have different bookmarks.
| **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Key-based Incremental |
| --- | --- |
| **Primary Key ** | landing\_id |
| **Replication Key ** | submitted\_at |
| **Useful links** | [submitted_landings schema on GitHub](https://github.com/singer-io/tap-typeform/blob/master/tap_typeform/schemas/submitted_landings.json "Opens in new tab: submitted_landings schema on GitHub")
[Typeform API method](https://developer.typeform.com/responses/reference/retrieve-responses "Opens in new tab: Typeform API method") |
submitted\_landings table foreign keys
| Join submitted\_landings with | on |
| --- | --- |
| [answers](https://help.qlik.com/en-US/stitch/integrations/saas/typeform#answers) | ``` submitted_landings.landing_id = answers.landing_id ``` |
| [unsubmitted_landings](https://help.qlik.com/en-US/stitch/integrations/saas/typeform#unsubmitted-landings) | ``` submitted_landings.landing_id = unsubmitted_landings.landing_id ``` |
submitted\_landings table schema
| **\_sdc\_form\_id**
STRING |
| --- |
| **browser**
STRING |
| **hidden**
STRING |
| **landed\_at**
DATE-TIME |
| **landing\_id**
STRING |
| **network\_id**
STRING |
| **platform**
STRING |
| **referer**
STRING |
| **submitted\_at**
DATE-TIME |
| **tags**
ARRAY
This is a nested data structure. If your destination doesn't natively support nested data, attributes will be denested into a subtable. <a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'>Learn more</a>. |
| **token**
STRING |
| **user\_agent**
STRING |
### unsubmitted\_landings
The `unsubmitted_landings` table contains info about unsubmitted form landings.
**Note**: Data related to a form landing can be retrieved twice, once in `unsubmitted_landings` when it is unsubmitted and once in `submitted_landings` when it is submitted. In this case, they will have different bookmarks.
| **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Key-based Incremental |
| --- | --- |
| **Primary Key ** | landing\_id |
| **Replication Key ** | landed\_at |
| **Useful links** | [unsubmitted_landings schema on GitHub](https://github.com/singer-io/tap-typeform/blob/master/tap_typeform/schemas/unsubmitted_landings.json "Opens in new tab: unsubmitted_landings schema on GitHub")
[Typeform API method](https://developer.typeform.com/responses/reference/retrieve-responses "Opens in new tab: Typeform API method") |
unsubmitted\_landings table foreign keys
| Join unsubmitted\_landings with | on |
| --- | --- |
| [answers](https://help.qlik.com/en-US/stitch/integrations/saas/typeform#answers) | ``` unsubmitted_landings.landing_id = answers.landing_id ``` |
| [submitted_landings](https://help.qlik.com/en-US/stitch/integrations/saas/typeform#submitted-landings) | ``` unsubmitted_landings.landing_id = submitted_landings.landing_id ``` |
unsubmitted\_landings table schema
| **\_sdc\_form\_id**