The moment it happens

Track your Mux live stream status in Slack

You see when a stream goes active, idle or disconnected.

Runs: The moment it happens
Apps: Mux
AI: Not needed
Access: Mux Video read

Send this to your assistant

Create a ClickRuntime automation: message #live-events in Slack whenever my Mux live stream goes active, idle or disconnected, with the stream name and time.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Add to ChatGPT Add to Claude

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

A producer running a webinar or a church service on Mux Live often cannot watch the dashboard while also managing the room. The encoder drops for 30 seconds because venue wifi hiccuped, the stream goes idle, and the audience sees a frozen player. Whoever is running the encoder may not notice for several minutes, and by then half the viewers have left and the chat is full of questions.

When your stream's status changes, Mux sends events such as video.live_stream.connected, active, disconnected and idle. ClickRuntime receives each one the moment it happens and posts a short message to Slack saying which stream changed and to what state. The producer's phone buzzes while there is still time to reconnect.

Event teams, streamers and educators who go live on a schedule get the most value.

What you get out of it

Dropped encoders are fixed in seconds
A disconnect message reaches the producer immediately, so they restart the encoder or switch to a backup connection before viewers give up. A 20-second glitch stays a glitch. A 20-second glitch stays a glitch instead of becoming a ten-minute outage.
The whole crew sees the same state
Technical directors, hosts and support staff all read the same Slack post. Nobody wonders whether the stream is live, because the channel states when it connected and when it stopped.
Start of broadcast is confirmed
A connected message appears when the encoder starts sending video. Producers know the pipeline works before opening doors, and the host is not announcing a stream that has not begun.
A timeline of the event for review
Slack keeps each state change with a timestamp. After a bad broadcast you can see exactly when the drop happened and how long recovery took, which helps when talking to the venue or the ISP.
Unattended streams are supervised
For recurring or overnight streams with nobody watching, a disconnect still reaches someone. You avoid hours of dead air on a channel that customers believed was live. Whoever is on call hears about the drop even at 3am.

How it works

What happens, step by step

When one of your Mux live streams goes live, goes idle or disconnects, Mux tells ClickRuntime straight away.
ClickRuntime picks out the stream's name and the time of the change.
A message appears in your #live-events Slack channel, such as "Acme Keynote stream disconnected at 17:42 UTC".

Before it runs live

Connect Mux
Paste your automation's link into the other app's webhook settings

What you get

RunsThe moment it happens

Track your Mux live stream status in Slackjust nowSucceeded

Slack · #live-eventsAcme Keynote stream 🔴 disconnected at 17:42 UTC

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.

Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

Changes you can ask for

Act only on the items that match your own rules, and skip the rest
Add an AI step, for example to summarize, sort or draft a reply
Add another app, for example also send it to Slack
Combine it with other Mux steps into one automation

Under the hood

The code that runs this automation

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.

live_stream_state_alerts.pyexample

from clickruntime import on_event, notify

LABELS = {"video.live_stream.active": "🟢 is live", "video.live_stream.idle": "⚪ went idle",
          "video.live_stream.disconnected": "🔴 disconnected"}

@on_event
def handle(event):
    body = event.json or {}
    label = LABELS.get(body.get("type"))
    if not label:
        return {"skipped": body.get("type")}
    stream = body["data"]
    name = stream.get("passthrough") or stream["id"]
    notify.slack(f"{name} {label} at {body['created_at'][11:16]} UTC", channel="#live-events")
    return {"stream": stream["id"], "type": body["type"]}

FAQ

Common questions

Which stream states can it report?

Mux sends connected, recording, active, disconnected and idle events for a live stream. You can post all of them or only the ones you care about, such as disconnected and active. Choose the ones that match how your producer works.

Will brief reconnects create noise?

Mux briefly reports a disconnect when an encoder reconnects within the reconnect window, so you may see a short pair of messages. If that bothers you, only alert on idle, which means the stream ended.

Can it handle several live streams?

Yes. Every event includes the live stream ID, and the message can show a friendly name you map to each ID. All streams in the environment share one webhook, so no extra setup is needed per stream.

What permissions does it need?

Mux Video read. Nothing else in your accounts is used.

Does it need AI?

No. It runs without AI, so it doesn't use your plan's AI allowance.

How many runs does it use?

One run for each event the app sends.

Can I change how it works?

Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

The moment it happens