Resources · Make integration

JW Player Make integrationAutomate JW Player with Make.

Can your video library react on its own when a new media goes live? The JW Player Make integration gives you 10 modules: 2 instant triggers, 7 actions and 1 search. This guide is for video and marketing teams, and it walks you from the connection to a first working scenario.

Try the JW Player integration on MakeSee the 10 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the JW Player Make integration do for you?

The JW Player Make integration links your JW Player account to Make, a tool where you build a scenario (an automation made of bricks called modules) without writing code. JW Player can alert Make the moment a media becomes available or changes, and Make can create, upload, update, search or delete media in return.

A library that fills itself. When a video file lands in another tool your team uses, Upload a Media (Single Upload) or Upload a Media (Multipart) sends it to JW Player, so nobody has to open the dashboard to drag files around.

A signal when a video is ready. Watch Media Available fires as soon as JW Player has finished making a media available. Pair it with Get a Media to pull the full record and pass it on to the next step of your process.

Clean-up you can trust. Search Media finds the media that match what you are looking for, then Update a Media corrects them or Delete a Media removes them, one bundle (one item passed between modules) at a time.

Make covers the modules listed below. For any other endpoint of the JW Player API, Make an API Call reuses the same connection. If you are still weighing tools, the n8n vs Make comparison sets the criteria side by side, and the Make review covers the editor in depth. When a scenario stops working, Make troubleshooting is the place to start.

Connect

How do you connect JW Player to Make?

  1. 01

    Copy your credentials from JW Player

    In your JW Player account dashboard, open the API credentials section and scroll to the V2 API credentials. Copy the API key shown there. Then go to the properties section and copy the Site ID of your property.

  2. 02

    Add a JW Player module in Make

    Open your scenario, add any JW Player module and click Create a connection. The connection is your JW Player account linked to Make once, and every JW Player module of the scenario reuses it.

  3. 03

    Paste the key and save

    Give the connection a name in Connection name if you like (it is optional), paste the credentials you copied, and follow the instructions on screen. Make then lists your JW Player data in the module fields.

First scenario

Your first scenario with JW Player

GoalWhen a media becomes available in JW Player, Make fetches its full record so the next step can use it.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to add the first module. Search for JW Player and pick Watch Media Available.

  2. 02

    Set up the webhook

    Click Create a webhook, then Create a connection and paste your API key and Site ID. From now on, JW Player notifies Make each time a media is ready.

  3. 03

    Add Get a Media

    Click the + on the right of the trigger and choose Get a Media. Map the media received by the trigger into the module, so Make knows which record to read.

  4. 04

    Test with Run once

    Click Run once, then publish or finish processing a test video in JW Player. Open the bubble above each module to read the bundles it received and check the record is complete.

  5. 05

    Switch it on

    Once the test looks right, turn the scenario on. Each new available media now starts one run, and every module that runs counts as one operation on your Make plan.

Triggers

What starts a JW Player scenario

2 modules start a scenario when something happens in JW Player. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by JW Player as soon as it happens.

JW Player1Watch Media Available

Watch Media Available

Instant trigger

In Make“Triggers when a media has become available.”

This trigger starts your scenario at the moment a media becomes available in JW Player, so the rest of the flow works on a video that viewers can already reach. It is the natural starting point for anything that should follow a publication.

How it fires
instant, JW Player calls Make through a webhook as soon as the media is available, with no waiting for a schedule.
When to use it
you want to announce, log or enrich a video only once it is actually ready, and not while it is still being uploaded.
Watch out
set it up with Create a webhook first, then the connection.
JW Player2Watch Media Updated

Watch Media Updated

Instant trigger

In Make“Triggers when a media has been updated.”

Here the scenario reacts to changes rather than arrivals: each time a media is updated in JW Player, Make receives it and can pass the new version down the chain. It keeps other tools in step with what your team edits in the dashboard.

How it fires
instant, JW Player notifies Make by webhook the moment the update happens.
When to use it
someone corrects a title or a description, and a catalog or a spreadsheet elsewhere should reflect it.
Watch out
if the same scenario also runs Update a Media on that media, it can start itself again, so keep the two apart.
Modules

What Make can do in JW Player

JW Player gives you 8 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

JW Player1

Create a Media

Action

In Make“Creates a new media by fetch or external upload methods.”

Adds a new media to your JW Player library by pointing JW Player to a file it fetches itself, or by preparing an external upload. You get a media entry without handling the file transfer inside Make.

When to use it
the video already sits at an address JW Player can reach, and you only need the entry created.
Watch out
when Make must push the file itself, the two Upload modules fit better.
JW Player2

Delete a Media

Action

In Make“Deletes one or more media.”

Removes one or several media from JW Player in a single step. Useful to keep the library tidy once a video has no reason to stay online.

When to use it
after Search Media has isolated the exact media to retire, for instance a campaign that has ended.
Watch out
point it at a test media first and check the result with Run once before switching the scenario on.
JW Player3

Get a Media

Action

In Make“Gets a media by ID.”

Reads a single media from its ID and returns its full record, ready to be mapped into the next module. Think of it as opening the media page, but inside the scenario.

When to use it
a trigger or another app hands you a media ID and you need the details that go with it.
Watch out
it needs an ID; if you only know a title, start with Search Media.
JW Player4

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Sends any authorized request to the JW Player API with the connection you already set up. It is the way out when none of the listed modules does exactly what you need.

When to use it
you found an endpoint in the JW Player API documentation that has no dedicated module in Make.
Watch out
you write the request yourself, so keep the vendor documentation open next to the editor.
JW Player5

Update a Media

Action

In Make“Updates a media.”

Changes an existing media in JW Player so its information stays correct without anyone editing it by hand. The media keeps its place in the library; only what you map is modified.

When to use it
a record in your CRM or content tool changed and the matching video should follow.
Watch out
paired with Watch Media Updated in the same scenario, it can trigger a new run on every change.
JW Player6

Upload a Media (Multipart)

Action

In Make“Creates a new media by a multipart upload method. Best for uploading media files that are 100MB to 25GB.”

Creates a new media by sending the file in several parts, which suits heavy video files. Make recommends it for files between 100 MB and 25 GB.

When to use it
long recordings, webinars or raw footage that are too big for a direct upload.
Watch out
for files of 100 MB or less, Upload a Media (Single Upload) is the simpler choice.
JW Player7

Upload a Media (Single Upload)

Action

In Make“Creates a new media by a direct upload method. Best for uploading media files that are 100 MB or less.”

Sends a video file straight to JW Player in one go and creates the media from it. It suits short clips and social videos.

When to use it
a file of 100 MB or less arrives from another module, such as a storage app, and should land in JW Player.
Watch out
above 100 MB, switch to Upload a Media (Multipart).
JW Player8

Search Media

Search

In Make“Searches for media or lists them all.”

Looks for media in your JW Player library, or lists all of them, and returns each result as its own bundle. That makes it the usual first step of any batch job on existing videos.

When to use it
before an update or a deletion, to select precisely which media are concerned.
Watch out
it can return zero, one or many bundles, and every module placed after it runs once per result.
Need help

Need help automating JW Player with Make?

A person reads every message.

FAQ

JW Player and Make: common questions

01Is the JW Player Make integration free?
Yes, on the Make side. JW Player is a standard app, available from the Free plan like the 3,000+ other standard apps. The Free plan allows 2 active scenarios, runs of 5 minutes at most, files up to 5 MB and 512 MB of data transfer. Scheduled runs are spaced by at least 15 minutes there, versus 1 minute on paid plans (Core, Pro, Teams, Enterprise), which also remove the cap on active scenarios. Usage is counted in operations each month. Your JW Player subscription is a separate matter, handled on the JW Player side.
02What do you need to connect JW Player to Make?
An active JW Player account with API credentials. In the account dashboard, open the API credentials section, scroll to the V2 API credentials and copy the API key. Then copy the Site ID shown for your property in the properties section. In Make, add a JW Player module, click Create a connection, optionally name it, and paste those credentials. For the two watch triggers, click Create a webhook first, then create the connection. After that, every JW Player module in your scenarios reuses the same connection.
03Does the JW Player trigger in Make work in real time?
Yes. Both JW Player triggers, Watch Media Available and Watch Media Updated, are instant: JW Player calls Make through a webhook as soon as the event happens, so the scenario does not wait for a schedule. This differs from scheduled triggers, where Make checks the app at an interval, every 15 minutes by default on a new scenario. Keep in mind that each run still counts operations, one per module executed, so a busy library generates more runs than a quiet one.
04What if a JW Player module is missing in Make?
Use Make an API Call. It sends any authorized request to the JW Player API with the connection you already have, so an endpoint without a dedicated module is still reachable from your scenario. You write the request yourself, with the JW Player documentation at hand. Make also points out that its JW Player documentation is AI-generated from the vendor documentation and may contain mistakes, so check important details directly with JW Player before you rely on them in production.
05Should you use Make or n8n for JW Player?
It depends on the tool your team already works in. On Make, JW Player comes with 10 modules, including 2 instant triggers, plus Make an API Call for the rest of the API, and it is available from the Free plan. The same app often has a node on n8n as well. The fair approach is to list the JW Player events and actions your process needs, check that each tool covers them, and pick the one where you will maintain the scenario comfortably over time.
Same platform

Other docs you might need on this stack.

Browse all integrations