Set up the Otter.ai connector

Connect Otter.ai to make meeting transcripts, summaries, and action items searchable in Glean. Create an API key in Otter.ai, configure the connector in Glean, and verify results after the initial crawl.

Prerequisites

Before you begin:

• Have an Otter.ai Enterprise account with workspace access. Otter.ai makes its Public API available to Enterprise workspaces.
• Confirm that you can open Integrations → Developer in Otter.ai and create an API key.
• Have a Glean admin account with permission to add and configure connectors.

Create an API key

Create the key in the Otter.ai account you want Glean to use:

1. Sign in to your Otter.ai Enterprise workspace.
2. Go to Integrations → Developer.
3. Click Create key.
4. Click Copy and store the key securely. Otter.ai displays it only once.

Otter.ai allows up to two API keys per user. If you've reached the limit, confirm that a key is no longer in use before revoking it. If the Developer tab isn't available, contact your Otter.ai account manager.

See Otter.ai Public API for current API-key requirements.

Add the connector in Glean

Use the API key to configure the native connector:

1. In the Glean Admin console, go to Connectors and click Add connector.
2. Search for and select Otter.ai.
3. Enter a Name for the connector. Users see this name in Glean.
4. Paste the key into API key. Use the Otter.ai Public API key, not an MCP endpoint or OAuth token.
5. Click Save. Glean validates that the key can access an Otter.ai workspace.

If validation fails, resolve the reported error before continuing. See OTTERAI_1.

Confirm indexing and access

A successful save isn't confirmation that content is searchable. Check the connector and its results:

1. In the Admin console, open the Otter.ai connector and confirm that crawling is turned on.
2. Wait for the initial crawl and indexing to finish, and check for reported errors.
3. Search Glean for an Otter.ai conversation you own or have access to through direct sharing or explicit channel membership. Open the result to confirm that it links to the expected conversation in Otter.ai.

If the conversation doesn't appear, check that Otter.ai has finished processing its summary, action items, and outline. See Troubleshoot the Otter.ai connector for other causes.

Protect and replace the API key

Treat the API key like a password. Do not include it in tickets, screenshots, source code, or shared documents. Store it in the Glean connector credential field or an approved secrets manager.

To replace a key:

1. Create a replacement key in Otter.ai.
2. Open the Otter.ai connector configuration in Glean, replace API key, and click Save.
3. Confirm that validation succeeds before revoking the old key, unless the old key has been exposed and needs immediate revocation.

See also

• Otter.ai overview for indexed content, permissions, and default crawl intervals