Resources · Make integration

VivoMeetings Make integrationAutomate VivoMeetings with Make.

Can Make handle your VivoMeetings calls without anyone copying links by hand? The VivoMeetings Make integration gives you 6 modules: 1 trigger and 5 actions. This guide is for teams who run their calls on VivoMeetings, and it walks you from the connection to a first working scenario.

Try the VivoMeetings integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the VivoMeetings Make integration do?

The VivoMeetings Make integration links your VivoMeetings account to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules that runs on a schedule or when an app calls Make. Each module is one brick of that chain, so you can spot new meetings, create calls and pass their links along without writing code.

Links that travel on their own. Watch New Meeting spots each meeting added to your account, and Get a Conference URL fetches the address people need to join. From there, the link can move to the next module of another app your team already reads.

Calls booked from somewhere else. Put Create a Meeting or Create a Reservationless Conference after a step from another app, and the call exists in VivoMeetings without anyone opening it. When plans change, Update a Conference edits the call you already have.

A way around the missing pieces. Make an API Call reaches any endpoint of the VivoMeetings API with the same connection, which helps when the five ready-made actions stop short.

Know one limit before you start: Make itself says its VivoMeetings documentation is incomplete, because little public information exists about the app. Expect to test each module with Run once rather than trust a written field list. The Make review gives the wider picture, Make troubleshooting helps when a run fails, and n8n vs Make covers the other tool.

Connect

How do you connect VivoMeetings to Make?

  1. 01

    Open the connection window

    Add any VivoMeetings module to your scenario and click Create a connection. A connection is your VivoMeetings account linked to Make once, then reused by every VivoMeetings module you add later.

  2. 02

    Name it and authorize

    Give the connection a name if you like, handy when several accounts sit side by side. Then authorize Make on the VivoMeetings page that opens, or paste the key VivoMeetings gives you, depending on what the window asks for.

  3. 03

    Save and check

    Click Save. The connection now shows in the module, and Make can list what it reads from your account. If nothing appears, open the connection again before going further.

First scenario

Your first scenario with VivoMeetings

GoalWhen a new meeting appears in VivoMeetings, Make fetches its conference URL so the join link is ready for the next step.

  1. 01

    Create the scenario

    Go to the Scenarios page, create a new scenario and click the big + to add the first module. The canvas stays empty until then.

  2. 02

    Add the trigger

    Search for VivoMeetings, pick Watch New Meeting and click Create a connection to link your account. This module starts the scenario each time it finds a new meeting.

  3. 03

    Add the conference link

    Click the + on the right of the trigger and choose Get a Conference URL. Map the meeting data coming from the trigger into it, using what Make offers in the fields.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received; a bundle is one item passed along, here one meeting. Read them to confirm the link came back.

  5. 05

    Schedule and switch on

    Open the clock on the first module to set the schedule, every 15 minutes by default on a new scenario, then switch the scenario on. You can add a module of another app after the URL step later.

Triggers

What starts a VivoMeetings scenario

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

VivoMeetings1Watch New Meeting

Watch New Meeting

triggerIn the docs only

Your scenario learns about every meeting added to your VivoMeetings account, and each one arrives as a bundle the next modules can use. Nobody has to report a new call anymore.

How it fires
scheduled, Make checks the app on the scenario's schedule, every 15 minutes by default and never faster than that on the Free plan. The scheduled type comes from the module's name, since the documentation does not describe it.
When to use it
when a new meeting should set something off, such as fetching its link or alerting the people invited.
Watch out
run it once before switching the scenario on and read what it returns, because no official field list exists for this trigger.
Modules

What the VivoMeetings modules do

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

VivoMeetings1

Create a Meeting

ActionIn the docs only

A meeting shows up in VivoMeetings without anyone opening the app, built from data that came from an earlier step of your scenario.

When to use it
after a booking or a signed quote lands in another tool, so the call is created at the same moment.
Watch out
the documentation lists no fields, so fill the module with Make's suggestions and check the result with Run once.
VivoMeetings2

Create a Reservationless Conference

ActionIn the docs only

You get a conference in VivoMeetings that does not rely on a booked slot, the kind people can join when they need it.

When to use it
when a new project or client file needs its own standing call room rather than a single dated meeting.
Watch out
pick this one over Create a Meeting only if the reservationless format fits how your team works.
VivoMeetings3

Get a Conference URL

ActionIn the docs only

The join address of a conference comes back into your scenario, ready to paste into a message, an email or a record in another app.

When to use it
right after Watch New Meeting or a create module, when the invited people need the link without asking for it.
Watch out
it only reads a link; place the module that sends it after this one.
VivoMeetings4

Make an API Call

ActionIn the docs only

Any endpoint of the VivoMeetings API becomes reachable from your scenario, using the connection you already set up, so no second login is needed.

When to use it
when the five ready-made modules stop short of what you need, such as an action none of them offers.
Watch out
this module expects you to know the VivoMeetings API, and Make's documentation for the app is incomplete.
VivoMeetings5

Update a Conference

ActionIn the docs only

A conference you already have in VivoMeetings gets changed from your scenario, so a new detail in another tool is carried over without a manual edit.

When to use it
when a project or event changes after its call room was created and the conference should follow.
Watch out
the module changes an existing conference, so map the right one and test on a sample with Run once.
Need help

Need help automating VivoMeetings with Make?

A person reads every message.

FAQ

VivoMeetings and Make: common questions

01Is the VivoMeetings Make integration free?
Yes, on the Make side. VivoMeetings is a standard app, so its modules work from the Free plan onward. That plan comes with limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios. Every run uses operations, one per module per bundle, and those count against your plan. Your VivoMeetings subscription is a separate matter.
02What do you need to connect VivoMeetings to Make?
You need two accounts: one on VivoMeetings and one on Make. Make's documentation for this app lists no prerequisites and no official connection steps. You follow the generic flow: add a VivoMeetings module, click Create a connection, name it if you want, authorize Make on the VivoMeetings page or paste the key the app provides, then click Save. The connection is then reused by all six modules, so you only do this once per account.
03Does the VivoMeetings trigger in Make react in real time?
No. Watch New Meeting is a scheduled trigger, going by its name, since the documentation does not describe its type. Make checks VivoMeetings on the scenario's schedule, every 15 minutes by default. On the Free plan, 15 minutes is also the shortest interval you can set; paid plans go down to 1 minute. So a new meeting reaches your scenario at the next check, not the second it is created. If you need a faster reaction, a shorter interval on a paid plan is the way to get there.
04What if a VivoMeetings module is missing in Make?
Use Make an API Call. It reaches any endpoint of the VivoMeetings API with the same connection as the other modules, so the five ready-made actions are not a hard ceiling. The catch is documentation: Make says it cannot document VivoMeetings fully because little public information exists about the app. Plan to check with VivoMeetings which calls its API accepts, and test each call with Run once before switching the scenario on. If the API does not offer what you need either, the gap sits on the VivoMeetings side.
05Should you use Make or n8n for VivoMeetings?
It depends on your criteria, and both can be fair picks. On Make, VivoMeetings offers 6 modules, a scheduled trigger and a Make an API Call module for the rest, available from the Free plan. The same app often has an n8n node as well, so check it exists there before deciding. Compare the modules each tool offers for your exact case, the plan you already pay for, and where your team already builds its automations. Pick the tool that covers your scenario end to end.
Same platform

Other docs you might need on this stack.

Browse all integrations