Resources · Make integration

Vxt Make integrationAutomate Vxt with Make.

Can Make update your Vxt voicemail for you? The Vxt Make integration gives you 2 action modules and no trigger, so another app or a schedule starts the work. This guide covers the connection, a first scenario and what each module is for.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Vxt Make integration do for you?

The Vxt Make integration links your Vxt account to Make, a no-code tool where you build a scenario: a chain of steps that runs on its own. Vxt brings two action modules to that chain, one named for your voicemail greeting and one named for incoming voicemail. Something else has to start the scenario, because Vxt has no trigger in Make.

A greeting that follows your team's status. Picture a small agency whose office closes for a holiday. When someone marks the closure in a tool the team already uses, the scenario can run Change Your Voicemail Greeting so callers are not left guessing. The event lives in the other app; Vxt only receives the change.

Voicemail details sent where the team works. Incoming Voicemail is listed as an action, with no official description. Test it with Run once first: if it hands back voicemail data, you can pass that on to a helpdesk or a spreadsheet in the next module.

Both modules in one flow. Once you know what each returns, a single scenario can reset the greeting and then deal with the voicemail side, all from one starting event.

Be clear about the limits. The Make documentation says it cannot yet describe Vxt in full because too little public information exists, so field names and behaviour are for you to check inside the editor. The Make troubleshooting guide helps when a test run fails, and the Make review covers the tool itself. Many apps also have an n8n node; n8n vs Make lays out the criteria for picking one.

Connect

How do you connect Vxt to Make?

  1. 01

    Add a Vxt module

    In a scenario, click the +, search for Vxt and pick one of its two modules. Then click Create a connection. A connection is your Vxt account linked to Make once, then reused by every Vxt module you add later.

  2. 02

    Name it and authorize

    Give the connection a name if you like, which helps when several accounts sit side by side. Then either approve Make on the Vxt page that opens, or paste the key Vxt gives you, depending on what the window asks for.

  3. 03

    Save and check

    Click Save. Make returns to the module, and the fields it can fill from your account start to appear. If the module stays empty, the connection did not go through; open it again and repeat the authorization.

First scenario

Your first scenario with Vxt

GoalWhen something happens in another app you use, Make changes your Vxt voicemail greeting.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Since Vxt has no trigger, the first module belongs to the app where the event happens.

  2. 02

    Set the starting module

    Pick the module of that other app, connect its account and fill its fields. Make lists what it can read, such as calendars or sheets, once the connection works.

  3. 03

    Add the Vxt action

    Click the + on the right, search for Vxt and choose Change Your Voicemail Greeting. Create the connection, then map data from the first module into the fields Make shows.

  4. 04

    Test with Run once

    Click Run once. Each module shows the bundles it received, a bundle being one item passed along. Check that the greeting really changed in Vxt before going further.

  5. 05

    Schedule and switch on

    On the first module, set the schedule, which is every 15 minutes by default on a new scenario, then switch the scenario on. Each module run on a bundle counts as one operation on your plan.

Modules

What the Vxt modules do

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

Vxt1

Change Your Voicemail Greeting

ActionIn the docs only

With this action, a scenario can swap the greeting callers hear on your Vxt voicemail, without you opening Vxt. Its name describes the job; Make gives no official description, so read the fields once connected.

When to use it
an event elsewhere should change what callers hear, such as a closure logged in a shared calendar.
Watch out
test with Run once and listen to the result before you switch the scenario on.
Vxt2

Incoming Voicemail

ActionIn the docs only

What you get here is not yet documented: Make lists Incoming Voicemail as an action and offers no description. Add it, connect Vxt, and click Run once to see which bundle it returns.

When to use it
after a test shows voicemail data you want to pass to a helpdesk, a CRM or a sheet.
Watch out
the name sounds like a trigger, but it is not one, so another module or a schedule must start the scenario.
Need help

Need help automating Vxt with Make?

A person reads every message.

FAQ

Questions about Vxt and Make

01Is the Vxt Make integration free?
Yes. Vxt is a standard app in Make, so it is available from the Free plan onward. That plan has limits worth knowing: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute and lift the cap on active scenarios. Make counts usage in operations, one per module run on one item, so a two-step Vxt scenario uses two operations each time it handles something.
02What do you need to connect Vxt to Make?
A Vxt account and a Make account are enough to start, as the Make docs list no other prerequisite. You add a Vxt module, click Create a connection, give it a name if you want, then approve Make on the Vxt page or paste the key Vxt provides, and click Save. The docs for Vxt are flagged as limited and give no app-specific steps, so the generic Make flow applies. Test right away with Run once to confirm the account really answers.
03Can a Vxt scenario start in real time?
Not from Vxt itself, because Vxt has no trigger in Make: both modules are actions. You still have two ways to start. The first module can belong to another app, and if that app offers an instant trigger it calls Make through a webhook as soon as its event happens. Otherwise the scenario runs on its schedule, every 15 minutes by default, or less often if you set it that way. On the Free plan, 15 minutes is also the shortest interval allowed.
04What if a Vxt module is missing or does not do enough?
It depends on the need, but Vxt offers no Make an API Call module, so you cannot reach extra Vxt features through a raw request inside Make. The docs also warn that Vxt is only partly documented, which means some behaviour stays unclear until you test it. If the two modules do not cover your case, look at whether another app in your stack can hold that step, or ask the team for help on the setup.
05Should you use Make or n8n for Vxt?
It depends on your criteria rather than on a winner. On Make, Vxt gives you 2 action modules, works from the Free plan and connects with the generic flow, which suits someone who wants a visual editor and a guided start. Many apps also have an n8n node, but this page does not confirm one for Vxt, so check that first. Compare the modules each tool offers for your exact task, and which editor you and your team already know.