Skip to main content

Otter.ai overview

Use the Otter.ai connector to search meeting conversations and use their content in Glean answers. The connector indexes content through the Otter.ai Public API and applies conversation sharing permissions to search results.

Indexed content​

Glean retrieves conversations available through the connected account and workspace APIs. Each indexed conversation links back to its Otter.ai page and includes the following content when Otter.ai returns it:

  • Title and creation date
  • Summary and transcript text
  • Outline sections
  • Action item text and assignees
  • Insights
  • Owner, calendar guests, shared channels, and meeting link

Channels provide sharing and search context. Glean doesn't index them as separate documents.

Authentication​

A Glean admin configures the connector with an API key from an Otter.ai Enterprise account. Glean stores the key as a secret and uses it to authenticate requests to Otter.ai. Users don't need to complete a separate OAuth sign-in for this connector.

During setup validation, Glean checks that the API key can access an Otter.ai workspace. Passing validation confirms workspace access, not that the initial crawl has finished or that every conversation is searchable.

See Set up the Otter.ai connector for prerequisites and instructions.

Permissions​

Glean grants access to an indexed conversation based on:

  • The conversation owner
  • Users the conversation is directly shared with
  • Members of channels the conversation is shared with

Glean uses the email addresses Otter.ai returns to identify users. Being listed as a calendar guest or meeting participant doesn't grant access by itself.

Workspace-shared channels

A channel shared with the workspace doesn't automatically make its conversations visible to everyone in Glean. Users must be explicit channel members, own the conversation, or have direct access through conversation sharing.

Crawl frequency and freshness​

The connector uses scheduled full crawls. The default intervals apply after initial indexing:

Crawl scopeDefault intervalWhat it refreshes
ChannelsEvery hourChannel information and membership
ConversationsEvery 24 hoursConversation content, metadata, and conversation sharing permissions

Channel membership changes and conversation sharing changes use different crawls. For example, removing someone from a channel is reflected through the channel crawl, while removing a direct share requires a conversation crawl.

These intervals aren't guarantees that a change will appear in search within that time. The relevant crawl and indexing must finish. The connector doesn't use incremental crawls or webhooks for real-time updates.

Limitations​

  • Glean doesn't index conversations while Otter.ai is still processing their summary, action items, or outline.
  • Audio recordings aren't indexed or downloaded by this connector.
  • The connector doesn't provide write operations in Otter.ai.

Otter.ai's vendor-hosted Model Context Protocol (MCP) server is a separate service. Setting up this native connector doesn't configure that server. See Otter MCP Server.

See also​