Resources · Zapier integration

JW Player Zapier integrationAutomate JW Player with Zapier.

The JW Player Zapier integration gives you 2 triggers, 2 actions and 1 search to wire your video library into the rest of your tools. Here is what each one does, what it costs you in tasks, and where it tends to break first.

See the 5 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the JW Player Zapier integration actually does

The integration links your JW Player account to Zapier so that something happening to your videos can start work in other apps, and the other way round. A new video ready to play, a media record that changed, a file sitting at a URL: each can kick off an automation without anyone copying data by hand.

Three results people usually build first. A heads-up the moment a video is live: Media Available fires as soon as JW Player finishes converting a new upload, so your content team hears about it before anyone asks. A library that fills itself: Upload Media via URL pushes a file that already lives somewhere else into JW Player, so a video dropped in a shared folder lands in your player library without a manual upload. Records that stay in sync: Find a Media looks up an existing video, then Update Media changes it, which is how a status set in another tool ends up on the right asset.

What Zapier does not do here matters just as much. There are only 5 operations on offer. No trigger for deleted videos, no action to delete or move one, nothing on playlists or players. If your plan depends on one of those, check the JW Player Make integration before you commit, or read Make vs Zapier to see how the two tools differ in general.

One more thing to know from day one: of the two triggers, only Media Available is instant. It reacts straight away even on the free plan, while Media Updated waits for Zapier's next check. Pick your trigger with that in mind.

Vocabulary

The Zapier vocabulary in one minute

Eight words come back on every page about Zapier. Here they are in plain English.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier sits and waits for that event.
Action
What the Zap does after it starts: the step that writes, sends or uploads something on your behalf.
Task
The unit Zapier bills you for: one action your Zap completes successfully. Your plan's allowance counts those.
Polling vs instant trigger
A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself the second the event happens.
Filter
A step that lets the Zap continue only when the incoming data meets a condition you set, and stops it otherwise.
Search step
A step that looks up something already stored in an app, so the steps after it can reuse what it found.
Connection
Your JW Player account linked to Zapier once, then reused by every step in every Zap that touches JW Player.
Cost

What a JW Player Zap really costs

JW Player is not a premium app on Zapier, so it works from the free plan. The bill is counted in tasks, not in Zaps.

  • Free plan100 tasks a month, unlimited Zaps
  • Free plan Zap size2 steps: one trigger, one action
  • Trigger and checks0 tasks
  • JW Player on the free planYes, it is not a premium app

The trigger never costs anything, and neither does Zapier checking for new data, however often it looks. Each action that succeeds counts as one task, so a Zap with three actions uses three times what a one-action Zap uses. An action that fails is not counted. The catch on the free plan: it only builds two-step Zaps, one trigger and one action. Add a filter, a search or a second action and you have a multi-step Zap, which needs a paid plan.

Connect

Connect JW Player to Zapier in 3 steps

  1. 01

    Open your connections

    In Zapier, go to the Apps page of your account and click + Add connection. A dialog opens with a search box; type JW Player and pick it from the list.

  2. 02

    Sign in to JW Player

    Click Add connection. A new tab opens on JW Player: sign in with the account that owns the videos, or one that has read and write access to the ones you want the Zap to touch.

  3. 03

    Grant access

    Allow Zapier to use the account. The connection then shows up in your list, and every JW Player step in every Zap can reuse it without asking you to sign in again.

First Zap

Your first Zap: post in Slack when a new video is ready

GoalWhen JW Player finishes converting a new upload, tell the marketing channel in Slack, but only for videos that match a condition you choose.

  1. 01

    Create the Zap

    Start a new Zap. Pick JW Player as the app that starts it and Media Available as the event, then choose your connection.

  2. 02

    Set the trigger

    Choose the Property and the media events you want to hear about. Both are required, so the step stays incomplete until they are filled.

  3. 03

    Test the trigger

    Run the test. Zapier brings back the three most recent items from your account, so you map the next steps on a real video, not a made-up one.

  4. 04

    Add the filter

    From the plus icon, add Filter, then set the field, the rule and the value. Use a text rule on a text field, or the filter never passes.

  5. 05

    Add Slack and map fields

    Add Slack as the action, pick the channel, and drop the video title from the trigger into the message so the team knows which one went live.

  6. 06

    Test and publish

    Test the Slack step, read what came back, then click Publish. With a filter inside, this Zap is multi-step and needs a paid plan.

Triggers

JW Player triggers on Zapier

2 events start a Zap when something happens in JW Player, and one of them is instant: the app calls Zapier straight away, whatever your plan.

1

Media Available

Instant trigger

In Zapier“Triggers when a conversion for a new media are completed or media becomes available.”

Starts your Zap once JW Player has finished converting a newly added video, or once a media becomes available to play. It is the closest thing to a "your video is live" signal you can get on Zapier.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
you want a team, a client or a spreadsheet to know a video is ready without anyone refreshing the dashboard.
Watch out
you have to choose which media events to subscribe to and which properties to listen to, and both fields are required before the step can be tested.
2

Media Updated

Polling trigger

In Zapier“Triggers when a media is updated.”

Watches one of your properties and starts the Zap when an existing video changes. Good for keeping a catalog, a CMS or a reporting sheet in line with what is actually in JW Player.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
an editor fixes a title in JW Player and you want the same change to show up in your content tracker.
Watch out
never point an Update Media action at the same property this trigger watches, or each update will set the Zap off again.
Actions

JW Player actions on Zapier

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

1

Update Media

Action

In Zapier“Updates a media.”

Changes an existing video in your library, identified by its media ID, inside the property you pick.

When to use it
a review tool marks a video as approved and you want that decision written back onto the asset.
Watch out
the ID is required, so if no earlier step carries it, put Find a Media in front.
2

Upload Media via URL

Action

In Zapier“Upload media to JW Player”

Adds a new video to a JW Player property from a file that already sits at a web address, so nobody downloads and re-uploads it.

When to use it
a production partner drops final cuts in a shared folder and you want each one in your library as soon as it appears.
Watch out
the file and the property are both required fields.
Searches

JW Player search on Zapier

1 search step looks for data that already exists in JW Player, so a later step can use it.

A search step finds a video that already exists so later steps can use it. In the editor, searches sit at the bottom of the Action event list, under SEARCH. Three settings decide what happens when the result is not clean.

1

Find a Media

Search

In Zapier“Finds a media.”

Looks up a video in a given property and hands its details, including its ID, to the next steps of the Zap.

When to use it
the only thing your other tool knows is a title or reference, and Update Media needs the real media ID.
Watch out
whether it wants an exact match or something close is decided by JW Player, so test it with a real value before you publish.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there and skips the steps that needed it. Switch it on and the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    This box turns a search into find-or-create. JW Player offers no such variant on Zapier, so you will not see it on Find a Media.
  3. If multiple search results are found?
    Three ways out: keep the first match (the default), stop the Zap, or pass every match on at once.
When it breaks

When a JW Player Zap breaks

Zapier attaches no help article to JW Player, so the failures to plan for are the general ones. They hit video Zaps harder than most because libraries are big and get edited in batches.

Four cases come back again and again. If one of them already bit you, the Zapier troubleshooting page goes further.

  • Your back catalog is ignored

    A Zap only reacts to what happens after you switch it on. The hundreds of videos already in JW Player are never picked up; moving them is a separate job.

  • The Zap that feeds itself

    Media Updated watching a property while Update Media writes into that same property: every update fires the trigger again and your task count drains fast.

  • A bulk import gets held back

    Upload a whole season at once and the trigger may return a huge batch. Zapier's flood protection can then hold those items back instead of running them all.

  • The same video twice? Not on polling

    On Media Updated, Zapier remembers what it has already seen, so the same item does not start the Zap twice. No need to build your own guard against duplicates.
Need help

Need help automating JW Player with Zapier?

A person reads every message.

FAQ

JW Player Zapier integration: common questions

01Is the JW Player Zapier integration free?
Yes, you can use it on the free plan, because JW Player is not one of the apps Zapier keeps for paid plans. The free plan gives you 100 tasks a month and as many Zaps as you like. The limit is the shape of the Zap: two steps only, one trigger and one action. As soon as you add a filter, a search like Find a Media or a second action, the Zap becomes multi-step and you need a paid plan to switch it on.
02How many tasks does a JW Player Zap use?
One task per action that succeeds, and nothing else. The trigger is free, and Zapier checking JW Player for changes is free too, however often it happens. A Zap with Media Available followed by one Slack message costs one task per new video. Add Update Media after it and each video costs two. An action that fails is not billed, but a Zap that loops on itself can still burn through the allowance quickly.
03Does JW Player trigger Zaps in real time?
Only one of the two triggers does. Media Available is instant: JW Player tells Zapier the moment a video is ready, and the Zap runs straight away on every plan, the free one included. Media Updated works by polling: Zapier asks JW Player for changes at a fixed interval, which is 15 minutes on the free plan, 2 on Professional, and 1 on Team and Enterprise. If speed matters, build around Media Available.
04What do you need to connect JW Player to Zapier?
A JW Player account, and read or write access to any videos you do not own but want the Zap to touch. In Zapier you open the Apps page, click + Add connection, pick JW Player, sign in in the tab that opens and grant access. Then check that the account can see the property your videos live in, because every JW Player step asks for one and will not work without it.
05Why does Update Media ask for an ID it can't find?
Because Update Media needs the media ID to know which video to change, and the field is required. If your Zap starts in another tool, that tool rarely holds the JW Player ID. The fix is to place Find a Media before the update: it looks the video up and passes its ID along. Keep in mind that the search step turns the Zap into a multi-step one, which needs a paid plan.
06What if the JW Player operation you need is missing?
Then Zapier cannot do it with the built-in steps, because the list is short: two triggers, two actions and one search. There is nothing for deleting a video, handling playlists or reacting to a deletion. The practical move is to check whether another automation tool covers that gap for JW Player, or to rethink the flow around the five operations that exist, for example by updating a record rather than removing it.
07Zapier, Make or n8n for JW Player?
It depends on your criteria rather than on a winner. Zapier is the quickest to set up, and its instant Media Available trigger works even on the free plan. If you need operations Zapier does not offer, compare the list on the Make side. If you care about hosting the automation yourself or about cost at high volume, n8n is the one to look at. Check the operations first, then pricing and who will maintain it.
Same platform

Other docs you might need on this stack.

Browse all integrations