Short answer: You can get mux asset in Mux by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Mux Get Mux Asset action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Asset ID asset_id | string | Required | The Asset ID assigned by Mux. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label. |
{"asset_id": "asset_abc..."}
{"data": {"id": "asset_abc","status": "ready","duration": 184.5,"aspect_ratio": "16:9","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.