Typeform (v1) | Stitch Documentation

Typeform is supported by the Singer community
This integration is powered by Singer's Typeform tap. For support, visit the GitHub repo or join the Singer Slack.

Typeform is in Open Beta
Typeform is currently in Open Beta. The info in this article is subject to change.

Typeform integration summary

Stitch’s Typeform integration replicates data using the Typeform Responses API. Refer to the Schema section for a list of objects available for replication.

Typeform feature snapshot

A high-level look at Stitch's Typeform integration, including release status, useful links, and the features supported in Stitch.

STITCH
Release Status	Open Beta	Supported By	Singer Community
Stitch Plan	Free	Singer GitHub Repository	Typeform Repository
DATA SELECTION
Table Selection	Supported	Column Selection	Supported
REPLICATION SETTINGS
Anchor Scheduling	Supported	Advanced Scheduling	Unsupported
Table-level Reset	Unsupported	Configurable Replication Methods	Unsupported
TRANSPARENCY
Extraction Logs	Supported	Loading Reports	Supported

Connecting Typeform

Step 1: Generate a Typeform API token

Sign into your Typeform account.
Click the user menu (your icon) in the top right corner of the page.
In the menu, click My Account.
On the page that displays, click Personal tokens on the left side of the page.
The Personal tokens page will display. Click the Generate a new token button.
Enter a Token name. For example: Stitch
In the Scopes section, click Custom scopes.
In the list that displays, select the Read option for the following permissions:
- Accounts
- Forms
- Images
- Responses
- Themes
- Workspaces
Click Generate token.
A window with the token will display. Copy the token somewhere handy, as you’ll need it to complete the setup. Note: Typeform will only display the token once. If you close this window, you’ll need to re-generate the token.

Step 2: 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.

In your Typeform account, navigate back to your workspaces.
On the workspace page, click on a form you want to include in Stitch. This should open the form’s edit page.
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.
Copy the form ID somewhere handy.
Repeat steps 2-4 for every form you want to include in Stitch.

Step 3: Add Typeform as a Stitch data source

Sign into your Stitch account.
On the Stitch Dashboard page, click the Add Integration button.
Click the Typeform icon.
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.
In the API Token field, paste the Typeform API token you generated in Step 1.
In the Forms field, enter a comma-separated list of the form IDs you retrieved in Step 2. For example:
- Single form: FrZ6iD
- Multiple forms: FrZ6iD,f8nzFM
In the Incremental Range dropdown, select the type of data aggregation you want Stitch to use:
- Daily: Data will be aggregated by day.
- Hourly: Data will be aggregated by hour.

Step 4: Define the historical sync

The Sync Historical Data setting will define the starting date for your Typeform integration. This means that:

For tables using Incremental Replication, data equal to or newer than this date will be replicated to your data warehouse.
For tables using Full Table Replication, all data - including records that are older, 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 guide.

Step 5: Create a replication schedule

Replication schedules affect the time Extraction begins, not the time to data loaded. Refer to the Replication Scheduling documentation for more information.

In the Replication Frequency section, you’ll create the integration’s replication schedule. 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:

To keep your row usage low, consider setting the integration to replicate less frequently. See the Understanding and Reducing Your Row Usage guide for tips on reducing your usage.

Step 6: Set tables and columns to replicate

To complete the setup, you’ll need to select the tables and columns you want to replicate to your data warehouse.

Check out the Schema section to learn more about the available tables in Typeform and how they replicate.

In the list of tables that displays - or in the Tables to Replicate tab, if you skipped this step during setup - locate a table you want to replicate.
To track a table, click the checkbox next to the table’s name. A green checkmark means the table is set to replicate.
To track a column, click the checkbox next to the column’s name. A green checkmark means the column is set to replicate.
Repeat this process for all the tables and columns you want to replicate.
When finished, click the Finalize Your Selections button at the bottom of the screen to save your selections.

Note: If you change these settings while a replication job is still in progress, they will not be used until the next job starts.

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.

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 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.

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 schemas

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 for your destination for more info.

answers

View table schema on GitHub

Replication Method :	Key-based Incremental	Replication Key :	landing_id
Primary Key :	landing_id : question_id	API endpoint :	Retrieve responses

The answers table contains info about the answers submitted for the forms specified in the Integration Settings page.

answers table schema

landing_id
STRING

The ID for the form landing.

Reference:

landings.landing_id

question_id
STRING

The question ID.

Reference:

questions.question_id

answer
STRING

data_type
STRING

The field type of the question. Possible values are:

choice
choices
date
email
url
file_url
number
boolean
text
payment

ref
STRING

type
STRING

landings

View table schema on GitHub

Replication Method :	Key-based Incremental	Replication Key :	submitted_at
Primary Key :	landing_id	API endpoint :	Retrieve responses

The landings table contains info about form landings. Depending on the Incremental Range setting defined in the Integration Settings page, data may be aggregated on a daily or hourly basis.

landings table schema

landing_id
STRING

The landing ID.

Reference:

answers.landing_id

submitted_at
DATE-TIME

The time that the form response was submitted in ISO 8601 format, UTC time.

browser
STRING

The browser used in the landing.

hidden
STRING

landed_at
DATE-TIME

The time of the form landing in ISO 8601 format, UTC time.

network_id
STRING

The IP address of the client.

platform
STRING

The platform used in the landing, derived from user_agent.

referer
STRING

If applicable, the referrer used in the landing.

token
STRING

user_agent
STRING

The user agent used in the landing.

questions

View table schema on GitHub

Replication Method :	Full Table	Primary Key :	form_id : question_id
API endpoint :	Retrieve form

The questions table contains a list of question titles and IDs that can be used to link to answers.

questions table schema

form_id
STRING

The form ID.

question_id
STRING

The question ID.

Reference:

answers.question_id

ref
STRING

The readable name used to reference the question field.

title
STRING

The unique name assigned to the field on the form.

Questions? Feedback?

Did this article help? If you have questions or feedback, feel free to submit a pull request with your suggestions, open an issue on GitHub, or reach out to us.

Related	Troubleshooting
Destination & Integration Compatibility Replication Scheduling Syncing Historical SaaS Data Resetting Replication Keys Nested Data Structures & Row Count Impact	Third-Party Downtime Understanding & Reducing Your Usage Re-Authorizing Integrations Replication Issues