Connecting Glean and Fellow makes meeting knowledge easy to find across your organization. Agendas, notes, transcripts, and AI recaps from Fellow are automatically indexed in Glean, so teams can search and access key meeting content alongside all other work content.
Note: This integration is set up by a Glean administrator and a Fellow workspace admin. Individual users do not need to connect their own accounts.
Set up the integration
Step 1: Create a Custom Data Source in Glean
In the Glean Admin Console, go to Data sources → Add data source → Custom, or navigate directly to the setup page.
Fill in the following fields:
Field | Value |
Unique name | Fellow |
Data source category | Collaborative Content |
Display name | Fellow |
URL regex | |
Email is used to reference users in document access control lists | Checked |
Step 2: Create an API token in Glean
In the Glean Admin Console, go to Platform > API tokens, or navigate directly here, and click Add token.
Fill in the following fields:
Field | Value |
Description | Fellow |
Scopes | Fellow (must match the Unique name set in the Custom Data Source exactly - this is case-sensitive) |
Expires | Set to at least 1 year in the future to avoid disruptions to syncing |
3. Click Save. The generated API token will appear in a modal - copy and store it securely before closing, as it will not be displayed again. If you miss this step, delete the token and create a new one.
Step 3: Send the following values to Fellow
Once the Custom Data Source and API token have been created in Glean, send the following details to the Fellow team to complete the integration:
Server instance (QE) - A URL in the format
https://<company>.glean.com, available from the About Glean pageDatasource name - The Unique name set when creating the Custom Data Source
Indexing API token - The API token created for Fellow
How the integration works
Once set up, Fellow automatically sends data to Glean as it becomes available. Content is synced whenever a note is updated, a user gains or loses access to content, or a meeting recap is generated.
Each meeting is indexed in Glean as a single document, combining the written agenda, notes, and all associated recaps (summary, chapters, action items, and decisions) into one searchable result.
Permissions in Glean mirror permissions in Fellow - if someone has access to content in Fellow via a calendar event, direct share, or channel, they will see it in Glean. Users without Fellow access will not see Fellow content in Glean.
Note: Indexed documents may take some time to appear or update, depending on how quickly Glean processes them.
Frequently asked questions
Are transcripts and videos sent to Glean?
Transcripts, agendas, and AI recap content (summary, chapters, action items, and decisions) are all sent to Glean. Videos are not sent — Glean processes text content only.
Are action items from the Action Items page sent to Glean?
No - only action items within meeting notes are sent to Glean.
Are private notes sent to Glean?
No - private notes are never sent to Glean.
Are personal meeting series (legacy feature) sent to Glean?
Yes - personal series are included.
Are attachments in notes sent to Glean?
No - Glean processes text only, so non-text attachments are not sent.
Is calendar data sent to Glean?
No - calendar data is not sent. Glean has its own calendar integrations for that.
Can I choose which meetings are sent to Glean?
Currently, all meeting content is sent automatically. More granular controls may be added in the future.
Do individual users need to connect their own Fellow accounts to Glean?
No - only the Fellow workspace admin needs to complete the setup. Once connected, the integration is available to all users of both platforms.
What if only some employees use both Fellow and Glean?
Permissions are enforced. A recap visible to everyone in Fellow will only appear in Glean for users who also have a Fellow account. Users without Fellow access must sign up to the workspace to access that content in Glean.
How long does it take for data to appear in Glean?
Anywhere from 5 minutes to 2 hours after content is created or updated in Fellow, depending on Glean's processing speed.
