Source connector

Typeform connector

Typeform integration for databases, warehouses and BI tools

Conversational forms and response analytics. Datrise captures Typeform entities such as forms, responses, questions, workspaces, and completion metrics, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Typeform Responses API authenticates with OAuth 2.0, personal access token, incremental runs key on since/until (submitted_at for completed responses, staged_at for partial responses), and Typeform caps calls at 2 requests per second per Typeform account for the Create and Responses APIs.

Of the 5 objects, 4 sync as upserts keyed on the primary key and 1 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `typeform_forms`) with a schema derived from the Typeform API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Typeform pipeline page, and join the waitlist to get the Typeform connector (Product analytics) with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Typeform data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
forms	typeform_forms	Upsert by primary key, incremental on updated-at
responses	typeform_responses	Upsert by primary key, incremental on updated-at
questions	typeform_questions	Upsert by primary key, incremental on updated-at
workspaces	typeform_workspaces	Upsert by primary key, incremental on updated-at
completion metrics	typeform_completion_metrics	Append-only, incremental by timestamp

Typeform API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	Typeform Responses API
Authentication	OAuth 2.0, personal access token — Server-to-server integrations typically use a Personal Access Token as a Bearer token; multi-account apps use OAuth 2.0 with granular scopes (e.g. `responses:read`) and require the `offline` scope to receive a refresh token.
Pagination	cursor — `page_size` defaults to 25 and maxes at 1,000; beyond that, page with the `before`/`after` response-token cursors (both exclusive) rather than an offset.
Rate limit	2 requests per second per Typeform account for the Create and Responses APIs
Incremental cursor	since/until (submitted_at for completed responses, staged_at for partial responses) — The `response_type` filter changes which timestamp field `since`/`until` filters on, so a connector pulling both `completed` and `partial` responses in one request cannot rely on a single consistent cursor semantic.
Webhooks	Yes — Typeform Webhooks (form_response event, fired on submission)
Bulk export	No
Deletes detectable	No

Official API reference

What bites when replicating Typeform

`page_size` tops out at 1,000 responses per call; a form with more than 1,000 total responses cannot be read in a single request and must be paged with `before`/`after` cursors.
Deleting responses via `DELETE /forms/{form_id}/responses` (up to 1,000 `included_response_ids` per call) is irreversible and returns HTTP 200 as soon as the request is accepted, before the deletion has necessarily completed, so a connector must re-query to confirm removal.
The Responses API has no delete event or tombstone: a response removed for GDPR Right-to-be-Forgotten simply stops appearing on the next `Retrieve responses` call, so incremental syncs based only on `since` will not learn that a previously-seen response_id was deleted.
The Create and Responses APIs share a 2 requests/second per-account limit, so paginating a large form's history and managing form metadata from the same integration can trip HTTP 429 if run concurrently.

Compare this against every other documented API

Popular destinations for Typeform

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Typeform connector FAQ

What Typeform data does the connector extract?: 5 objects: forms, responses, questions, workspaces and completion metrics. Each lands in its own table with types preserved; history-style objects (1: completion metrics) load as append-only streams.
Is the Typeform integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Typeform data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Typeform → destination pair has its own page with the object-to-table mapping.

Related Product analytics sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Typeform pipeline with guided onboarding

Join the waitlist to get priority access for Typeform integrations with guided setup, schema-aware mapping, and production-grade incremental sync.