Integrations · Productivity

Connect Make to Well

Name: Make entities in Well
Creator: Well

Index Make scenario, run, and trigger so questions about workflow and execution log answer themselves in conversation.

What Well pulls from Make

Make feeds scenario, run, trigger into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Make’s access.

From Make	In Well	Relation
Scenario	Workflow	Indexes as
Run	Execution log	Captures as
Trigger	Event source	Fires from

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

What Well does with your Make connection

Connect

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

Sync

Well brings scenario, run, and trigger in from Make 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 Make entity into workflow, execution log, and event source, assigns categories, and links every record to an audit trail across the rest of your connected tools.

Available

Your data from Make lands in the workspace as workflow, execution log, and event source you can search, chart, and automate.

Questions Make unlocks

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

Ask Well

Ask anything about your Make connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your Make connection…

Connect Make in three steps

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

How Make stays secure with Well

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

OAuth (MCP DCR)Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requestsmcp.make.com

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

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

Frequently asked questions about Make and Well

From Well, open Connections, find Make, and click Connect. Well discovers the OAuth metadata at mcp.make.com/.well-known/oauth-authorization-server, registers a client on the fly via Dynamic Client Registration, and walks you through the authorize prompt on Make's side. No client_id or client_secret to paste; the handshake takes roughly a minute.

Well brings in scenario, run, and trigger from Make and reshapes each entity into your workspace: scenario becomes workflow; run becomes execution log. Every record arrives with the source identifier preserved, so Make stays the source of truth while Well lets you query the data alongside the rest of your stack.

Make items linked to engineering issues, deploys, or revenue commitments inherit those joins in your workspace. The product roadmap question "what's blocking enterprise rollout this quarter" returns the Make items, the engineering work they depend on, and the customers waiting on the outcome, all in one answer.

Yes. Make triggers are indexed in your workspace as event source, so questions like "show me last week's triggers from Make" return them with the original Make link, the workspace context, and any related records (counterparty, period, attached document) joined inline.

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

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

Make 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.