Prerequisites
- An Ergo account with permission to configure webhooks under Meeting → Webhooks.
Setup
Open Yuzu Settings → Integrations
Go to Settings → Integrations, click Connect Notetaker, and choose Ergo. Yuzu creates the integration immediately and shows you a unique webhook URL.
Open Ergo's webhook settings
In the Ergo dashboard, navigate to the Meeting section, click the three-dot menu in the top-right corner, and open the Webhooks tab.
Paste the Yuzu webhook URL
Copy the URL from Yuzu (it looks like
https://<your-yuzu-host>/webhooks/notetaker/ntk_<token>) and paste it into Ergo’s endpoint field.Generate an auth secret in Ergo and paste it back into Yuzu
Ergo will prompt you to generate an auth secret for the webhook. Copy it and paste it into the Webhook Secret field in the Yuzu dialog. Yuzu uses this secret to verify every incoming Ergo webhook.
What gets pulled
Ergo sends the entire meeting payload in the webhook body, so Yuzu doesn’t need to make a follow-up API call. Eachnotetaker.meeting.completed event includes:
- The transcript array with
speaker,text, andtimestamp. - Title, attendees, duration, recording URL.
- Summary and action items if Ergo generated them.
- A no-show flag (Yuzu skips no-show meetings).
Troubleshooting
Webhooks reach Yuzu but get rejected
Webhooks reach Yuzu but get rejected
This usually means the auth secret in Yuzu doesn’t match the one in Ergo. Regenerate the secret in Ergo, paste it into Yuzu (Settings → Integrations → Ergo), and trigger a test meeting.
Webhooks aren't arriving at all
Webhooks aren't arriving at all
Confirm the Yuzu webhook URL in your Ergo dashboard matches the one shown in Yuzu’s Ergo row exactly — including the
ntk_… token. Regenerating the token in Yuzu invalidates the old URL.No-show meetings show up in my transcripts list
No-show meetings show up in my transcripts list
They shouldn’t. Yuzu drops events flagged with
isNoShow: true from Ergo. If you see a no-show coming through, check the activity log and report the meeting ID to support@yuzulabs.io.