Integrations·Updated Aug 21, 2026
Integrations Overview
Choose the right KendoAI integration for meetings, dialers, CRM context, revenue, and automation.
Choose by Job to Be Done
Open Configure > Integrations to connect providers, select destination teams, inspect connection health, run supported backfills, and review provider requirements.
Personal meeting imports — Fathom, Zoom, Google, Fireflies, and Wispr Flow connect per user because each account exposes that person's accessible meetings
Team-wide call imports — Aircall, RingCentral, Dialpad, Quo, Grain, Granola, Close CRM, Gong, Avoma, and GoHighLevel use an admin or workspace credential and route eligible calls to one Kendo team
Business context and revenue — HubSpot enriches calls; Stripe and Whop attach collected payments
Automation — Slack, Webhooks, Push API, Zapier, Make, and n8n notify other systems or send calls into Kendo
Meeting Assistants and Conferencing
Fathom — Per-user OAuth; recordings and transcripts; automatic imports; 25-call manual backfill; title/internal-call filters
Zoom — Per-user OAuth; paid-plan cloud recordings and transcripts; automatic imports and manual backfill; local-only recordings are unavailable
Google — Per-user OAuth for reviewable Gmail drafts, Calendar event management, and accessible native Meet recordings/transcripts; no meeting bot
Fireflies — Per-user API key and 25-call backfill; a standard key sees that user's meetings, while company-wide access requires Fireflies Super Admin API on Enterprise
Wispr Flow (beta) — Per-user OAuth/read-only MCP; completed Notetaker transcript imports; Cloud Sync required; audio is not copied
Dialers, Recorders, and Team-Wide Imports
Aircall (beta) — Admin connection, company webhook, recorded calls over 60 seconds, rep matching by email
RingCentral — Private JWT app credentials, company call-log polling every 15 minutes, recorded calls over 60 seconds, rep matching by extension
Dialpad (beta) — Company-admin API key and webhook, recordings over 60 seconds, rep matching by email
Quo (formerly OpenPhone, beta) — Workspace-admin API key and webhook, native transcripts on Business/Scale, rep matching by email
Grain (beta) — Workspace access token, title/rep/date import rules, recording audio, and automatic imports
Granola (beta) — Workspace API key, signed note webhooks, owner-email matching, transcript/note imports without stored audio or video
Close CRM (beta) — Team API key, calls with transcript and recording, rep matching by email, private durable recording copy, 30-minute sync
Gong (beta) — Admin access key/secret, workspace calls and speaker-attributed transcripts, rep matching by email, scheduled transcript checks
Avoma (beta) — Scoped API key, recordings and speaker-attributed transcripts, rep matching by email, scheduled transcript checks
GoHighLevel (beta) — Private Integration token and Location ID, connected calls over 60 seconds, contacts and rep details, roughly 30-minute polling
CRM and Payment Intelligence
HubSpot (beta) — Team-scoped OAuth for read-only contacts, companies, deals, pipelines, and owners; enriches confidently matched calls and provides CRM deep links
Stripe (beta) — Restricted read-only key; imports payments, suggests call matches, supports customer search, and cannot move money
Whop (beta) — Company API key; imports payments read-only, supports call-to-payment linking, and refreshes new payments automatically
Payment links feed cash collected, win rate, average deal size, payment-assignment reporting, and revenue webhooks.
Automation and Custom Ingestion
Slack — Channel call alerts, rep direct messages, low-score rules, scheduled reports, and slash commands
Webhooks — Signed real-time events with test sends, delivery history, and a 30-request-per-minute delivery limit
Push API — Team-scoped API keys for transcript or audio URL ingestion, metadata, tags, notes, title control, and deal fields
Zapier, Make, and n8n — Use Kendo webhooks as triggers or Push API as an input path for broader workflows
How Routing and Rep Attribution Work
Personal connections normally attribute meetings to the connecting user. Team-wide integrations resolve the source-system owner, user, or extension against members of the selected destination team.
Email-based matching checks the member's primary email and additional aliases. Kendo uses exact matches and does not guess between similar names. Unmatched imports may fall back to the team owner or be skipped, depending on the provider; the integration panel explains its behavior.
After ingestion, Call Routing independently chooses the scorecard and follow-up workflow. Destination-team routing and scorecard routing are separate controls.
Connection Checklist
- 1. Confirm whether the provider connection is personal or team-wide
- 2. Verify the provider plan includes recordings, transcripts, or API access required by the card
- 3. Connect with the smallest permitted scope and choose the destination Kendo team
- 4. Match source users to Kendo members and add email aliases where needed
- 5. Run a small manual sync or wait for one new call
- 6. Confirm the recording/transcript, rep, source, team, scorecard, and usage charge are correct
- 7. Review connection health and import events before enabling a large backfill
Beta and Provider Limitations
A beta badge means the integration is available but may still have provider-specific setup requirements or evolving behavior. Kendo can only import artifacts the connected credential is allowed to access.
Some providers expose transcripts without audio, require native recording to be enabled, delay transcripts after a meeting, restrict APIs to higher plans, or block embedded playback. The integration panel is the source of truth for the current provider requirements.