Pick where Otter notes should land, then buy the plan that reaches it, since the Public API and webhooks need Enterprise. Every plan connects to Slack and to AI assistants over MCP (Model Context Protocol). Zapier needs Pro or above, CRM sync covers more users on higher plans, and AI Chat acts in other tools only after someone approves.
When you need this
- Teams want meeting notes in a CRM, a wiki, a task tracker, or an AI assistant without copying them by hand.
- Someone has built a pipeline from Otter recordings into other systems.
- An admin needs to know which keys, connectors, and assistants can read which meetings.
Evaluation criteria
Plan gates
Which connections does each plan include?
Look forSlack and MCP work on any plan. Zapier needs Pro, Business, or Enterprise. Salesforce or HubSpot sync covers 1 user on Pro, 5 on Business, and any number on Enterprise. AI Chat with Salesforce, the Public API, and webhooks need Enterprise.
Look forMCP tools can search and fetch the meetings each user authorizes through OAuth. Otter recommends setting its tools to always allow in Claude, so check that against your data policy before rollout.
AI Chat actions
Can AI Chat change things in other tools?
Look forWork mode can create Jira tickets, Notion pages, Google Drive files, and Gmail drafts through connectors, and Otter asks for approval before some of those actions, so confirm which ones prompt before you rely on it. The pricing page lists the Gmail, Google Drive, Notion, and Jira connectors on Enterprise, so check which ones your plan has.
CRMs and exports
Do customer notes land on the right record?
Look forSalesforce must run Sales Cloud in Enterprise, Unlimited, or Developer Edition. HubSpot connects per user or across an Enterprise workspace. Check export permissions for Notion, Google Drive, and OneDrive, which admins can turn off.
API and webhooks
Which keys can read which data, and who manages them?
Look forGive each Enterprise API key a named owner. Each user can hold up to 2 keys, at up to 10 requests per second. The Public API exposes channels, conversations, transcripts, audio, action items, and insights. Workspace admins configure webhooks for summaries and action items, including insights.
Governance: check the pipeline
Will a generated or automated pipeline push bad data silently?
Look forRequire review before anything writes to the CRM. One builder who sent Otter recordings to Clay and a CRM added a verification step after generated pipelines pushed unchecked contacts.
Questions to ask vendors
- Which MCP clients will we allow to connect to Otter for our users, and with what tool permissions?
- Who owns each API key and webhook endpoint when its creator leaves?
- How many of our people need Salesforce or HubSpot sync, given that more than 5 requires Enterprise?
- Which AI Chat connectors are available on our plan, and who approves Work mode actions?
Red flags
- MCP connections set to always allow on accounts that hold confidential meetings.
- API keys created without a named owner or rotation plan.
- Customer notes syncing to the CRM before anyone checks speakers and action items.
- Zapier workflows importing audio that use up a team's monthly minutes unnoticed.
Products in this piece
Sources
- Official documentation
- 9
- Public source
- 2
- Otter.ai pricing
- Otter Help Center: Connect Slack to Otter.ai
- Otter Help Center: Connect Otter to Zapier
- Otter Help Center: Connect HubSpot with Otter.ai
- Otter Help Center: Export to Notion
- Otter Help Center: Otter MCP Server
- Otter Help Center: Otter AI Chat Overview V2
- Otter Help Center: Otter.ai Public API
- Otter Help Center: Workspace Webhooks
- Hacker News comment on piping Otter recordings into a CRM (Mar 5, 2026)
- Hacker News comment on Otter versus Copilot for meeting minutes (Dec 4, 2025)