Webhook / Stream Events

What is it?

Stream events are the notifications a streaming system fires when something happens: broadcast started, broadcast ended, recording ready, viewer count crossed a threshold, stream dropped. A webhook is the standard delivery mechanism — the system automatically "calls out" to another service the moment the event occurs, so other software can react instantly without anyone checking manually.

Think of it as the platform's reflexes: things that should just happen when something else happens.

Practical example

A creator ends their show. In the seconds that follow, a chain fires automatically: the "stream ended" event posts the VOD link to their Telegram channel, the "recording ready" event kicks off the AI clipping job, and an entry lands in their team's Slack with the show's stats. Earlier, when the stream unexpectedly dropped mid-show, the failure event instantly pinged the creator's phone — they knew before their audience did. None of this required a human watching dashboards; events triggered actions.

Key things to know (non-technical)

• Events turn a product from a tool into a platform: they're what let other software build on top of it (the entire Zapier/automation world connects through webhooks).
• The high-value events are predictable: started, ended, failed, recording-ready, milestone-reached.
• Internally, the product's own features ride the same rails — auto-posting, alerts, and post-show processing are all event-driven.
• For business users, events enable workflows (CRM updates, ad triggers) that become reasons to choose the product.

In Tupic Live

Stream events power Tupic Live's automation story twice over: internally (auto-publish the VOD, fire the clip pipeline, alert on failures) and externally — a public webhook offering lets agencies and businesses wire Tupic Live into their own systems, which is exactly the kind of integration that makes B2B customers sticky.