Resources · Make integration

VdoCipher Make integrationAutomate VdoCipher with Make.

What if new videos reached VdoCipher without anyone uploading them by hand? The VdoCipher Make integration gives you 5 modules: 1 instant trigger and 4 actions. It suits course creators and video teams, and this page walks you from the connection to a working first scenario.

Try the VdoCipher integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the VdoCipher Make integration do for you?

The VdoCipher Make integration links your VdoCipher account to Make, a tool where you build a scenario (an automation made of connected steps) without writing code. Each step is a module: one trigger that starts the scenario, or one action that does something in VdoCipher, such as adding a video or creating a playback code.

Videos that arrive on their own. A file link collected in another app goes to Import Video from URL, which pulls the video into VdoCipher from any HTTP or FTP address. If you already hold the file inside Make, Upload Video sends it straight to your account.

A team kept in the loop. Watch Video Status fires when a video changes status, so the next module can alert the right people or update a tracking sheet in another app, with no refreshing of the dashboard.

Playback codes on demand. Generate an OTP creates the one-time password VdoCipher uses for video playback, ready to pass to the next module of your scenario.

The listed modules stop there. For anything else in the VdoCipher API, Make an API Call reuses your connection. The same app often exists as an n8n node too; the n8n vs Make comparison lays out the two tools side by side, and the Make review or the Make training help you get started.

Connect

How do you connect VdoCipher to Make?

  1. 01

    Generate your API key

    In your VdoCipher dashboard, open the Security and Config section, click Generate API Key, then use the copy option to grab the key. You need an active VdoCipher account for this step.

  2. 02

    Open the connection window

    In your Make scenario, add any VdoCipher module and click Create a connection. The Connection name field is optional; a clear name helps when you later run several accounts side by side.

  3. 03

    Paste the key and save

    Enter the API key you copied, or follow the instructions Make shows on screen, and confirm. That connection (your VdoCipher account linked to Make once) is then reused by every VdoCipher module you add.

First scenario

Build your first scenario with VdoCipher

GoalWhen another app hands Make a video link, Make imports that video into VdoCipher.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. The first module comes from the app that holds your video links, such as a form or a storage tool.

  2. 02

    Set up the source module

    Pick the module of that other app, click Create a connection to link its account, then fill its fields. Make lists what it can read once the connection exists.

  3. 03

    Add Import Video from URL

    Click the + on the right, search VdoCipher, choose Import Video from URL and connect it with your API key. Then map the link from the first module into its fields.

  4. 04

    Test with Run once

    Click Run once. Each module shows the bundles it received (a bundle is one item passed along, here one video link). Check in VdoCipher that the video landed.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. From now on, each new link becomes a video in your account.

Triggers

What starts a VdoCipher scenario?

1 module starts a scenario when something happens in VdoCipher. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by VdoCipher as soon as it happens.

VdoCipher1Watch Video Status

Watch Video Status

Instant trigger

In Make“Triggers by video status change events.”

Watch Video Status starts your scenario whenever a video in your VdoCipher account changes status, so the rest of the flow runs at the right moment instead of when someone remembers to check.

How it fires
instant: VdoCipher calls Make through a webhook as soon as the change happens, so there is no polling interval to set.
When to use it
after an import or upload, to warn your team or update a list in another app once the video status moves.
Watch out
the Make documentation asks for the webhook first, then the connection; keep that order when you set it up.
Modules

What can VdoCipher do in Make?

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

VdoCipher1

Generate an OTP

Action

In Make“Generates an OTP for video playback.”

This action hands you a one-time password that VdoCipher uses for video playback, created inside your scenario rather than by hand each time a viewer needs access.

When to use it
when a sign-up or purchase in another app should give that person a playback code right away.
Watch out
test it with Run once and read the output bundle before mapping it downstream.
VdoCipher2

Import Video from URL

Action

In Make“Imports a video from any HTTP/FTP URL.”

You get a video in VdoCipher from nothing more than a link: the module pulls the file from any HTTP or FTP address, so nobody downloads and re-uploads it.

When to use it
the file already sits online, for example a link sent through a form or shared from storage.
Watch out
the link must point to the file itself; if you hold the file in Make instead, pick Upload Video.
VdoCipher3

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Here you reach any endpoint of the VdoCipher API that the other modules leave out, while keeping the same connection and the same API key.

When to use it
a need the four named modules do not cover, once you have found the matching endpoint in the VdoCipher documentation.
Watch out
you build the request yourself, so a wrong path or body fails; run it once before activating.
VdoCipher4

Upload Video

Action

In Make“Uploads a video to your VdoCipher account.”

Upload Video puts a file your scenario already carries straight into your VdoCipher account, which saves the manual trip through the dashboard.

When to use it
an earlier module downloaded the video from another app and passes the file itself, not a link.
Watch out
on the Make Free plan, files are capped at 5 MB, so check the size of your videos against your plan before you activate.
Need help

Need help automating VdoCipher with Make?

A person reads every message.

FAQ

VdoCipher and Make: frequent questions

01Is the VdoCipher Make integration free?
Yes, on the Make side. VdoCipher is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) drop the interval to 1 minute and remove the cap on active scenarios. Make counts usage in operations, one execution of one module on one bundle. Your VdoCipher subscription is separate and follows VdoCipher's own pricing.
02What do you need to connect VdoCipher to Make?
An active VdoCipher account and an API key. You generate the key in the Security and Config section of your VdoCipher dashboard with the Generate API Key button, then copy it. In Make, add a VdoCipher module, click Create a connection, give it a name if you want, and paste the key. If the first module is the instant trigger Watch Video Status, click Create a webhook first, then Create a connection. The same connection then serves every VdoCipher module.
03Does the VdoCipher trigger react in real time?
Yes. Watch Video Status is an instant trigger: VdoCipher calls Make through a webhook as soon as a video changes status, and the scenario starts right away. Scenarios that begin with a scheduled module from another app behave differently: Make checks on the scenario schedule, every 15 minutes by default, and no less than 15 minutes apart on the Free plan. So a flow that imports videos from links waits for its schedule, while one that follows video status reacts immediately.
04What if a VdoCipher module is missing in Make?
Use Make an API Call. It reaches any endpoint of the VdoCipher API with your existing connection, so an operation the four named modules do not offer can still happen inside the scenario. You write the request yourself from the VdoCipher documentation, then test it with Run once. The Make documentation page for this app also warns that its content is AI-generated from VdoCipher sources and may contain mistakes, so for anything critical, check with VdoCipher directly.
05Should you use Make or n8n for VdoCipher?
It depends on the tool your team already works in. On Make, VdoCipher offers 5 modules, including an instant trigger for video status and a Make an API Call module for the rest of the API. The same app often has an n8n node as well. Compare what each side offers for the exact actions you need, such as imports, uploads and playback codes, and pick the platform where your other scenarios or workflows already run.
Same platform

Other docs you might need on this stack.

Browse all integrations