Integrations · DevelopmentConnect Netlify to Well
Link Netlify deploy, site, and form submission to the customer and revenue context they affect.
What Well pulls from Netlify
Netlify feeds deploy, site, form submission into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Netlify’s access.
| From Netlify | In Well | Relation | |
|---|---|---|---|
| Deploy | Build record | Captures as | |
| Site | Workspace context | Groups under | |
| Form submission | Lead record | Becomes |
- Sync mode
- MCP hybrid
- Refresh
- live + reconciliation reads
- Direction
- Netlify → Well
What Well does with your Netlify connection
Connect
Connect Netlify over OAuth (MCP DCR): Well registers a client through Netlify's OAuth Dynamic Client Registration and you approve on Netlify's side, so the password never reaches Well; Well holds only a scoped token it can refresh.
Sync
Well brings deploy, site, and form submission in from Netlify 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 Netlify entity into build 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 Netlify lands in the workspace as build record, workspace context, and lead record you can search, chart, and automate.
Questions Netlify unlocks
Ask in plain language. Well answers from your connected Netlify connection, resolved against the rest of your stack.
Ask anything about your Netlify connection
Ask about your Netlify connection…
Connect Netlify in three steps
- 01
Authorise Netlify via MCP
From Well's Connections panel, search for Netlify and click Connect. Well discovers Netlify's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on Netlify's side. No client credentials to paste.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
- MCP servernetlify-mcp.netlify.app/mcp
- 02
Map your entities
Well's MCP client discovers deploy, site, and form submission from Netlify that Netlify'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 Netlify records. Because Netlify 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 Netlify records happens in the background.
How Netlify stays secure with Well
Well connects to Netlify's MCP server (netlify-mcp.netlify.app/mcp) via the Model Context Protocol. The MCP server itself handles credential issuance through OAuth Dynamic Client Registration; Well never sees a long-lived Netlify secret. Tokens are scoped to the deploy, site, and form submission Netlify exposes and refreshed server-side. Reads only, Well cannot modify or delete Netlify records.
- granted
Read Netlify records
Resources the Netlify MCP server exposes, scoped by your OAuth approval.
- granted
Resolve deploy, site, and form submission across your stack
Match identifiers in Netlify against the same entities your other connected tools expose, so each record carries cross-tool context.
- refused
Modify or delete Netlify records
Not granted; Netlify is read-only in Well. Write-back is opt-in per connector when a write surface exists.
- refused
Store Netlify passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
Frequently asked questions about Netlify and Well
From Well, open Connections, find Netlify, and click Connect. Well discovers the OAuth metadata at netlify-mcp.netlify.app/mcp/.well-known/oauth-authorization-server, registers a client on the fly via Dynamic Client Registration, and walks you through the authorize prompt on Netlify's side. No client_id or client_secret to paste; the handshake takes roughly a minute.
Well brings in deploy, site, and form submission from Netlify and reshapes each entity into your workspace: deploy becomes build record; site becomes workspace context. Every record arrives with the source identifier preserved, so Netlify stays the source of truth while Well lets you query the data alongside the rest of your stack.
Well links Netlify activity (issues, commits, deploys, runs) to the customer accounts in your CRM that originated each request. A bug report from a top-revenue customer shows that revenue context inline; a deploy mentions the customer-facing features that just shipped.
Well watches for updates to deploys and applies them on the next sync, preserving the original workspace identifier so anything downstream (records tables, conversation history, agent runs) keeps pointing at the right build record. Edits flow in incrementally; nothing is duplicated, and the Netlify source identifier is retained on every revision.
Well combines live Netlify events with periodic reconciliation reads of deploy, site, and form submission. New rows appear within seconds when Netlify pushes them; periodic reads catch anything a push missed. The first connect backfills history from Netlify in the background.
Open Connections > Netlify in Well and click Disconnect. Well calls Netlify's token revocation endpoint and stops calling Netlify immediately on its side; provider-side propagation to Netlify's admin panel varies by provider. The deploy, site, and form submission Well already synced stay in your workspace by default; ask Support to purge them if your compliance flow requires it.
Netlify 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 Netlify
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 Netlify?
Connect once. Every deploy, site, form submission from Netlify becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.