--- title: "JW Player Integration" description: "Manage a JW Player video library from your workflows. Agents ingest videos from external URLs with metadata set at creation, update titles, descriptions, and tags, check encoding status before publishing downstream, and list media and playlists." url: https://flowrunner.ai/integrations/jw-player date_modified: 2026-08-04T10:04:16-07:00 --- # JW Player [CMS & Content](https://flowrunner.ai/integrations/category/cms-content) Manage a JW Player video library from your workflows. Agents ingest videos from external URLs with metadata set at creation, update titles, descriptions, and tags, check encoding status before publishing downstream, and list media and playlists. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 6 actions · API key · available [JW Player website](https://jwplayer.com/) · [Platform Documentation](https://docs.jwplayer.com/platform) · Capability data verified 2026-07-28 1. An upstream workflow finishes producing a final MP4 and hands over its download URL 2. Create Media from URL ingests the file into the JW Player property with title, description, and tags set at creation 3. Get Media polls the new media ID until encoding status progresses from processing to ready 4. Update Media applies the final metadata from the content calendar: corrected title, campaign tags, author 5. The content channel receives the media ID, title, and player preview link 6. The content owner watches the encoded video before it goes into a public playlist, because a transcoding artifact or wrong cut reaches every embed at once 7. On approval, the publish step embeds the media ID into the CMS post and the video goes live ## What This Integration Enables A video library is infrastructure, not a folder of files. Every media ID in a JW Player property is a live endpoint that players across your sites and apps resolve at view time, which means the library deserves the same discipline as any production system: automated ingest, status-gated releases, synced metadata, and audited cleanup. FlowRunner agents run that discipline. They ingest renders by URL the moment an upstream step produces them, hold publishing until the encoder reports ready, and keep titles, descriptions, and tags aligned with the CMS that editorial actually maintains. The people who make the videos never touch the dashboard, and the property still behaves like someone curates it daily. - Ingest videos from any publicly accessible URL, with title, description, tags, and author set at creation - Poll encoding status and gate downstream publishing on ready - Update metadata partially and safely: only provided fields change, and nothing re-encodes - Search and enumerate the library with free-text search across titles, descriptions, tags, and status - List playlists, including manual, dynamic, and recommendations types, for placement decisions - Keep permanent deletion behind [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) review ### Without FlowRunner **Ingest is a browser upload**: Someone downloads the render, uploads it through the dashboard, and retypes the metadata **Publishing races the encoder**: Pages go live embedding a video still in processing, and visitors get a spinner **The library quietly rots**: Titles drift from the CMS, tags stop matching campaigns, and nobody can say what is safe to remove ### With FlowRunner **Ingest is a URL handoff**: Any workflow that produces a video passes its download URL, and metadata is set at creation **Ready status gates the release**: Agents poll encoding status and downstream publishing waits for ready, not for luck **The library is auditable inventory**: Scheduled sweeps log every video's ID, status, and metadata, and cleanup runs against evidence ## Use Case Scenarios ### Render to published post without a dashboard login A production workflow finishes a tutorial video and stores the MP4. The agent passes the download URL to Create Media from URL with the title and campaign tags already set, then polls Get Media until status reads ready. It notifies the content team in [Slack](https://flowrunner.ai/integrations/slack) with the preview, and once the owner approves the encode, the agent creates the article in [WordPress](https://flowrunner.ai/integrations/wordpress) with the media ID embedded. The gap between final render and live post is however long the encoder and one human review take, not however long the upload sits in someone's task list. ### The metadata sync that ends title drift Editorial manages video titles, descriptions, and tags in the CMS, but the player shows what JW Player has. A nightly agent walks List Media, compares each record against the CMS entry, and calls Update Media on mismatches, changing only the drifted fields. Because updates are partial and never touch the video file, the sync is safe to run every night. Search on the site, recommendations in playlists, and analytics groupings all inherit the corrected metadata, and the CMS becomes the single place anyone edits. ### Library inventory that makes cleanup an evidence-based decision Quarterly, an agent pages through List Media and List Playlists and writes the full inventory to [Google Sheets](https://flowrunner.ai/integrations/google-sheets): media ID, title, duration, encoding status, tags, and which playlists reference each video. Stale candidates, videos with dead tags and no playlist membership, get flagged in a review tab. The content owner works the tab, marks what dies, and the agent executes only the approved deletions. The library stays lean without anyone deleting from memory. ## Human-in-Loop Highlight Delete Media removes the hosted video and its metadata permanently, and the blast radius is every embed that references the media ID: pages, apps, and playlists all go dark on that video the moment it disappears, with no undo on JW Player's side. Worse, if the original render no longer exists upstream, the deleted encode was the last copy. So FlowRunner agents never delete media inside an unattended loop. The cleanup sweep builds the case per video: "Media a1b2c3d4, 'Q3 webinar teaser', not in any playlist, tags reference a campaign that ended in January. Delete?" The content owner confirms, the agent runs Delete Media and records the confirmation it returns. A wrong metadata update costs one more Update Media call. A wrong deletion costs a video you may not have anymore. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 6 actions ### Media 5 - **List Media** Lists the videos hosted in the property, newest first, with free-text search across titles, descriptions, tags, and status, plus page-based pagination and a total count. The inventory and lookup step behind audits and syncs. - **Get Media** Retrieves the full record for a single media item by ID, including metadata, hosting type, encoding status, duration, and delivery details. The polling step that gates publishing on ready. - **Create Media from URL** Creates a new media item by ingesting a video from a publicly accessible download URL, with title, description, and tags set at creation. JW Player fetches, transcodes, and hosts the file, and status progresses from processing to ready asynchronously. - **Update Media** Updates a media item's metadata: title, description, tags, or author. Only provided fields change, omitted fields stay untouched, and nothing is re-uploaded or re-encoded. The safe workhorse of nightly metadata syncs. - **Delete Media** Permanently deletes a media item, removing the hosted video and its metadata. Cannot be undone, and every embed referencing the media ID goes dark. The operation this page's human gate exists for. ### Playlists 1 - **List Playlists** Lists the playlists configured in the property, including manual, dynamic, and recommendations playlists, with pagination and a total count. Used to check placement and reference before cleanup or reporting. ## Frequently Asked Questions ### What can FlowRunner do with JW Player? FlowRunner agents can run List Media, Get Media, and Create Media from URL in JW Player, plus 3 more actions. ### Does connecting JW Player to FlowRunner require OAuth? No. JW Player connects to FlowRunner with an API key, no OAuth flow required. ### Can JW Player trigger a FlowRunner workflow automatically? JW Player doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at JW Player?** This integration exposes JW Player to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/jw-player. Site index: https://flowrunner.ai/llms.txt