Skip to main content
The Zapier integration is the catch-all bridge for tools we don’t yet support directly. tl;dv, Otter, Grain, custom internal tools — anything that has a Zapier trigger can pipe transcripts into Yuzu. Auth method: OAuth 2.0 between Zapier and Yuzu (handled by the Yuzu Zapier app).
The Zapier integration is currently in beta. Reach out to support@yuzulabs.io to have it enabled for your workspace.

​
Prerequisites

  • A Zapier account on a plan that supports webhook actions or premium app integrations.
  • An admin on your Yuzu workspace who can authorize the Zapier connection.
  • The source app (Otter, Grain, tl;dv, etc.) connected to Zapier.

​
Setup

1

Request Zapier access for your workspace

Email support@yuzulabs.io with the subject “Zapier Integration Request” and your workspace name. Yuzu enables the Zapier app for your workspace.
2

Connect Yuzu inside Zapier

In Zapier, search for Yuzu and click Connect. You’ll be redirected to Yuzu to authorize the connection. Approve the requested scopes.
3

Build a Zap from your source app to Yuzu

Pick your notetaker (Otter, Grain, tl;dv, …) as the trigger. For the action, use the Yuzu Send Transcript action.Map these fields:
  • Transcript → the full transcript text from the source app.
  • Title → the meeting title.
  • Meeting date → the meeting start time.
  • Participants → attendee emails or names.
  • Summary (optional) → if your source app produces one.
  • Action items (optional).
4

Test the Zap

Run the Zap with a sample meeting from your source app. The transcript should appear in your Yuzu transcripts list within a minute.
5

Turn the Zap on

Once it works end-to-end, enable the Zap. Every new meeting in the source app will now flow into Yuzu.

​
What gets pulled

Whatever you map in the Zap. At minimum, the transcript text is required for Yuzu to classify the call and (if it’s a sales call) generate a recap video. The richer the metadata you pass through, the better Yuzu’s automation rules can target the right meetings.
Zapier-sourced transcripts don’t have a Yuzu-managed integration record, so Yuzu cannot retry-fetch them. If a webhook from Zapier fails, the Zap itself needs to retry — Yuzu’s “Retry fetch” button does not apply.

​
Running Zapier alongside a direct integration

You can keep Zapier connected even if you also have Fireflies, Fathom, or another direct integration active. Yuzu accepts webhooks from both. Use this when one team uses Fireflies and another uses Otter, for example.

​
Troubleshooting

The Zapier integration is gated per-workspace during the beta. Email support@yuzulabs.io with your workspace name to have it enabled.
Zapier’s transcript field is plain text. Speaker diarization isn’t preserved unless your source app serializes speakers into the text itself (e.g. Alice: …). Yuzu does its best to detect speaker prefixes when present.
Open the run in Zapier and check the response from Yuzu — most failures are field-mapping errors (missing transcript, malformed date). Fix the mapping in the Zap editor and re-run.
Zapier tokens expire periodically. Reconnect Yuzu inside Zapier — go to My Apps → Yuzu → Reconnect. No data is lost.