Integrations · Development

Connect Contentful to Well

Link Contentful document to the customer and revenue context they affect.

What Well pulls from Contentful

Contentful feeds document into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Contentful’s access.

From Contentful		In Well	Relation
Document		Source document	Captures as

Sync mode: MCP hybrid
Refresh: live + reconciliation reads
Direction: Contentful → Well

What Well does with your Contentful connection

Connect

Connect Contentful over OAuth (MCP DCR): Well registers a client through Contentful's OAuth Dynamic Client Registration and you approve on Contentful's side, so the password never reaches Well; Well holds only a scoped token it can refresh.

Sync

Well brings document in from Contentful through live reads, backed by a periodic reconciliation pass. The first sync backfills history in the background and the connection stays live after.

Enrich

Well resolves each Contentful entity into source document, assigns categories, and links every record to an audit trail across the rest of your connected tools.

Available

Your data from Contentful lands in the workspace as source document you can search, chart, and automate.

Questions Contentful unlocks

Ask in plain language. Well answers from your connected Contentful connection, resolved against the rest of your stack.

Ask Well

Ask anything about your Contentful connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your Contentful connection…

1 agent skill runs on Contentful.

Well lists Contentful in the connection check every skill runs before it answers. No skill reads it for a figure yet.

Connects and checks Contentful

Check your connections

See what is connected, what is syncing, and what is missing.

Browse all skills

Connect Contentful in three steps

01
Authorise Contentful via MCP
From Well's Connections panel, search for Contentful and click Connect. Well discovers Contentful's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on Contentful's side. No client credentials to paste.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
02
Map your entities
Well's MCP client discovers document from Contentful that Contentful'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 Contentful records. Because Contentful 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 Contentful records happens in the background.

How Contentful stays secure with Well

Well connects to Contentful's MCP server via the Model Context Protocol. The MCP server itself handles credential issuance through OAuth Dynamic Client Registration; Well never sees a long-lived Contentful secret. Tokens are scoped to the document Contentful exposes and refreshed server-side. Reads only, Well cannot modify or delete Contentful records.

OAuth (MCP DCR)Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requests

Read Contentful records
Resources the Contentful MCP server exposes, scoped by your OAuth approval.
granted
Resolve document across your stack
Match identifiers in Contentful against the same entities your other connected tools expose, so each record carries cross-tool context.
granted
Modify or delete Contentful records
Not granted; Contentful is read-only in Well. Write-back is opt-in per connector when a write surface exists.
refused
Store Contentful passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
refused

Disconnect any time from Well settings or Contentful’s admin panel.

Frequently asked questions about Contentful and Well

How do I connect Contentful to Well, and how long does it take?

From Well, open Connections, find Contentful, and click Connect. Well discovers the OAuth metadata from Contentful's MCP server, registers a client on the fly via Dynamic Client Registration, and walks you through the authorize prompt on Contentful's side. No client_id or client_secret to paste; the handshake takes roughly a minute.

What does Well pull into the workspace from Contentful?

Well brings in document from Contentful and reshapes each entity into your workspace: document becomes source document. Every record arrives with the source identifier preserved, so Contentful stays the source of truth while Well lets you query the data alongside the rest of your stack.

How does Well join Contentful incident history with the customers who experienced the impact?

Every Contentful incident, postmortem, or rollback event carries the affected services, which Well joins to the customer entities those services support. Asking "which customers were impacted by last Tuesday's incident" returns the list with severity, restoration time, and any open follow-up actions per customer.

How does Well match a document from Contentful to a source document in my workspace?

Each Contentful document is scored against the candidate source documents in your workspace on identifier overlap, amount or quantity match, date proximity, and counterparty resolution. Matches above the auto-link confidence threshold flow through cleanly; below the threshold they queue for a one-click human review, with the most likely source document prefilled and the Contentful source attached.

How often does Contentful sync with Well, and what triggers a refresh?

Well combines live Contentful events with periodic reconciliation reads of document. New rows appear within seconds when Contentful pushes them; periodic reads catch anything a push missed. The first connect backfills history from Contentful in the background.

Can I disconnect Contentful and what happens to the data Well already pulled?

Open Connections > Contentful in Well and click Disconnect. Well calls Contentful's token revocation endpoint and stops calling Contentful immediately on its side; provider-side propagation to Contentful's admin panel varies by provider. The document Well already synced stay in your workspace by default; ask Support to purge them if your compliance flow requires it.

How does Well protect what it pulls in from Contentful?

The Contentful records Well holds are encrypted at rest and handled in line with GDPR. See /privacy for the current data-handling policy.