Integrations · DevelopmentConnect Webflow to Well
Sync Webflow site content, forms, and CMS collections into Well. Link page activity and form submissions to the customers and prospects they relate to.
What Well pulls from Webflow
Webflow feeds CMS item, site, form submission into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Webflow’s access.
| From Webflow | In Well | Relation | |
|---|---|---|---|
| CMS item | Indexed record | Becomes | |
| Site | Workspace context | Groups under | |
| Form submission | Lead record | Feeds |
- Sync mode
- MCP hybrid
- Refresh
- live + reconciliation reads
- Direction
- Webflow → Well
What Well does with your Webflow connection
Connect
Connect Webflow over OAuth (MCP DCR): Well registers a client through Webflow's OAuth Dynamic Client Registration and you approve on Webflow's side, so the password never reaches Well; Well holds only a scoped token it can refresh.
Sync
Well brings CMS item, site, and form submission in from Webflow on live events backed by periodic reconciliation reads. The first sync backfills history in the background and the connection stays live after.
Enrich
Well resolves each Webflow entity into indexed record, workspace context, and lead record, assigns categories, and links every record to an audit trail across the rest of your connected tools.
Available
Your data from Webflow lands in the workspace as indexed record, workspace context, and lead record you can search, chart, and automate.
Questions Webflow unlocks
Ask in plain language. Well answers from your connected Webflow connection, resolved against the rest of your stack.
Ask anything about your Webflow connection
Ask about your Webflow connection…
Connect Webflow in three steps
- 01
Authorise Webflow via MCP
From Well's Connections panel, search for Webflow and click Connect. Well discovers Webflow's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on Webflow's side. No client credentials to paste.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
- MCP servermcp.webflow.com/mcp
- 02
Map your entities
Well's MCP client discovers CMS item, site, and form submission from Webflow that Webflow's MCP server exposes and brings them into your workspace using the canonical mappings defined in Well's data-views layer. You can inspect the workspace data model from Settings > Data Model.
- Mappingpreconfigured by Well
- 03
Use the data
Ask questions in conversation, build records tables, or let agents act on Webflow records. Because Webflow ships through MCP, Well treats every entity it exposes as queryable graph state alongside the rest of your connected tools.
- First syncstarts as soon as connect completes
MCP handshake typically completes under a minute on warm connections. Resource enumeration runs immediately after; full backfill of historical Webflow records happens in the background.
How Webflow stays secure with Well
Well connects to Webflow's MCP server (mcp.webflow.com/mcp) via the Model Context Protocol. The MCP server itself handles credential issuance through OAuth Dynamic Client Registration; Well never sees a long-lived Webflow secret. Tokens are scoped to the CMS item, site, and form submission Webflow exposes and refreshed server-side. Reads only, Well cannot modify or delete Webflow records.
- granted
Read Webflow records
Resources the Webflow MCP server exposes, scoped by your OAuth approval.
- granted
Resolve CMS item, site, and form submission across your stack
Match identifiers in Webflow against the same entities your other connected tools expose, so each record carries cross-tool context.
- refused
Modify or delete Webflow records
Not granted; Webflow is read-only in Well. Write-back is opt-in per connector when a write surface exists.
- refused
Store Webflow passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
Frequently asked questions about Webflow and Well
From Well, open Connections, find Webflow, and click Connect. Well discovers the OAuth metadata at mcp.webflow.com/mcp/.well-known/oauth-authorization-server, registers a client on the fly via Dynamic Client Registration, and walks you through the authorize prompt on Webflow's side. No client_id or client_secret to paste; the handshake takes roughly a minute.
Well brings in CMS item, site, and form submission from Webflow and reshapes each entity into your workspace: CMS item becomes indexed record; site becomes workspace context. Every record arrives with the source identifier preserved, so Webflow stays the source of truth while Well lets you query the data alongside the rest of your stack.
Each Webflow form submission, page event, and CMS update is linked to the matching prospect or customer in your CRM. Ask "which Webflow forms my top prospects filled in this week" and Well joins the form data to the contact record without a separate export.
Yes. Webflow form submissions are indexed in your workspace as lead record, so questions like "show me last week's form submissions from Webflow" return them with the original Webflow link, the workspace context, and any related records (counterparty, period, attached document) joined inline.
Well combines live Webflow events with periodic reconciliation reads of CMS item, site, and form submission. New rows appear within seconds when Webflow pushes them; periodic reads catch anything a push missed. The first connect backfills history from Webflow in the background.
Open Connections > Webflow in Well and click Disconnect. Well calls Webflow's token revocation endpoint and stops calling Webflow immediately on its side; provider-side propagation to Webflow's admin panel varies by provider. The CMS item, site, and form submission Well already synced stay in your workspace by default; ask Support to purge them if your compliance flow requires it.
Webflow records are stored in the region Well operates for your workspace. Specific region details and the steps to change region are available from Support. See /privacy for the current data-handling policy.
Pairs well with Webflow
More in Development
Cloudflare
Connect Cloudflare to Well to sync development tools and infrastructure data.
Context7
Connect Context7 to Well over its MCP server so your agents can reach it, with no structured data sync.
DocFork
Connect DocFork to Well over its MCP server so your agents can reach it, with no structured data sync.
GitLab
Connect GitLab to Well to sync development tools and infrastructure data.
Popular cross-category
Ready to connect Webflow?
Connect once. Every CMS item, site, form submission from Webflow becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.