Who this section is for
- Admins and RevOps teams choosing workspace-level sources.
- Users connecting personal sources such as email, calendar, Slack, or a notetaker.
Before you start
- Know whether the integration is personal, workspace-level, or admin-only.
- Use the account your team expects Ergo to read from or write through.
- Approve every required scope during OAuth and keep API keys, webhook secrets, and signing keys current.
- Verify the downstream workflow after connecting. A connected card does not mean every CRM object, Slack channel, calendar event, or recording is accessible.
Articles
- Salesforce
- HubSpot
- HubSpot meeting activities and recording links
- Attio
- Pipedrive
- Ergo CRM
- Google Workspace
- Calendar scopes and meeting auto-join
- Microsoft 365
- Email signature
- Expired grants and reconnecting
- Slack
- Slack monitoring and pre-call context
- Beeper
- Pylon
- Ergo Notetaker
- Ergo Desktop Notetaker
- Gong
- Fireflies
- Circleback
- BlueDot
- Fathom
- Granola
- Outreach
- Nooks
- Salesfinity
- MCP/external agent tools
Common issue path
- For expired Google or Microsoft grants, start with Expired grants and reconnecting.
- For CRM object or field issues, check the CRM integration page and Field mapping.
- For notetaker overlap, compare the bot, desktop, and third-party notetaker pages before enabling multiple sources.
- If the symptom crosses sources or permissions, use Troubleshooting.