Solution skill
HeyGen video completion: webhooks first, polling every 10s as the fallback
Complete solution
Build both paths.
HeyGen video completion: webhooks first, polling every 10s as the fallback
TL;DR
Build both paths. Use webhooks as the primary completion signal in production (public HTTPS endpoint, handle avatarvideo.success and avatarvideo.fail, update your records idempotently). Keep a polling fallback that checks GET /v3/videos/{video_id} every 10 seconds for local dev and as a safety net; if the webhook path is silent for longer than your polling timeout, fall back to the status endpoint rather than assuming failure.
Use this when you run into the situation in the title.
When not to use this skill: unrelated tasks. It covers only the procedure above.
Compatibility
The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.
Details
Context: GitHub integration notes (mediamake HeyGen webhook setup, real production walkthrough): documents the two completion patterns. The default is the webhook: HeyGen calls your endpoint with avatarvideo.success or avatarvideo.fail when the video is ready, and the handler updates the database. Polling is the fallback: it runs automatically in the background every 10 seconds against the status endpoint, and it is what you use for local development without a public URL or as a safety net if a webhook never arrives. Production webhooks require a publicly accessible HTTPS endpoint with no firewall blocking the route.
Evidence
Source: GitHub integration notes (mediamake HeyGen webhook setup, real production walkthrough): documents the two completion patterns. The default is the webhook: HeyGen calls your endpoint with avatarvideo.success or avatarvideo.fail when the video is ready, and the handler updates the database. Polling is the fallback: it runs automatically in the background every 10 seconds against the status endpoint, and it is what you use for local development without a public URL or as a safety net if a webhook never arrives. Production webhooks require a publicly accessible HTTPS endpoint with no firewall blocking the route.
Verified resolution: Build both paths. Use webhooks as the primary completion signal in production (public HTTPS endpoint, handle avatarvideo.success and avatarvideo.fail, update your records idempotently). Keep a polling fallback that checks GET /v3/videos/{video_id} every 10 seconds for local dev and as a safety net; if the webhook path is silent for longer than your polling timeout, fall back to the status endpoint rather than assuming failure.
Source URL: https://github.com/microfox-ai/mediamake/blob/HEAD/apps/mediamake/components/transcriber/video/WEBHOOK_SETUP.md
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_D4QuW9OPBnlVpkzwISU4KA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">HeyGen video completion: webhooks first, polling every 10s as the fallback <span>— Vectle</span></a>