Skip to main content
Yuzu can pull sales-call data, email activity, calendar meetings, LinkedIn engagement, CRM context, and meeting transcripts from your existing tools. Most teams start with a notetaker, then connect Gmail, Google Calendar, and LinkedIn so follow-up, meetings, and engagement can return to the deal thread.

​
Available integrations

Notetakers

Auto-generate videos from meeting transcripts. Direct providers plus Zapier.

Yuzu Notetaker

Native meeting capture that syncs completed calls into Yuzu.

Gmail

Send and schedule tracked emails, backfill person history, and detect buyer replies.

Google Calendar

Sync meetings, create invites, and power booking links.

LinkedIn

Draft, schedule, and publish posts, then bring reactions and comments back into deals.

Slack

Send package notifications, review emails in Slack, and route Zu replies.

Telegram

Send mobile-friendly notifications and workspace-scoped Zu replies.

Fireflies

API-key based. Webhook-driven transcript imports.

Fathom

OAuth. Webhook is created automatically on connect.

Granola

API key. Polls Granola for new notes and supports all-time sync.

Ergo

Webhook only. Paste the URL into the Ergo dashboard.

Circleback

Webhook automation. Sends notes, action items, and transcripts.

Monaco

API key. Pulls meetings from the Monaco revenue engine.

Otter

Beta. Connect via Zapier today.

Grain

Beta. Connect via Zapier today.

HubSpot (CRM)

OAuth. Pulls meeting transcripts and call recordings from HubSpot.

Zapier

Connect any of 6,000+ apps. Map fields in Zapier.

​
How they fit together

Each integration falls into one of three roles:
  • Source — provides the raw signal (transcript, email, calendar event, CRM event). Examples: Fireflies, Granola, Gmail, Google Calendar, HubSpot.
  • Trigger — decides which signals turn into a Yuzu flow. Configured per-workspace under Settings → Automations.
  • Destination — where the rendered video, draft, or notification lands. Examples: Slack, Telegram, HubSpot deal notes, and email.
  • Engagement return path — sends buyer activity back into Yuzu. Examples: Gmail replies, calendar meetings, LinkedIn comments, public-link views, and video CTA clicks.
A typical setup wires up at least one source and one destination, then lets Yuzu’s automation rules handle the rest.

​
Need something custom?

If your tool isn’t listed, the Yuzu API gives you the same primitives our integrations use. Most one-off integrations end up as a small webhook handler that calls POST /flows/sales-email-video.