Integrations · Development

Connect Heroku to Well

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

What Well pulls from Heroku

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

From Heroku		In Well	Relation
Document		Source document	Captures as

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

What Well does with your Heroku connection

Connect

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

Sync

Well brings document in from Heroku 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 Heroku 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 Heroku lands in the workspace as source document you can search, chart, and automate.

Questions Heroku unlocks

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

Ask Well

Ask anything about your Heroku connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your Heroku connection…

Connect Heroku in three steps

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

How Heroku stays secure with Well

Well connects to Heroku'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 Heroku secret. Tokens are scoped to the document Heroku exposes and refreshed server-side. Reads only, Well cannot modify or delete Heroku records.

OAuth (MCP DCR)Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requests

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

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

Frequently asked questions about Heroku and Well

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

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

What does Well pull into the workspace from Heroku?

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

Can Well show me which Heroku deploys touched which customer-facing features?

Deploys and runs in Heroku carry their commit refs, which Well joins back to the workspace entities (features, projects) those commits relate to. Asking "what changed for our enterprise tier this week" returns a ranked list of deploys with the customer-facing surface they touched.

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

Each Heroku 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 Heroku source attached.

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

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

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

Open Connections > Heroku in Well and click Disconnect. Well calls Heroku's token revocation endpoint and stops calling Heroku immediately on its side; provider-side propagation to Heroku'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 Heroku?

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