Resources · Make integration

Wistia Make integrationAutomate Wistia with Make.

New video in Wistia, and the rest of the work follows on its own? The Wistia Make integration gives you 16 modules: 3 triggers, 11 actions and 2 searches. This guide connects your account, then walks you through a first scenario, click by click.

Try the Wistia integration on MakeSee the 16 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Wistia Make integration do for you?

The Wistia Make integration links your Wistia account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a single brick such as a trigger, an action or a search. Wistia brings 16 of those bricks, so your videos and projects can talk to the other apps you use.

Embed codes that write themselves. A marketing team drops a finished video into a Wistia project. Watch New Videos spots it, Create an Embed Code turns it into a snippet, and the next module sends that snippet wherever the web team works.

A clean project for every client. An agency that signs a new client can start from a template: Copy a Project duplicates it with all its media and sections, then Update a Project renames it. Nobody rebuilds the same folder structure by hand.

Visitors that reach your sales tools. Watch New Visitors picks up each new viewer Wistia records, so a sales rep can see who watched before picking up the phone.

One limit to know before you start: all three Wistia triggers are scheduled, which means Make checks Wistia at the rhythm you set instead of Wistia pinging Make. For anything the listed modules skip, Make an API Call reaches the rest of the API with the same account. If you are weighing both tools, the n8n vs Make comparison sets out the criteria, and the Make training covers the editor from scratch. Rather hand the build to someone else? The Make agency builds scenarios like these for its clients.

Connect

How do you connect Wistia to Make?

  1. 01

    Copy your Wistia API token

    In Wistia, open the Account Settings page, click the API tab and copy the token shown when it is created. Make sure it has the permissions your scenario needs, since Make can only do what the token allows.

  2. 02

    Open a Wistia module in Make

    Add any Wistia module to your scenario and click Create a connection. A connection is your Wistia account linked to Make once, then reused by every Wistia module. The Connection name field is optional.

  3. 03

    Paste the token and save

    Paste the API token you copied, or follow the on-screen instructions, then confirm. Make now lists your Wistia projects right inside the module, so you pick them instead of typing IDs.

First scenario

Your first scenario: an embed code for every new video

GoalWhen a new video lands in a Wistia project, Make creates its embed code.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big +. Search for Wistia and choose Watch New Videos as the first module.

  2. 02

    Link your account

    Click Create a connection and paste your API token. Once the connection exists, Make can read your projects and offer them as a list.

  3. 03

    Pick the project to watch

    Choose the Wistia project where finished videos go. Only videos added to that project will start the scenario, so a draft folder stays out of the flow.

  4. 04

    Add the embed code step

    Click the + on the right of the trigger and add Create an Embed Code. Map the video data from the trigger into its URL field instead of pasting a fixed link.

  5. 05

    Test with Run once

    Add a video to the project, then click Run once. Then read the bundles each module received: one bundle is one video passing from module to module.

  6. 06

    Schedule and switch on

    Click the clock on the first module. A new scenario runs every 15 minutes by default, and the Free plan cannot go lower. Pick your interval and switch the scenario on.

Triggers

What can start a Wistia scenario?

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

Wistia1Watch New Projects

Watch New Projects

Scheduled trigger

In Make“Triggers when a new project has been added.”

Each project created in your Wistia account becomes a bundle that starts your scenario, so the tools around Wistia learn about it without anyone copying names across.

How it fires
scheduled. Make checks Wistia on the scenario's schedule, which is every 15 minutes on a new scenario, and picks up the projects added since the last check.
When to use it
your team opens one project per client or per campaign, and you want a matching folder or a task created elsewhere as soon as the project appears.
Watch out
avoid pairing it with Copy a Project or Create a Project in the same scenario, since the new project would wake the trigger again.
Wistia2Watch New Videos

Watch New Videos

Scheduled trigger

In Make“Triggers when a new video has been added to a specific project.”

This trigger keeps an eye on one project you choose and hands Make every video added to it, one bundle per video. It is the natural starting point for anything that should happen after an upload.

How it fires
scheduled. Make checks the project at the rhythm set on the scenario, not the moment the upload ends.
When to use it
a project holds only approved videos, and each new one should get an embed code, a notification to the team or a row in a content tracker.
Watch out
it watches a single project, so a video parked in another project will not start this scenario.
Wistia3Watch New Visitors

Watch New Visitors

Scheduled trigger

In Make“Triggers when a new visitor has been added.”

With this trigger, each new visitor Wistia records flows into Make as a bundle you can send to a CRM, a spreadsheet or a chat channel. Viewing activity stops living only inside Wistia.

How it fires
scheduled. Make asks Wistia for new visitors on the scenario's schedule, so a visitor shows up at the next check rather than instantly.
When to use it
sales wants to know which prospects watched a demo video before calling them back.
Watch out
every visitor is one bundle, and each module that processes it counts one operation, the unit Make charges on your plan. A busy video can use your budget fast.
Modules

What can Make do in Wistia?

Wistia gives you 13 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Wistia1

Copy a Project

Action

In Make“Copies a project, including all media and sections.”

Duplicates an existing project with all of its media and sections, which gives you a ready-made structure in one step instead of rebuilding it.

When to use it
a template project for onboarding videos is cloned for each new client the moment the deal is signed in your CRM.
Watch out
the copy brings every video along, so keep the template lean if you only need its sections.
Wistia2

Create an Embed Code

Action

In Make“Creates an embed code for the specified URL.”

Produces the embed code for the URL you give it, so the snippet a web page needs is ready without opening Wistia and copying it from the share menu.

When to use it
right after Watch New Videos, to hand the web team or a content tool a code it can paste into a landing page.
Watch out
map the URL from the previous module; a fixed link would return the same code on every run.
Wistia3

Create a Project

Action

In Make“Creates a new project.”

Opens a new, empty project in your Wistia account from data coming out of another app, so project names follow your own naming rule every time.

When to use it
a new campaign is added in your planning tool and the video team should find its project waiting in Wistia.
Watch out
choose Copy a Project instead when the new project should start with existing videos and sections.
Wistia4

Delete a Media

Action

In Make“Deletes a media specified by ID.”

Removes one media from Wistia, identified by its ID, which keeps the library tidy once a video has no reason to stay online.

When to use it
a product is withdrawn from your catalog and its demo video should disappear with it.
Watch out
a deletion cannot be undone from Make. Test with Run once on a throwaway video and read the ID it received before switching the scenario on.
Wistia5

Delete a Project

Action

In Make“Removes a project specified by ID.”

Takes a whole project out of Wistia by its ID. It is the cleanup step at the end of a client or campaign lifecycle.

When to use it
a client contract closes in your CRM and the project created for that client is no longer needed.
Watch out
a project holds media, so this reaches much further than Delete a Media. Read the project name in a Run once test before switching the scenario on.
Wistia6

Get a Media

Action

In Make“Retrieves a single media specified by hashed ID.”

Fetches the details of one media from its hashed ID, so later modules work with fresh information about that video rather than a stale copy.

When to use it
another app only stores the video's hashed ID, and you need the rest of its data before writing a report or a message.
Watch out
it expects the hashed ID, not the project ID; mapping the wrong one returns nothing useful.
Wistia7

Get a Project

Action

In Make“Retrieves a single project specified by ID.”

Reads a single project by its ID and returns it as one bundle, handy when you already know which project you mean and just need its details.

When to use it
a form or a CRM record stores the project ID, and the next step needs that project's information to fill in an email or a sheet.
Watch out
to find a project you only know by name, start with List Projects instead.
Wistia8

Make an API Call

Action

In Make“Performs an arbitary authorized API call.”

Sends your own request to the Wistia API with the connection you already set up, so you reach what the other 15 modules leave out without managing a new login.

When to use it
the action you need does not appear in the list above, and you have found the matching endpoint in the Wistia API reference.
Watch out
you write the request yourself, so check the API reference for the path and method before running it.
Wistia9

Update a Media

Action

In Make“Updates a media specified by ID.”

Changes an existing media identified by its ID, which lets another tool keep your Wistia library in line with the source of truth.

When to use it
a product is renamed in your catalog and the video attached to it should carry the new name as well.
Watch out
the ID must come from an earlier module such as Search Medias or Watch New Videos; a typed ID breaks as soon as the video changes.
Wistia10

Update a Project

Action

In Make“Updates a project specified by ID.”

Edits a project picked by its ID, the usual follow-up when something else in your stack changes and Wistia should reflect it.

When to use it
right after Copy a Project, to rename the fresh copy after the client it now belongs to.
Watch out
run it on a test project first, because the change lands straight in the live account where your team works.
Wistia11

Upload a Video

Action

In Make“Uploads a new video to the Wistia account.”

Sends a new video into your Wistia account, which spares someone the download and upload dance between tools.

When to use it
a video editor exports the final cut to a cloud storage folder, and Make picks up the file and pushes it to Wistia.
Watch out
on the Free plan Make handles files up to 5 MB and 512 MB of transfer, so check that your videos fit your plan before relying on this step.
Wistia12

List Projects

Search

In Make“Lists all account's projects.”

Returns every project in the account, one bundle each, so the following modules can loop over your whole Wistia catalog.

When to use it
a manager wants a spreadsheet listing each project, or you need to find the ID of a project known only by its name.
Watch out
each project becomes a bundle, and every module after this one runs once per bundle, which adds up in operations on a large account.
Wistia13

Search Medias

Search

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

Looks up medias in your account, or lists all of them, and returns zero, one or several bundles you can act on next.

When to use it
you need the ID of a specific video before Update a Media or Delete a Media can touch it.
Watch out
a search can come back empty. Plan for that case, otherwise the next modules simply never run and the scenario looks broken.
Need help

Need help automating Wistia with Make?

A person reads every message.

FAQ

Wistia and Make: common questions

01Is the Wistia Make integration free?
Yes, on the Make side. Wistia is a standard app, available from the Free plan. That plan allows 2 active scenarios, runs scheduled scenarios at most every 15 minutes, caps a run at 5 minutes and files at 5 MB, with 512 MB of transfer. Paid plans (Core, Pro, Teams, Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and count usage in credits per month. You still need an active Wistia account, which follows its own pricing.
02What does it take to connect Wistia to Make?
An active Wistia account and an API token with the right permissions. You create the token from the API tab of the Account Settings page in Wistia, copy it when it appears, then paste it into Make after clicking Create a connection on any Wistia module. The connection name is optional. From then on, all 16 Wistia modules reuse that same connection, so there is nothing to set up again when you add a second module.
03Do Wistia triggers in Make react in real time?
No. All three Wistia triggers, Watch New Projects, Watch New Videos and Watch New Visitors, are scheduled. Make checks Wistia on the scenario's schedule and collects what changed since the last check. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan; paid plans go down to 1 minute. If you need an instant reaction, this app offers no instant trigger in Make.
04What if a Wistia module is missing in Make?
Use Make an API Call. It sends any request to the Wistia API with the connection you already created, so you can reach endpoints the other modules skip without a new login. You write the path and method yourself, so keep the Wistia API reference open. The Make documentation for Wistia lists no specific quota or limit, only a note that its content is AI-generated from Wistia's documentation and should be checked against it.
05Make or n8n for Wistia: which one fits?
It depends on the tool your team already runs. On Make, Wistia comes with 16 modules, including 3 scheduled triggers, and the remaining gaps are covered by Make an API Call. Many apps also have an n8n node, so check whether the Wistia actions you need exist there before choosing. Neither tool is ranked here; the n8n vs Make comparison on this site lays out the criteria to weigh side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations