Prerequisites
- A Fireflies account on a plan that exposes the Developer settings (Pro or higher).
- Permission to add a webhook in Fireflies workspace settings.
- Fireflies must be set to record and transcribe the meetings you want in Yuzu.
Setup
Open Yuzu Settings → Integrations
In your Yuzu workspace, go to Settings → Integrations and click Connect Notetaker, then choose Fireflies.
Grab your Fireflies API key
Open Fireflies Settings → Developer. Copy the API key shown there.
Paste the API key and your account email into Yuzu
Yuzu validates the key against the Fireflies GraphQL API before saving it. The email should be the address tied to your Fireflies account.
Copy the webhook URL Yuzu generates
After Yuzu saves the key, it shows a unique webhook URL of the form
https://<your-yuzu-host>/webhooks/notetaker/ntk_<token>. Copy it.Add the webhook in Fireflies
Back in Fireflies Settings → Developer:
- Paste the URL into the Webhook URL field.
- Choose Meeting Transcribed as the trigger event.
- Save.
What gets pulled
For each completed meeting, Yuzu imports:- The full transcript with speaker-labeled sentences (Fireflies provides high-quality diarization).
- Title, date, duration, host email, organizer email, and participants.
- The Fireflies-generated summary and action items.
- The transcript URL, audio URL, and video URL.
Historical sync
After connecting, you can import past meetings from Settings → Integrations → Sync Meetings. Choose 7 days, 2 weeks, or 4 weeks. Existing transcripts are not duplicated.Fireflies’ API does not document a public rate limit, so Yuzu paces fetches with a short delay between requests. A 4-week sync of a heavy user typically completes in a few minutes.
Troubleshooting
Webhooks aren't arriving
Webhooks aren't arriving
Open the webhook URL row in your Fireflies Developer settings. Make sure the URL starts with
https:// and ends with the ntk_… token from Yuzu — a regenerated token in Yuzu invalidates the old one immediately. Trigger a test by recording a short meeting; the activity log under Settings → Automations shows webhook arrivals.Yuzu rejected my API key
Yuzu rejected my API key
The connect dialog tests the key by calling Fireflies’
user GraphQL query. A failure means either the key is invalid or your Fireflies plan doesn’t expose API access. Confirm both, then paste the key again.The transcript came in but with no speaker names
The transcript came in but with no speaker names
Fireflies labels speakers using participant emails on the calendar event. If a meeting was recorded outside your calendar or the participant emails didn’t resolve, you may see generic
Speaker 1 / Speaker 2 labels. This is upstream from Yuzu.A meeting completed but no video was created
A meeting completed but no video was created
Check Settings → Automations → Activity log for that meeting. The most common reasons: the meeting wasn’t classified as a sales call, your automation rules excluded it (length, attendees, or pillar), or the workspace is out of video quota.