Meetings & Voice · Integration
Fellow
Add Fellow to your product for your customers, and give your AI agents governed access to it.
Fellow, now at fellow.ai after operating on fellow.app, is built around the calendar rather than around standalone documents: a meeting record derives from a Google or Microsoft calendar event, and its notes, agenda and action items hang off that event. Recurring series carry an agenda forward between occurrences, so a note written once appears against the series and not only a single instance, which changes how you deduplicate when syncing. Transcripts and AI summaries only exist for meetings the notetaker actually joined, so a meeting can be present with a full agenda and no recording at all, and integrations that assume every meeting has a transcript will find gaps. Action items are first-class objects with an assignee and due date that survive independently of the meeting they were created in, which is what makes them worth syncing outward. Access is workspace-scoped, and private notes on a meeting are excluded from what an integration can read, so counts will not match what a workspace owner sees in the UI. fastn holds each customer's own credential, handles the calendar-linked reauthorisation, and keeps meeting reads attributed per tenant.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Fellow workspace so your product can read their meeting notes and action items without a shared credential
Sync action items with assignees and due dates into your own task model and keep status in step
Attach the AI summary of a customer call to the matching record in your product
Show which recurring meetings have agendas that have not changed in weeks so a customer can prune them
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent pull the action items assigned to a person across recent meetings and report what is overdue, with every read audited per tenant
Have an agent summarise what was decided in a recurring meeting series over the last month
Allow an agent to flag meetings that had no notetaker present and therefore no transcript
Example prompt
What action items came out of my meetings this week, and which ones are already overdue?
Set up Fellow in 4 steps
- 01Enable the Fellow connector from your fastn dashboard.
- 02Have each customer authorise their own Fellow account, so calls run under their credentials rather than a shared key.
- 03Decide which meetings, calls and participants your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Fellow integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Fellow integration without building it. Your customers connect their own Fellow account inside your product and work their meetings, calls and participants there, with no per-customer code on your side.
- Handle the part that actually costs time: a call or a meeting is a real-time event, so a missed join or a dropped recording cannot be retried later. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Fellow update is not your on-call problem.
- One integration serves your product and your agents. The same governed Fellow connection powers in-product features and gives AI agents scoped, audited access, so you let your product act on the conversations that happen by voice and video, not just the written ones without wiring it twice.
Used by these teams
Compare with
Aircall
Gong
Chorus.aiOften used alongside
Tools the same teams tend to run next to Fellow, across other categories.
Slack
Microsoft Teams
Twilio
CalendlyFellow integration FAQ
How do I add a Fellow integration to my product?
Enable the Fellow connector in your fastn dashboard, then let each customer authenticate their own Fellow account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Fellow client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Fellow account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Fellow account and only ever sees their own meetings, calls and participants. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Fellow integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent pull the action items assigned to a person across recent meetings and report what is overdue, with every read audited per tenant
Who maintains the Fellow integration?
fastn does. When Fellow changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can my product schedule or act on Fellow conversations automatically?
Yes. Within the permissions each customer grants, your product can create a meeting, place or route a call, add participants, or react when one ends, all inside their own Fellow account rather than through a shared one.
Can I get recordings, transcripts and outcomes back from Fellow?
Yes, scoped per tenant and audited. This matters more here than in most integrations, because the substance of a call usually exists only in its recording or transcript, so a read that fails silently loses the thing you wanted.
What can I build with the Fellow integration?
A common starting point: let a customer connect their own Fellow workspace so your product can read their meeting notes and action items without a shared credential. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Fellow integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Fellow does not change your per-connector cost. You can start free with 3 connected accounts.
Add Fellow to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.