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.

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

Send this to your assistant

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.

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 creator uploads a 40-minute webinar recording through your product, the upload finishes, and the player shows a spinner forever. On Mux, the asset moved to the errored state because the file was corrupt, the codec was unsupported or the source URL could not be fetched. Nobody on your side knows until the user emails support a day later, by which time they have uploaded it twice and are frustrated.

When Mux sends a video.asset.errored webhook, ClickRuntime receives it as it arrives, formats the asset ID, the error type and message, and the passthrough value you attached to the upload, then posts it to the Slack channel or inbox you choose. There is no polling, so the notice appears moments after processing fails.

Teams that run user-generated video, course platforms and internal training libraries rely on it the most.

What you get out of it

Customers are contacted before they complain
A failed asset becomes a message to the support channel within seconds. Someone can write to the uploader that the file needs re-exporting, which beats a ticket arriving after two retries.
Support starts with the facts
The post carries the asset ID and Mux's error message, such as an invalid input file. The person answering knows whether to ask for a new export or to escalate a pipeline bug.
Pipeline bugs show up as a pattern
Five errors in an hour from one source indicate a regression, for example a transcoding setting or a broken upload URL. Seeing them in sequence in a channel makes that obvious, whereas one email would not.
Storage and encoding spend is not wasted
Assets stuck in errored state still occupy records and retries. Knowing about them quickly lets you delete them or retry the upload instead of paying for repeated failed processing. Retrying or deleting them early keeps your asset list clean.
Launches and live content are protected
If a keynote recording fails minutes before it is meant to go public, the team hears right away. Hours of delay can cost an event its audience. Hours of delay can cost an event its audience and a creator their trust.

How it works

What happens, step by step

When a video fails to process in Mux, Mux tells ClickRuntime straight away.
ClickRuntime ignores anything outside your production environment.
A message appears in your #video-ops Slack channel with the video's ID and the error Mux reported.

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

Post failed Mux assets to Slackjust nowSucceeded

Slack · #video-ops❌ Mux asset Vf3Xk00aBc errored: The input file contains no video stream

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.

asset_errored_alert.pyexample

from clickruntime import on_event, notify

@on_event
def handle(event):
    body = event.json or {}
    if body.get("type") != "video.asset.errored" or body.get("environment", {}).get("name") != "Production":
        return {"skipped": True}
    asset = body["data"]
    errors = "; ".join((asset.get("errors") or {}).get("messages", [])) or "no message"
    notify.slack(f"❌ Mux asset {asset['id']} errored: {errors}", channel="#video-ops")
    return {"asset": asset["id"]}

FAQ

Common questions

Which Mux webhook does it use?

It listens for video.asset.errored, which Mux sends when an asset fails during ingest or processing. You paste the ClickRuntime webhook URL into the Webhooks section of your Mux environment settings. Mux retries delivery if your endpoint is down, so nothing is lost.

Can I tell which user uploaded the failed video?

Yes, if you set a passthrough value or metadata on the upload, such as a user ID, Mux includes it in the event and the alert can show it. Without that, the asset ID is the identifier.

Does it also report successes?

Not by default, since the point is quiet monitoring. A separate message for asset.ready is possible if you want confirmation of each upload, but most teams limit alerts to failures to keep the channel useful.

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