Mattering Automations Mux integration
Connect Mux to Mattering Automations: video assets, playback IDs, live streams, direct uploads, and Mux Data analytics as workflow steps, authenticated with a Mux access token over HTTP Basic auth.
The Mattering Automations Mux integration adds Mux to your automation canvas: ingest video assets from URLs, create and retire playback IDs, run live streams end to end, hand out direct upload URLs for your own apps, and read Mux Data analytics, from individual video views to metric breakdowns, timeseries, and playback error lists.
Mux uses four kinds of IDs that are easy to mix up: asset IDs, playback IDs, upload IDs, and live stream IDs. Every ID field in this integration says which one it takes, and Mux: Resolve Playback ID exists to look up which asset or live stream a playback ID belongs to, so an ID copied out of a playback URL is never a dead end.
Setup takes a few minutes: create an access token in the Mux dashboard, attach its Token ID and Token Secret as a credential in Mattering, and run one read-only node to confirm it works. This guide walks through each step and ends with the full node reference.
Before you start
- A Mux account with access to the environment you want to automate.
- A Mattering workspace with access to the Automations app.
- Permission to create an access token in the Mux dashboard for that environment.
- A note on billing: Mux charges for encoding, storage, and streaming on a usage basis, so workflow steps that create assets or run live streams spend real money on your Mux account. Mux's test mode (a test flag on creation) produces free, watermarked, short-lived objects for rehearsing workflows.
Create a Mux access token
Mattering authenticates to Mux with an access token over HTTP Basic auth: the Token ID is the username and the Token Secret is the password. Tokens are created per environment in the Mux dashboard, carry separate permission toggles for Mux Video and Mux Data, and are shown once.
Connect Mux to Mattering
Verify it works
Open any automation canvas and check the palette: a Mux section should list the read and action nodes. Drop Mux: List Assets onto the canvas and run a test step. It takes no parameters, so a successful run proves the credential works: good credentials return the assets in the token's environment, bad ones return an authentication error. An empty list on a fresh environment still counts as success.
To go one step further, copy an asset's id from the list result and feed it to Mux: Get Asset. The response includes the asset's status, duration, tracks, and its playback IDs under data.playback_ids, which are the values most other nodes ask for. If the list came back empty but your dashboard shows videos, the token belongs to a different environment than the one you are looking at.
Node reference
32 nodes, generated from the connector itself so this reference always matches what ships.
Read and query nodes 16
Mux: Get Asset
mux_get_asset
Fetch a single video asset by its asset ID: status, duration, tracks, playback IDs, metadata.
Mux: Get Asset Input Info
mux_get_asset_input_info
Fetch details about an asset's ingest source files: container format, tracks, and the input settings used.
Mux: Get Asset Playback ID
mux_get_asset_playback_id
Fetch one playback ID on an asset (its policy and value). Takes both the asset ID and the playback ID.
Mux: Get Direct Upload
mux_get_upload
Fetch a direct upload by its upload ID. Once status is asset_created, the created asset's ID is in data.asset_id.
Mux: Get Live Stream
mux_get_live_stream
Fetch a single live stream by its live stream ID: status, stream key, playback IDs, settings.
Mux: Get Live Stream Playback ID
mux_get_live_stream_playback_id
Fetch one playback ID on a live stream (its policy and value). Takes both the live stream ID and the playback ID.
Mux: Get Video View
mux_get_video_view
Fetch every collected field for a single video view by its view ID (the id from Mux: List Video Views).
Mux: List Assets
mux_list_assets
List video assets in the Mux environment, newest first. Filterable by source live stream or direct upload. Clean auth probe: works with no parameters.
Mux: List Direct Uploads
mux_list_uploads
List direct uploads and their statuses: waiting, asset_created, errored, cancelled, timed_out.
Mux: List Live Streams
mux_list_live_streams
List live streams in the Mux environment (paginated).
Mux: List Playback Errors
mux_list_errors
List playback errors seen across video views in a timeframe, with counts and percentages.
Mux: List Video Views
mux_list_video_views
List individual playback sessions (video views) from Mux Data, filterable by viewer, error, dimension filters, and timeframe. Requires Mux Data permission on the access token.
Mux: Metric Breakdown
mux_metrics_breakdown
Break a Mux Data metric down by a dimension, e.g. video_startup_time by country or by video_title.
Mux: Metric Overall Values
mux_metrics_overall
Get the overall value of a Mux Data metric for a timeframe, plus total views and watch time.
Mux: Metric Timeseries
mux_metrics_timeseries
Get a Mux Data metric over time as a series of intervals, e.g. rebuffer_percentage per hour for the last day.
Mux: Resolve Playback ID
mux_resolve_playback_id
Look up which asset or live stream a playback ID belongs to. Use this when you only have the playback ID from a URL and need the owning object's ID.
Action nodes 16
Mux: Cancel Direct Upload
mux_cancel_upload
Cancel a direct upload that is still waiting for a file. Only succeeds while the upload status is waiting.
Mux: Create Asset Playback ID
mux_create_asset_playback_id
Create a new playback ID on an asset. The returned data.id is the playback ID to use in stream.mux.com playback URLs.
Mux: Create Asset from URL
mux_create_asset
Ingest a video into Mux from a publicly reachable file URL. Returns the new asset in status preparing; poll Mux: Get Asset (or use webhooks) until status is ready. Encoding is billable.
Mux: Create Direct Upload URL
mux_create_upload
Create a direct upload slot and get back a signed URL. Your own client or browser then PUTs the video file to that URL; this node does not upload the file itself. The finished asset's ID appears on the upload as asset_id once processed.
Mux: Create Live Stream
mux_create_live_stream
Create a live stream. Returns the stream key for the RTMP encoder plus a playback ID for viewers. Active streaming is billable.
Mux: Create Live Stream Playback ID
mux_create_live_stream_playback_id
Create a new playback ID on a live stream for viewers. The returned data.id goes in the stream.mux.com playback URL.
Mux: Delete Asset
mux_delete_asset
Permanently delete a video asset and all of its playback IDs. Irreversible: the video cannot be recovered.
Mux: Delete Asset Playback ID
mux_delete_asset_playback_id
Delete a playback ID from an asset. Every playback URL using that playback ID stops working immediately.
Mux: Delete Live Stream
mux_delete_live_stream
Permanently delete a live stream and its stream key. Already-recorded assets are kept but the stream itself cannot be recovered.
Mux: Delete Live Stream Playback ID
mux_delete_live_stream_playback_id
Delete a playback ID from a live stream. Every playback URL using that playback ID stops working immediately.
Mux: Disable Live Stream
mux_disable_live_stream
Disable a live stream: any active broadcast ends and new RTMP connections are refused until re-enabled.
Mux: Enable Live Stream
mux_enable_live_stream
Enable a disabled live stream so it accepts an incoming RTMP connection again.
Mux: Reset Stream Key
mux_reset_stream_key
Generate a new stream key for a live stream. The old key stops working immediately: any encoder still configured with it can no longer broadcast.
Mux: Signal Live Stream Complete
mux_complete_live_stream
Signal that the broadcast is over: closes out the live playback (EXT-X-ENDLIST) without waiting for the reconnect window.
Mux: Update Asset
mux_update_asset
Update an asset's passthrough or meta metadata. Video content itself is immutable after ingest.
Mux: Update Live Stream
mux_update_live_stream
Update a live stream's settings: passthrough, latency mode, reconnect window, max duration, or new-asset settings.
Using the integration
On the automation canvas
Mux nodes chain with every other node: a finished render can ingest itself with Mux: Create Asset from URL, an AI step can summarize playback errors before anyone reads them, and the playback link can land in a Mattering Productivity task. The four delete nodes and Mux: Reset Stream Key act irreversibly on live video infrastructure, so put a condition or an approval step in front of them in any workflow that runs unattended.
From AI assistants over MCP
Every node speaks MCP, the open protocol for connecting AI assistants to tools. Claude, ChatGPT, and Matter can list assets, mint playback IDs, control live streams, and read analytics through the same nodes your workflows use.
Keeping Mux IDs straight
Asset IDs, playback IDs, upload IDs, and live stream IDs are four separate namespaces that look alike. The ID inside a stream.mux.com URL is a playback ID, not an asset ID, and Mux: Resolve Playback ID looks up the asset or live stream that owns it. A direct upload's own ID is a third thing again: once its status is asset_created, the created asset's ID sits on the upload as asset_id, readable with Mux: Get Direct Upload. Every ID field on every node states which namespace it expects.
Direct uploads without pretending
Mux: Create Direct Upload URL creates an upload slot and returns a signed URL; your own client or browser then PUTs the video file to that URL. The node never touches file bytes, so the workflow's job is to create the slot, hand the URL to your app, and watch Mux: Get Direct Upload or Mux: List Direct Uploads until the status reads asset_created, cancelled, timed_out, or errored.
Reading Mux Data analytics
The analytics nodes read Mux Data, which collects from real player sessions. Mux: Metric Overall Values gives a metric's value for a timeframe plus total views and watch time, Mux: Metric Timeseries returns it over time, Mux: Metric Breakdown splits it by a dimension such as country or video title, and Mux: List Playback Errors counts errors across views. They need a token with Mux Data permission, and on an environment with no player traffic they return empty results with a successful status.
Beyond the typed fields
Every create and update node accepts an extra body object that is merged into the request, and every read node accepts extra query parameters. Documented Mux settings a node does not list individually, such as static renditions or generated subtitles on asset creation, stay reachable without waiting on a connector update.
Troubleshooting
Every node returns an authentication error
The video nodes work but the analytics nodes fail
Mux: List Assets returns an empty list but the dashboard shows videos
A node says the resource was not found for an ID you are sure exists
A deleted playback ID's URL still plays, or a working URL suddenly stopped
A direct upload sits in waiting forever
An asset created from a URL comes back errored instead of ready
The encoder cannot connect after a stream key reset
Related
The Mux MCP
What connecting Mux unlocks for AI agents and automations, with common uses and FAQs.
More guides
All Automations documentation
Every integration guide, plus how connectors, credentials, and workflows fit together.
Mux is a trademark of its respective owner. Mattering uses platform names to identify the services these integrations connect to; no endorsement or affiliation is implied.