OtherReal-timeUpdated May 2026

Mux

Mux developer video API and streaming

Mux is the developer-focused video API — handles ingestion, transcoding, adaptive streaming, and analytics for embedded video at scale. Used by companies that want to build video into their product (LMS platforms, fitness apps, video conferencing) without managing FFmpeg or origin servers themselves. Tiny Command exposes three actions, no triggers (Mux emits asset-lifecycle events via webhooks configured per-environment in the Mux dashboard; point at a Tiny Command webhook trigger URL): Create Asset from URL (Mux ingests from a publicly accessible URL — your S3, a hosted source — and starts transcoding), Get Asset (current state, plus the playback IDs and per-resolution URLs when ready), List Assets (paginated history with metadata). The connection uses a Mux access token + secret from Settings → API Access Tokens. Mux's playback model uses signed playback IDs — a single asset has one or more playback IDs (public or signed for token-protected playback). The signed-playback pattern is the standard for paid-content platforms — issue a JWT per viewer, embed with the JWT, only your server can mint valid JWTs.

Connect Mux

0triggers

3actions

≈ 2 minto set up

Freetier · no card

Actions

Do anything Mux can do, from a workflow.

Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.

Action	What it does	Inputs
Create Mux Asset from URL	Ingests video from a publicly accessible URL. Mux transcodes asynchronously; poll Get Asset until status=ready or use webhook callback. For "video already in S3 → ingest into Mux for streaming" workflows.	3 fields	View →
Get Mux Asset	Returns the asset by ID with status, playback IDs, recording duration. The lookup before embedding the playback URL downstream.	1 fields	View →
List Mux Assets	Paginated assets with status filter. For inventory and for "find videos uploaded last week" maintenance workflows.	2 fields	View →

Recipes

Pre-built Mux workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

Mux → Slack alerts

AI-triage every Mux event, ping the right channel only when it matters.

Mux → Google Sheets log

Every event matching a filter, appended to a running spreadsheet.

Mux → Notion database

Turn Mux into a Notion-backed source of truth, auto-tagged.

Before you build

Three things worth knowing.

Filter at the trigger

Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.

Authorize once, reuse anywhere

Connect Mux once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.

No JSON to read

Every Mux field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.

FAQ

Questions about the Mux integration.

If we missed yours, ping support. We usually reply within an hour.

How do I connect Mux to Tiny Command?

Open the Tiny Command workflow builder, drop in a Mux node, and click Connect. Authorize Mux once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.

What Mux triggers does Tiny Command support?

Tiny Command focuses on outbound actions for Mux today. Use Tiny Command's universal Webhook or Schedule trigger to start Mux workflows, then run any Mux action you need.

What Mux actions can I run from a workflow?

3 Mux actions are available out of the box, covering other operations like "Create Mux Asset from URL". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.

Is the Mux integration real-time?

Mux actions execute synchronously inside your workflow. Tiny Command waits for Mux's API to confirm before continuing to the next step, so downstream nodes can rely on the result.

Do I need to write code to use Mux with Tiny Command?

No. Every Mux trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any Mux API endpoint directly.

How much does the Mux integration cost?

There's a free tier you can start on without a credit card. Higher run volumes and team features come with paid plans. The Mux integration itself has no per-app surcharge.