Integrations · ProductivityConnect Circleback to Well
Index Circleback meeting recording, transcript, and participant so questions about audit attachment and indexed record answer themselves in conversation.
What Well pulls from Circleback
Circleback feeds meeting recording, transcript, participant into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Circleback’s access.
| From Circleback | In Well | Relation | |
|---|---|---|---|
| Meeting recording | Audit attachment | Preserves as | |
| Transcript | Indexed record | Becomes | |
| Participant | Team member | Resolves to |
- Sync mode
- MCP hybrid
- Refresh
- live + reconciliation reads
- Direction
- Circleback → Well
What Well does with your Circleback connection
Connect
Connect Circleback over OAuth (MCP DCR): Well registers a client through Circleback's OAuth Dynamic Client Registration and you approve on Circleback's side, so the password never reaches Well; Well holds only a scoped token it can refresh.
Sync
Well brings meeting recording, transcript, and participant in from Circleback 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 Circleback entity into audit attachment, indexed record, and team member, assigns categories, and links every record to an audit trail across the rest of your connected tools.
Available
Your data from Circleback lands in the workspace as audit attachment, indexed record, and team member you can search, chart, and automate.
Questions Circleback unlocks
Ask in plain language. Well answers from your connected Circleback connection, resolved against the rest of your stack.
Ask anything about your Circleback connection
Ask about your Circleback connection…
Connect Circleback in three steps
- 01
Authorise Circleback via MCP
From Well's Connections panel, search for Circleback and click Connect. Well discovers Circleback's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on Circleback's side. No client credentials to paste.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
- MCP serverapp.circleback.ai/api/mcp
- 02
Map your entities
Well's MCP client discovers meeting recording, transcript, and participant from Circleback that Circleback'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 Circleback records. Because Circleback 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 Circleback records happens in the background.
How Circleback stays secure with Well
Well connects to Circleback's MCP server (app.circleback.ai/api/mcp) via the Model Context Protocol. The MCP server itself handles credential issuance through OAuth Dynamic Client Registration; Well never sees a long-lived Circleback secret. Tokens are scoped to the meeting recording, transcript, and participant Circleback exposes and refreshed server-side. Reads only, Well cannot modify or delete Circleback records.
- granted
Read Circleback records
Resources the Circleback MCP server exposes, scoped by your OAuth approval.
- granted
Resolve meeting recording, transcript, and participant across your stack
Match identifiers in Circleback against the same entities your other connected tools expose, so each record carries cross-tool context.
- refused
Modify or delete Circleback records
Not granted; Circleback is read-only in Well. Write-back is opt-in per connector when a write surface exists.
- refused
Store Circleback passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
Frequently asked questions about Circleback and Well
From Well, open Connections, find Circleback, and click Connect. Well discovers the OAuth metadata at app.circleback.ai/api/mcp/.well-known/oauth-authorization-server, registers a client on the fly via Dynamic Client Registration, and walks you through the authorize prompt on Circleback's side. No client_id or client_secret to paste; the handshake takes roughly a minute.
Well brings in meeting recording, transcript, and participant from Circleback and reshapes each entity into your workspace: meeting recording becomes audit attachment; transcript becomes indexed record. Every record arrives with the source identifier preserved, so Circleback stays the source of truth while Well lets you query the data alongside the rest of your stack.
Tasks, projects, and team members from Circleback are indexed as workspace entities. When you ask "what is the team working on for Globex" Well joins Circleback items mentioning Globex to deals in your CRM and conversations with that customer, so the answer carries product, sales, and support context together.
Well watches for updates to meeting recordings 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 audit attachment. Edits flow in incrementally; nothing is duplicated, and the Circleback source identifier is retained on every revision.
Well combines live Circleback events with periodic reconciliation reads of meeting recording, transcript, and participant. New rows appear within seconds when Circleback pushes them; periodic reads catch anything a push missed. The first connect backfills history from Circleback in the background.
Open Connections > Circleback in Well and click Disconnect. Well calls Circleback's token revocation endpoint and stops calling Circleback immediately on its side; provider-side propagation to Circleback's admin panel varies by provider. The meeting recording, transcript, and participant Well already synced stay in your workspace by default; ask Support to purge them if your compliance flow requires it.
Circleback 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 Circleback
More in Productivity
Asana
Connect Asana to Well to sync tasks, projects, and team workflows.
Atlassian
Connect Atlassian to Well to sync tasks, projects, and team workflows.
ClickUp
Connect ClickUp to Well to sync tasks, projects, and team workflows.
Clockwise
Connect Clockwise to Well to sync tasks, projects, and team workflows.
Popular cross-category
Ready to connect Circleback?
Connect once. Every meeting recording, transcript, participant from Circleback becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.