Skip to content
ClickRuntime

Automate Mux

Mux encodes and streams video for your product, through assets for on-demand video and live streams for broadcasts. Developers and producers automate alerts for assets that fail processing and for live streams that connect, go idle or drop. Describe the alert to your AI assistant, look over what it will do, and it stays on.

Add to ChatGPTAdd to Claude
Works inChatGPTClaudeClaude CodeCursorCodexVS CodeGemini CLIZedopencodeAny MCP client

Try asking

Create a ClickRuntime automation: when a Mux asset in production errors, post the asset ID and the error message to #video-ops in Slack.

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

Ideas

What you can automate in Mux

Spot a failed asset before a customer does, and know the moment a live stream starts, pauses or loses its connection. These are ready-made starting points. Anything else you can describe works too.
The moment it happens

Post failed Mux assets to Slack

You learn when a video fails to process, with the asset ID and the error.

See how it works
The moment it happens

Track your Mux live stream status in Slack

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

See how it works Your own logic

Any other automation you can describe in words

Your own rules, schedule and AI steps with Mux, plus any other app. Describe it and your assistant builds it.

See how to build your own

Build your own

Build any Mux automation you can describe

The ideas above are ready-made starting points, not a fixed list. Describe what Mux should do in your own words, with your conditions, other apps or an AI step, and 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.

For example, ask your assistant

Every hour, check Mux for assets that errored during processing and send me the asset IDs and errors.

When a Mux live stream goes active, post the stream name and playback link to our Slack channel.

Every day, pull Mux views per video, add them to Google Sheets, and create a Notion page summarizing which videos had the most rebuffering.

Beyond chat

Have Mux work when you're not in the chat

Connecting Mux to ChatGPT or Claude lets you ask about it while you chat. ClickRuntime handles the part that should happen on its own: checks on a schedule and actions on each new event, set up from the same chat and running after you close it.

Setup

Connect Mux

Mux connects with an access token ID and secret that an org admin generates. Each token belongs to one environment, so production needs a production token.

Mux

Video infrastructure

  1. In the Mux dashboard, open Settings, then Access Tokens. You need to be an org admin.
  2. Generate a new token, pick the environment (for example Production) and grant Mux Video read, plus Data if you need it.
  3. Copy the token ID and secret right away; Mux shows the secret only once.
  4. In the ClickRuntime dashboard, open Connections & secrets and save the token ID and secret as secrets for Mux.

Good to know

Mux limits that affect automations

  • A token works in one environment only. A development token is rejected by production, so match the token to the environment you want alerts for.
  • The token secret cannot be recovered after creation. If it is lost, generate a new token.
  • Webhooks are configured per environment, so set one up in each environment you want events from.
  • Only org admins can create access tokens.

FAQ

Questions about automating Mux

How quickly do Mux alerts arrive?
Both automations run on Mux webhooks, so the Slack message goes out when Mux sends the event, not on a timer.
Which live stream changes can I hear about?
The live stream events used here are active, idle and disconnected.
What does a failed-asset alert include?
The asset ID and the error Mux reported, so whoever picks it up can find the asset straight away.
Can I use one token for staging and production?
No. Mux tokens are tied to one environment. Create a token, and a webhook, in each environment.
Is AI involved?
Not in these alerts; they pass Mux events through to Slack. AI is part of every plan if you want it, and no AI key is needed.
Is this a Mux connector for ChatGPT or Claude?
Not for chatting with Mux data. A chat connector lets your assistant read and change Mux while you're in the conversation. ClickRuntime is for the work that should happen without you: you set up an automation from the chat once, and it keeps running on a schedule or on each Mux event.

Related pages

Keep exploring

Tell your assistant what Mux should do

Free plan. No credit card.

Add to ChatGPTAdd to Claude