Integrations · Productivity

Connect Fellow.ai to Well

Name: Fellow.ai entities in Well
Creator: Well

Index Fellow.ai meeting note, agenda item, and attendee so questions about audit entry and work item answer themselves in conversation.

Connect Fellow.aiSee what Well does

What Well pulls from Fellow.ai

Fellow.ai feeds meeting note, agenda item, attendee into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Fellow.ai’s access.

From Fellow.ai	In Well	Relation
Meeting note	Audit entry	Captures as
Agenda item	Work item	Indexes as
Attendee	Team member	Resolves to

Sync mode: MCP hybrid
Refresh: live + reconciliation reads
Direction: Fellow.ai → Well

What Well does with your Fellow.ai connection

Connect

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

Sync

Well brings meeting note, agenda item, and attendee in from Fellow.ai 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 Fellow.ai entity into audit entry, work item, and team member, assigns categories, and links every record to an audit trail across the rest of your connected tools.

Available

Your data from Fellow.ai lands in the workspace as audit entry, work item, and team member you can search, chart, and automate.

Questions Fellow.ai unlocks

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

Ask Well

Ask anything about your Fellow.ai connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your Fellow.ai connection…

Connect Fellow.ai in three steps

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

How Fellow.ai stays secure with Well

Well connects to Fellow.ai's MCP server (fellow.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 Fellow.ai secret. Tokens are scoped to the meeting note, agenda item, and attendee Fellow.ai exposes and refreshed server-side. Reads only, Well cannot modify or delete Fellow.ai records.

OAuth (MCP DCR)Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requestsfellow.app/mcp

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

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

Frequently asked questions about Fellow.ai and Well

From Well, open Connections, find Fellow.ai, and click Connect. Well discovers the OAuth metadata at fellow.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 Fellow.ai's side. No client_id or client_secret to paste; the handshake takes roughly a minute.

Well brings in meeting note, agenda item, and attendee from Fellow.ai and reshapes each entity into your workspace: meeting note becomes audit entry; agenda item becomes work item. Every record arrives with the source identifier preserved, so Fellow.ai stays the source of truth while Well lets you query the data alongside the rest of your stack.

Every Fellow.ai record is scanned for references to companies, contacts, and deal names in your workspace. Matches are surfaced inline on each entity's workspace page: a customer's profile shows the Fellow.ai tasks and threads that mention them, ranked by recency and reach.

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

Well combines live Fellow.ai events with periodic reconciliation reads of meeting note, agenda item, and attendee. New rows appear within seconds when Fellow.ai pushes them; periodic reads catch anything a push missed. The first connect backfills history from Fellow.ai in the background.

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

Fellow.ai 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.

Ready to connect Fellow.ai?

Connect once. Every meeting note, agenda item, attendee from Fellow.ai becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.

Connect Fellow.aiTalk to us