Resources · Make integration

Vyte Make integrationAutomate Vyte with Make.

Can your meeting bookings update themselves across your other tools? The Vyte Make integration gives you 6 modules: one instant trigger, four actions and one search. This guide is for teams that book meetings with Vyte, and it walks you from the API key to a working first scenario.

Try the Vyte integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Vyte Make integration do for you?

The Vyte Make integration links your Vyte organization to Make so your events move without copy and paste. You build a scenario, the automation you assemble in Make, out of modules: each module is one brick, such as a trigger that starts the flow or an action that changes something in Vyte.

A CRM that knows about every booking. Watch Events starts your scenario the moment Vyte reports a new event action, and the next module can write the meeting into your CRM or a shared sheet. Your sales team stops asking who booked what.

Cancellations that follow the client. When a deal is lost in another tool, Search Events finds the matching Vyte event and Cancel an Event closes it, so nobody shows up to a meeting that no longer has a reason to exist.

Meetings created from a request. A form answer or a new lead can feed Create an Event, then Confirm an Event once the slot is agreed. The booking starts where the request arrives.

The listed modules only cover events. For anything else the Vyte API offers, Make an API Call reuses the same connection. The Vyte documentation in Make also warns that its content is AI-generated from the vendor docs, so check important details with Vyte. If you are weighing tools, read n8n vs Make; to go further on the editor itself, see Make training or Make pricing.

Connect

How do you connect your Vyte account to Make?

  1. 01

    Get your API key in Vyte

    Log in to Vyte and make sure you have an organization, since the key lives there. Open your organization settings, go to the API key tab and copy the key shown. Keep it at hand for the next step.

  2. 02

    Add a Vyte module and open the connection

    In your Make scenario, add any Vyte module and click Create a connection. A connection is your Vyte account linked to Make once, then reused by every Vyte module. You can type a label in Connection name if you plan to link several organizations.

  3. 03

    Paste the key and save

    Paste the API key you copied from Vyte and confirm. Make now lists what it can read from your organization when you fill in the module fields, so you pick from real data instead of typing identifiers by hand.

First scenario

Your first scenario: cancel a Vyte meeting when a deal falls through

GoalWhen a deal is marked lost in another app, Make finds the matching Vyte event and cancels it.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the module of the app where lost deals are recorded, such as your CRM, and connect that account.

  2. 02

    Add Search Events

    Click the + on the right of the first module, search for Vyte and choose Search Events. Map a detail from the deal, such as the client name, so Make looks for the right meeting.

  3. 03

    Add Cancel an Event

    Add Cancel an Event after the search and map the event it returned. Each event found is a bundle, one item passed from module to module, and each one gets its own cancellation.

  4. 04

    Test with Run once

    Click Run once on a test deal linked to a test meeting. Open the bubbles above each module to read the bundles it received and check that only the expected event was cancelled.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each module run on a bundle is an operation, the unit Make counts on your plan.

Triggers

What starts a Vyte scenario

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

Vyte1Watch Events

Watch Events

Instant trigger

In Make“Triggers when a new event action.”

Watch Events hands your scenario each new event action from Vyte, so the rest of your tools learn about a booking without anyone retyping it. It is the only trigger of the app, which makes it the natural starting point for anything that should react to a meeting.

How it fires
instant, Vyte calls Make through a webhook as soon as the event action happens; the module carries the lightning badge.
When to use it
a new meeting should appear in your CRM, a team channel or a booking log.
Watch out
the documentation does not list which event actions are sent, so run a real booking through Run once and read the bundle before mapping fields.
Modules

Everything the Vyte modules can do

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

Vyte1

Cancel an Event

Action

In Make“Cancels an Event.”

Cancel an Event calls off a meeting in Vyte from your scenario, which keeps a calendar clean when the reason for the meeting disappears somewhere else. It acts on one event at a time.

When to use it
a deal is lost or a client asks to stop, and the booked slot should go.
Watch out
place a Search Events or a filter before it and test on a dummy meeting, since a wrong mapping cancels the wrong client.
Vyte2

Confirm an Event

Action

In Make“Confirms an Event.”

Confirm an Event marks a Vyte event as confirmed without you having to open Vyte. Picture a request that has been approved elsewhere: this module turns that approval into a confirmed meeting.

When to use it
right after Watch Events or Create an Event, once your own rule says the slot is fine.
Watch out
the documentation does not describe what Vyte sends to invitees on confirmation, so check it on a test event.
Vyte3

Create an Event

Action

In Make“Creates an Event.”

Create an Event opens a new event in Vyte from data that arrives in another app, so a meeting exists the moment the request comes in. A demo form, a signed quote or a new lead can all be the starting point.

When to use it
the request lands outside Vyte and you want the booking to start without manual entry.
Watch out
if Watch Events runs in another scenario, this new event starts that one too, so keep the two flows from feeding each other.
Vyte4

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call reaches any endpoint of the Vyte API with the connection you already have, which covers what the five other modules leave out. You write the request yourself, so it suits someone comfortable reading API documentation.

When to use it
you need a Vyte feature that goes beyond events, and no listed module offers it.
Watch out
check the endpoint in the Vyte API documentation first, since Make does not guide the fields for you here.
Vyte5

Search Events

Search

In Make“Returns events by searched criteria.”

Search Events looks through your Vyte events with the criteria you set and returns what matches, so a later module can act on the right meeting. It is the bridge between a name or date from another tool and an event in Vyte.

When to use it
before a cancel or confirm, when you only know who the meeting is with.
Watch out
it can return zero, one or several bundles, and every following module then runs once per bundle.
Need help

Need help automating Vyte with Make?

A person reads every message.

FAQ

Vyte and Make: frequent questions

01Is the Vyte Make integration free?
Yes, Vyte is a standard app in Make, so you can use it on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and allow unlimited active scenarios. Make counts usage in operations, one module running on one bundle. Your Vyte subscription is separate and not covered here.
02What do you need to connect Vyte to Make?
You need a Vyte account with an organization, because the API key is tied to it. Log in to Vyte, create the organization if it does not exist yet, open its settings and copy the key from the API key tab. In Make, add a Vyte module, click Create a connection, give it a name if you like and paste the key. For the Watch Events trigger, Make first asks you to create a webhook, then the connection.
03Does the Vyte trigger in Make fire instantly?
Yes. Watch Events is an instant trigger: Vyte calls Make through a webhook as soon as a new event action happens, instead of Make checking on a schedule. You see a lightning badge on the module in the editor. Scenarios that start with another app, such as a CRM, follow that app's trigger instead, and a scheduled one runs every 15 minutes by default. On the Free plan the scheduled minimum is 15 minutes.
04What if a Vyte module you need is missing in Make?
Use Make an API Call. It sends any request to the Vyte API with the connection you already set up, so you are not limited to the five listed modules that handle events. You write the endpoint and the body yourself, based on the Vyte API documentation. Keep in mind that the Vyte help page in Make states it was generated with AI from vendor docs, so confirm details with Vyte when something does not behave as expected.
05Should you use Make or n8n for Vyte?
It depends on what you need to automate and which tool your team already uses. In Make, Vyte comes with 6 modules: an instant trigger for events, actions to create, confirm and cancel events, a search, and Make an API Call for everything else. Many apps also have an n8n node, so check whether one exists for Vyte before choosing. The deciding question is which modules cover your flow, not which platform is better in general.
Same platform

Other docs you might need on this stack.

Browse all integrations