Webhooks are a Max plan feature

Webhooks live under Connect, which is only available on the Max plan. If you don't see Connect in your sidebar, upgrade from your billing page to unlock webhooks alongside MCP, OneShot defaults, and Email Settings.

Webhook payloads include video URLs, render IDs, and workspace metadata. Sending them over plain HTTP exposes them to anyone on the network path. Use HTTPS — every modern automation tool supports it by default.

Resync is your replay button

If your endpoint went down and missed events, use Resync on the webhook row to replay recent deliveries. Better than asking BIGVU to refire — Resync is built for exactly this case.

Test before you trust it

Every webhook row has a Test action that fires a real payload. Run it once you've wired up your automation and confirm the downstream side actually does what it should. Save-time ping ≠ end-to-end test.

One webhook per workflow

Tempting to point everything at one mega-endpoint, but you'll thank yourself later if you split — "render done → Sheets," "render fail → Slack," "publish → CRM." Easier to debug, easier to pause one without affecting the others.

Never put secrets in the URL

Don't embed tokens, API keys, or passwords in the webhook URL. URLs end up in logs and are visible in the BIGVU UI. If your endpoint needs auth, use a signed header verified on your side.

Delete removes the webhook and its full delivery history with no undo. If you might want it back, use Disable instead — it stops deliveries without losing the config or history, and you can re-enable anytime.

All Steps (7)

Webhooks — Web

Send finished videos straight to other platforms or trigger your own automations. Wire BIGVU into Zapier, Make, n8n, or your own backend with a name and a URL — and manage everything from a webhooks dashboard. Available on the Max plan.

Webhooks — Web

All Steps (7)

Webhooks — Web

Was this helpful?

Related Topics

Was this helpful?

Related Topics