Short answer: Drop the "Mux → Create Mux Asset from URL" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Source URL input_url | string | Required | Public URL Mux can fetch. HTTPS recommended. |
Playback Policy playback_policy | options | Optional | — |
MP4 Support mp4_support | options | Optional | Whether to generate static MP4 renditions in addition to HLS. |
{"input_url": "https://my-cdn.example.com/video.mp4","playback_policy": "{{trigger.playback_policy}}","mp4_support": "{{trigger.mp4_support}}"}
{"data": {"id": "asset_abc","status": "preparing","playback_ids": [{"id": "play_abc","policy": "public"}]}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.