Source connector

Webflow connector

Webflow integration for databases, warehouses and BI tools

Visual website builder with a structured CMS. Datrise captures Webflow entities such as collections, collection items, sites, fields, form submissions and publish events, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Webflow Data API v2 authenticates with OAuth 2.0, API key, incremental runs key on lastUpdated, and Webflow caps calls at 60 requests/minute per API token on Starter/Basic site plans, 120 requests/minute on CMS/eCommerce/Business, custom on Enterprise; Site Publish is separately capped at one successful publish per minute.

Of the 6 objects, 5 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 `webflow_collections`) with a schema derived from the Webflow 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 Webflow pipeline page, and join the waitlist to get the Webflow connector with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Webflow 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
collections	webflow_collections	Upsert by primary key, incremental on updated-at
collection items	webflow_collection_items	Upsert by primary key, incremental on updated-at
sites	webflow_sites	Upsert by primary key, incremental on updated-at
fields	webflow_fields	Upsert by primary key, incremental on updated-at
form submissions	webflow_form_submissions	Upsert by primary key, incremental on updated-at
publish events	webflow_publish_events	Append-only, incremental by timestamp

Webflow API: setup facts for the connector

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

API	Webflow Data API v2
Authentication	OAuth 2.0, API key — Requests carry a bearer token that is either a Site Token (generated in Site settings > Apps & integrations for single-site/internal use) or an OAuth 2.0 Authorization Code Grant token for marketplace apps.
Pagination	offset — List endpoints (e.g. collection items) take `limit` (max 100) and `offset` query parameters, echoed back with `total` in a `pagination` response object.
Rate limit	60 requests/minute per API token on Starter/Basic site plans, 120 requests/minute on CMS/eCommerce/Business, custom on Enterprise; Site Publish is separately capped at one successful publish per minute.
Incremental cursor	lastUpdated — Each CMS collection item carries a `lastUpdated` date-string field that can be used to identify records changed since a prior sync, though list endpoints do not expose a server-side `modified-since` filter.
Webhooks	Yes — Webflow webhooks (collection_item_created, collection_item_changed, collection_item_deleted, form_submission, site_publish, etc.)
Bulk export	No
Deletes detectable	Yes — The `collection_item_deleted` webhook event fires on removal; items also carry `isArchived`/`isDraft` boolean flags for soft states short of deletion.

Official API reference

What bites when replicating Webflow

The `limit` parameter on collection-item list endpoints hard-caps at 100 per page, so a 10,000-item collection needs 100 sequential `offset`-paged requests against the same per-token rate limit that everything else in the integration shares.
`isArchived` and `isDraft` are separate boolean flags from actual deletion; a connector that treats `isArchived: true` as "deleted" will misclassify content the editor only hid from the live site.
Rate limits (60 or 120 requests/minute depending on plan) apply per API token, not per site, so multiple integrations sharing one token silently compete for the same budget and can each see unexplained 429s.
Staged CMS items (draft/unpublished changes) and live items are separate endpoint families (`/collections/{id}/items` vs `/collections/{id}/items/live`), so a sync built only against staged items will not reflect what is actually published on the site.

Compare this against every other documented API

Popular destinations for Webflow

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

Webflow connector FAQ

What Webflow data does the connector extract?: 6 objects: collections, collection items, sites, fields, form submissions and publish events. Each lands in its own table with types preserved; history-style objects (1: publish events) load as append-only streams.
Is the Webflow 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 Webflow data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Webflow → destination pair has its own page with the object-to-table mapping.

Related sources

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

Early access

Launch your Webflow pipeline with guided onboarding

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