Short answer: You can list mux assets in Mux by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Mux List Mux Assets action to a workflow, map its 2 inputs 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 |
|---|---|---|---|
Page Size limit | number | Optional | – |
Page page | number | Optional | – |
{"limit": "{{trigger.limit}}","page": "{{trigger.page}}"}
{"data": [{"id": "asset_abc","status": "ready","duration": 184.5,"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.