Resources · Make integration

Vidalytics Make integrationAutomate Vidalytics with Make.

What happens after a viewer fills your Play Gate or watches your video to the key moment? The Vidalytics Make integration gives you 2 triggers and 1 API call module. This guide shows marketers how to connect the account and build a first working scenario.

Try the Vidalytics integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Vidalytics Make integration automate?

The Vidalytics Make integration links your video account to Make so viewer activity can start an automation without code. In Make, that automation is called a scenario: a chain of modules, where each module is one brick, such as a trigger that watches Vidalytics or an action that does something with what it found.

Turn Play Gate forms into follow-up. Watch Play Gate Submission picks up the details a viewer typed into the gate before playing your video. Each submission becomes a bundle, one item passed from module to module, which you can send on to the tool where your sales team works.

React to real viewing, not just clicks. Watch Video Watched fires when a viewer reaches a point in the video you defined in Vidalytics. For a webinar replay or a sales video, that moment is a better signal than a page visit, and the scenario can act on it.

Reach what the listed modules skip. Make an API Call lets you call any endpoint of the Vidalytics API with the same connection, so you are not stuck with only 3 modules.

Two limits to know. Both triggers are scheduled, so Make checks Vidalytics on the scenario's schedule instead of hearing from it the second something happens. And Make itself says its Vidalytics documentation is limited, because little public information exists about the app. If you are weighing tools, Vidalytics often has an n8n node too, and the n8n vs Make comparison lays out the differences. New to the editor? The Make training starts from zero, and Make troubleshooting helps when a run fails.

Connect

How do you connect Vidalytics to Make?

  1. 01

    Add a Vidalytics module

    In your scenario, add any Vidalytics module, for example Watch Play Gate Submission. The field for the account is empty at first. Click Create a connection to open the window that links your Vidalytics account to Make.

  2. 02

    Name it and authorize

    Give the connection a name you will recognize later, which is optional but handy with several accounts. Then either approve Make on the Vidalytics page that opens, or paste the key Vidalytics gives you, depending on what the window asks for.

  3. 03

    Save and reuse

    Click Save. The connection now appears in the module, and every other Vidalytics module in any scenario can reuse it. You only link the account once, then pick it from the list.

First scenario

Build your first Vidalytics scenario

GoalWhen a viewer submits your Play Gate form in Vidalytics, Make picks up the submission and sends it to the Vidalytics API endpoint you choose.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + in the middle of the canvas to place the first module.

  2. 02

    Add the Play Gate trigger

    Search for Vidalytics, pick Watch Play Gate Submission and select your connection. Once it is linked, Make lists what it can read from your account, so you fill the fields by choosing.

  3. 03

    Add the API call

    Click the + on the right of the trigger and add Make an API Call. Point it at the endpoint you need and map values from the submission into the request.

  4. 04

    Test with Run once

    Submit your own Play Gate form, then click Run once. Open the bubble above each module to read the bundles it received and check the request went out as planned.

  5. 05

    Schedule and switch on

    Click the clock on the first module. A new scenario checks every 15 minutes by default, the shortest gap on the Free plan. Keep it or change it, then turn the scenario on.

Triggers

What starts a Vidalytics scenario

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

Vidalytics1Watch Play Gate Submission

Watch Play Gate Submission

Scheduled trigger

In Make“Triggers when user submits information through Play Gate.”

Every time a viewer fills the Play Gate on one of your videos, this trigger hands their answers to your scenario so you can act on them outside Vidalytics. Each submission arrives as its own bundle, ready to be mapped into the next module.

How it fires
scheduled. Make checks the app on the scenario's schedule, so a new submission is picked up at the next check rather than the moment it is sent.
When to use it
you gate a demo or training video and want every viewer who signs up passed along to the team that follows up.
Watch out
the doc lists no fields for this trigger, so run the scenario once with a test submission and look at the bundle before you map anything.
Vidalytics2Watch Video Watched

Watch Video Watched

Scheduled trigger

In Make“Triggers when user reaches some predefined time in the video.”

This one tells your scenario that a viewer has actually reached a chosen point in a video, which says far more about interest than an open or a click. You get a bundle per viewer who crossed that point.

How it fires
scheduled. Make checks the app on the scenario's schedule and collects the viewers who reached the point since the last check.
When to use it
a sales video where getting past the offer section should trigger a different follow-up than dropping off early.
Watch out
the point in the video is predefined, so set it up in Vidalytics first; Make only reports viewers who reach it.
Modules

What Make can do in Vidalytics

Vidalytics gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

Vidalytics1

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

With this module you can reach any part of the Vidalytics API that the two triggers leave out, using the connection you already created. It is your way past a short module list.

When to use it
you need something from Vidalytics that no listed module offers and the API exposes it.
Watch out
Make's own Vidalytics documentation is limited, so test each call with Run once and read the response bundle before you build around it.
Need help

Need help automating Vidalytics with Make?

A person reads every message.

FAQ

Vidalytics and Make: common questions

01Is the Vidalytics Make integration free?
Yes, Vidalytics is a standard app in Make, so it works on the Free plan. That plan gives you 2 active scenarios, a shortest gap of 15 minutes between scheduled runs, up to 5 minutes per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the gap to 1 minute, remove the cap on active scenarios and allow runs of up to 40 minutes. Make counts usage in operations, one module running on one bundle, each month. Your Vidalytics subscription is a separate matter.
02What do you need to connect Vidalytics to Make?
A Vidalytics account and a Make account. The Make doc lists no prerequisites for this app and no app-specific steps, so the standard flow applies. Add a Vidalytics module, click Create a connection, give it a name if you like, then either approve Make on the Vidalytics page or paste the key Vidalytics provides, and click Save. After that, the connection is stored in Make and every Vidalytics module can pick it from a list, in this scenario or any other you build later.
03Do the Vidalytics triggers in Make fire instantly?
No. Both Watch Play Gate Submission and Watch Video Watched are scheduled triggers, shown with a clock badge in the editor. Make checks Vidalytics on the scenario's schedule and picks up everything that happened since the last check. A new scenario runs every 15 minutes by default, which is also the shortest gap on the Free plan; paid plans go down to 1 minute. For a follow-up that needs to leave faster, a paid plan with a tighter schedule is the lever to pull, since Vidalytics has no instant trigger in Make.
04What if the Vidalytics module you need is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the Vidalytics API with the connection you already set up, so anything the API exposes can be reached from a scenario even without a dedicated module. Be aware that Make describes its Vidalytics documentation as limited because little public information exists about the app, so you will need the endpoint name and parameters from Vidalytics itself. Test each call with Run once and read the response bundle before you connect further modules to it.
05Make or n8n for Vidalytics?
It depends on the tool you already use. Vidalytics often has an n8n node as well, so the choice rarely comes down to whether the app is supported. In Make you get 2 scheduled triggers, one for Play Gate submissions and one for watched videos, plus Make an API Call for everything else, all set up from a visual editor. If your other automations already run in one of the two tools, keeping Vidalytics there saves you from maintaining connections in two places. Compare both on the scenarios you actually plan to build.
Same platform

Other docs you might need on this stack.

Browse all integrations