Resources · Make integration

Vapi Make integrationAutomate Vapi with Make.

What if your Vapi assistant could ask your other tools for an answer while the caller is still on the line? The Vapi Make integration gives you 36 modules, including 2 instant triggers. This guide connects your account and walks you through a first scenario, step by step.

Try the Vapi integration on MakeSee the 36 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Vapi Make integration do for you?

The Vapi Make integration links your Vapi account to Make so your voice assistants can work with the rest of your stack. You build a scenario, the automation you assemble in Make, out of modules: each module is one brick, such as a trigger that listens to Vapi or an action that creates a call, an assistant or a file.

Answer questions mid-call. Watch Tool Call Request receives the moment your assistant asks for a tool, Make looks up the answer in another app, and Respond to a Tool Call hands the result back so the conversation keeps going. Think of an order status for a shop, or a free slot for a repair service.

File every call once it ends. Watch End of Call Report delivers the report of each finished call. From there, a scenario can write it to a base like the one described in our Airtable Make integration guide, so sales reps read a recap instead of replaying a recording.

Place calls from your other tools. Create an Outbound Phone Call dials out through a Twilio or Vonage number added in your Vapi dashboard. A new lead in a form or a CRM can start that call without anyone picking up a phone.

A few limits are worth knowing. The five modules of the Workflow group are marked as deprecated, so new builds should skip them. The Squads group has no delete module and Phone Numbers only has a list module; Make an API Call covers those gaps with the same connection. If you are weighing Make against n8n for Vapi, the n8n vs Make comparison lays out the criteria, and the Make training takes you further on the editor itself.

Connect

How do you connect your Vapi account to Make?

  1. 01

    Copy your private key in Vapi

    Log in to Vapi and open Build > Vapi API Keys in the left sidebar. Copy the Private Key value and keep it somewhere safe. No key yet? Click Add Key and Vapi creates one for you.

  2. 02

    Create the connection in Make

    A connection is your Vapi account linked to Make once, then reused by every Vapi module. Add any Vapi module to your scenario and click Create a connection. You can give it a label in Connection name, handy when you manage several accounts.

  3. 03

    Paste the key and save

    Paste the private key into the API Key field and click Save. If Make asks you to authenticate or confirm access, accept it. The connection now appears in the module, and every other Vapi module can pick it from the same list.

First scenario

Your first scenario: answer a Vapi tool call from Make

GoalWhen your Vapi assistant calls a tool during a conversation, Make receives the request and sends the answer back to the call.

  1. 01

    Create a blank scenario

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

  2. 02

    Add Watch Tool Call Request

    Search for Vapi, pick Watch Tool Call Request and select the connection you just made. During this setup the module creates the matching tool definition in your Vapi account for you.

  3. 03

    Add Respond to a Tool Call

    Click the + on the right of the trigger and choose Respond to a Tool Call. Map the data received from the trigger, then fill in the result your assistant should hear.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Then read the bundles each module received: the items that pass from one module to the next.

  5. 05

    Switch the scenario on

    This trigger is instant: Vapi calls Make through a webhook as soon as a tool call happens, so there is no clock to tune. Turn the scenario on and it waits for the next request.

Triggers

What can start a Vapi scenario?

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

Vapi1Watch Tool Call Request

Watch Tool Call Request

Instant trigger

In Make“Listens to function call from Vapi. Creates the Tool definition in Vapi during setup.”

Watch Tool Call Request lets your Vapi assistant hand a question to Make in the middle of a call: the assistant asks for a tool, and the request lands in your scenario as a bundle. During setup, the module also creates the matching tool definition in Vapi, so you have nothing to declare by hand.

How it fires
instant: the app calls Make through a webhook as soon as it happens.
When to use it
the assistant needs an answer held in another app, such as an order status or a free slot, before it can reply to the caller.
Watch out
the caller is waiting on the line, so end the scenario with Respond to a Tool Call, the module that returns the result or the error to Vapi.
Vapi2Watch End of Call Report

Watch End of Call Report

Instant trigger

In Make“Listens to end of call report from Vapi call via this webhook.”

Watch End of Call Report gives you the report of each finished Vapi call, so a scenario can store it, share it or act on it once the conversation is over. Every report arrives as its own bundle, ready to map into the next module.

How it fires
instant: the app calls Make through a webhook as soon as it happens.
When to use it
a sales team wants each call recap in its CRM or spreadsheet without anyone copying notes after the conversation.
Watch out
the doc does not describe what the report contains, so click Run once and read the bundle before you decide which parts to map.
Modules

What can Make do in Vapi?

Vapi gives you 34 modules in 10 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Calls

5 modules
Vapi1

List Calls

SearchIn the docs only

List Calls pulls the calls stored in your Vapi account into the scenario, one bundle per call, so you can review or export them in bulk.

When to use it
you want a spreadsheet of past calls to go through with the team, rather than opening each one in Vapi.
Watch out
as a search, it can return zero, one or many bundles, and each bundle that reaches a later module costs an operation, the unit Make counts on your plan.
Vapi2

Create Call

Action

In Make“Create Call”

Create Call starts a new call in Vapi from your scenario, turning a form entry or a CRM event into a conversation with your assistant.

When to use it
a lead fills in a callback form and Vapi should reach out without a person dialing.
Watch out
the doc gives this module no description beyond its name; when you dial through a Twilio or Vonage number, Create an Outbound Phone Call is the module described for that case.
Vapi3

Get Call

ActionIn the docs only

Get Call fetches a single call you already know about, so later modules can use its details.

When to use it
after Watch End of Call Report or List Calls, when you need the full record of one call before writing it somewhere else.
Watch out
Make files it as an action, not a search, so it handles one call at a time; map the call from the previous module instead of typing it in.
Vapi4

Delete Call Data

ActionIn the docs only

Delete Call Data erases what Vapi keeps about a call, which helps when a caller asks for their data to be removed.

When to use it
a deletion request reaches your support inbox and the same scenario that logs the request should also handle the erase step.
Watch out
the doc says nothing about restoring deleted data, so treat the erase as final and test on a dummy call with Run once before you switch the scenario on.
Vapi5

Update Call

ActionIn the docs only

Update Call changes a call that already exists in Vapi, so the record stays in line with what happened next in your other tools.

When to use it
a deal moves forward in your CRM and the related Vapi call should reflect that progress.
Watch out
the doc does not say which parts of a call you can edit; open the module in Make and check the fields it offers before you plan around it.

Assistants

5 modules
Vapi6

List Assistants

SearchIn the docs only

List Assistants returns every assistant set up in your Vapi account as separate bundles, a quick way to take stock or keep a sync going.

When to use it
an agency running assistants for several clients wants one sheet that names them all.
Watch out
the output can be many bundles; add an aggregator after it, the module that groups bundles back together, if the next step should run only once.
Vapi7

Get Assistant

ActionIn the docs only

Get Assistant reads the setup of one assistant, so a scenario can check it, copy it or document it.

When to use it
right before Update Assistant, to keep a copy of the current version in a shared document.
Watch out
pick the assistant from the previous bundle rather than hardcoding it, or the scenario keeps reading the same one every time.
Vapi8

Create Assistant

ActionIn the docs only

Create Assistant sets up a new Vapi assistant from a scenario, which spares you from rebuilding the same one by hand for every client or brand.

When to use it
a new client signs and the onboarding scenario should prepare their assistant along with the folder and the CRM record.
Watch out
each run adds one more assistant; a trigger that fires twice for the same client leaves you with a duplicate.
Vapi9

Delete Assistant

ActionIn the docs only

Delete Assistant removes an assistant from your Vapi account and keeps the list tidy once a campaign or a client contract ends.

When to use it
a client is marked as lost in your CRM and the assistant built for them should go too.
Watch out
the doc mentions no way to restore it, so treat it as final; run List Assistants first and check that the bundle points to the right assistant.
Vapi10

Update Assistant

ActionIn the docs only

Update Assistant edits an existing assistant, so a change made in your source of truth reaches Vapi without opening its dashboard.

When to use it
opening hours or an offer change in your internal sheet and the assistant should talk about the new version.
Watch out
the doc does not list the settings you can edit; read the module form in Make and test with Run once on a spare assistant.

Phone Numbers

1 module
Vapi11

List Phone Numbebrs

SearchIn the docs only

List Phone Numbebrs returns the phone numbers attached to your Vapi account, one bundle each. The typo is part of the module name in Make, so expect to see it spelled that way.

When to use it
you need to choose which number an outbound call should use, or keep a sheet of numbers per team.
Watch out
it is the only module of the Phone Numbers group, so adding or editing a number goes through Make an API Call.

Tools

4 modules
Vapi12

List Tools

SearchIn the docs only

List Tools collects the tools your Vapi assistants can call, which gives you a fast audit of what is already wired.

When to use it
before creating a tool, to check whether one with the same purpose already exists.
Watch out
Watch Tool Call Request also creates a tool definition in Vapi when you set it up, so the list can include those next to the ones you built yourself.
Vapi13

Create Tool

ActionIn the docs only

Create Tool adds a new tool to Vapi from a scenario, the piece an assistant relies on to ask something of another system.

When to use it
you roll out the same tool across several client accounts and want a scenario to set each one up.
Watch out
for a tool that Make answers itself, Watch Tool Call Request already creates the definition during setup; adding Create Tool on top may leave you with two.
Vapi14

Update Tool

ActionIn the docs only

Update Tool changes a tool that already exists in Vapi, so a decision taken elsewhere reaches your assistants without manual edits.

When to use it
a tool must follow a change in the system it talks to, and your team tracks those changes in a sheet or a ticket.
Watch out
fetch the tool first with Get Tool or List Tools, then map it into this module so the right one changes.
Vapi15

Get Tool

ActionIn the docs only

Get Tool reads a single tool from Vapi, a simple way to see how it is set before a scenario depends on it.

When to use it
in a scenario that documents your setup, one tool per run, into a shared page.
Watch out
Make files it as an action and it handles one tool; to go through all of them, start from List Tools instead.

Workflow (deprecated)

5 modules
Vapi16

Create Workflow (deprecated)

ActionIn the docs only

Create Workflow (deprecated) creates a workflow in Vapi, but the whole Workflow group carries the deprecated label, so treat it as a legacy piece.

When to use it
only to keep an older scenario running while you plan what replaces it.
Watch out
do not start a new build on it; look at Create Assistant or Create Squad first, and keep Make an API Call for what they miss.
Vapi17

Update Workflow (deprecated)

ActionIn the docs only

Update Workflow (deprecated) edits a Vapi workflow that already exists. It still shows up in Make, yet the doc marks it deprecated like the rest of its group.

When to use it
an inherited scenario updates workflows and you cannot rebuild it right away.
Watch out
the label is a warning; write down in the scenario notes which module will take over and plan the switch.
Vapi18

List Workflows (deprecated)

SearchIn the docs only

List Workflows (deprecated) returns the workflows of your Vapi account, mostly useful to see what still depends on this older group.

When to use it
an audit before a migration, to know how many workflows are left to move.
Watch out
as a search it can send many bundles to the next module, and it belongs to a deprecated group, so keep it out of new builds.
Vapi19

Get Workflow (deprecated)

ActionIn the docs only

Get Workflow (deprecated) reads one workflow from Vapi. See it as an archive tool rather than an everyday one, since the doc files it under a deprecated group.

When to use it
to copy the setup of an old workflow into a document before rebuilding it another way.
Watch out
the doc gives no end date for the group, so do not let a live scenario rely on it.
Vapi20

Delete Workflow (deprecated)

ActionIn the docs only

Delete Workflow (deprecated) removes a workflow from Vapi, the last step of a cleanup once its replacement works.

When to use it
the new setup has handled real calls and the old workflow no longer serves any purpose.
Watch out
treat the deletion as final, since the doc mentions no restore, and the module sits in a deprecated group; map the workflow from List Workflows (deprecated) instead of guessing it.

Squads

4 modules
Vapi21

List Squads

SearchIn the docs only

List Squads brings every squad of your Vapi account into the scenario, one bundle per squad.

When to use it
to keep a register of squads next to the assistants they bring together, in a sheet the whole team can read.
Watch out
several bundles mean several runs of the next module; an aggregator merges them when you want a single row.
Vapi22

Get Squad

ActionIn the docs only

Get Squad reads one squad in Vapi and returns its details as a single bundle for the rest of the scenario.

When to use it
a scenario reports on a squad after a call and needs its current setup to do so.
Watch out
pair it with List Squads when you do not know yet which squad to target; Get Squad expects exactly one.
Vapi23

Create Squad

ActionIn the docs only

Create Squad builds a new squad in Vapi from a scenario, so a team of assistants is set up the same way every time.

When to use it
onboarding a client who needs several assistants working together, right after Create Assistant has prepared each of them.
Watch out
each run adds one squad; guard against a trigger that fires twice for the same client.
Vapi24

Update Squad

ActionIn the docs only

Update Squad edits a squad that already exists, useful as soon as the lineup of assistants changes.

When to use it
an assistant is retired with Delete Assistant and the squad it belonged to must be adjusted in the same scenario.
Watch out
the Squads group has no delete module in Make; to remove a squad, turn to Make an API Call.

Webhooks

2 modules
Vapi25

Server Message

ActionIn the docs only

Server Message is one of the two modules of the Webhooks group. The doc gives it no description, and its name hints at the messages Vapi exchanges with a server.

When to use it
you already handle Vapi server messages elsewhere and want Make to take part in that exchange.
Watch out
with no official description, build it in a test scenario, click Run once and read the bundle before using it on live calls.
Vapi26

Client Message

ActionIn the docs only

Client Message sits next to Server Message in the Webhooks group, and its name points to the client side of a Vapi call. The doc says nothing more about it.

When to use it
you are exploring what Make can send around a call and want to compare both message modules.
Watch out
treat it as experimental until a Run once shows what it returns, and keep it away from scenarios your customers depend on.

Files

5 modules
Vapi27

Upload File

ActionIn the docs only

Upload File sends a file from your scenario into Vapi, which keeps what Vapi stores in line with the documents your team edits.

When to use it
a price list or a help document changes in your cloud storage and Vapi should hold the new copy.
Watch out
on the Free plan, Make handles files up to 5 MB, so a heavier document stops at this module.
Vapi28

List Files

SearchIn the docs only

List Files shows the files stored in your Vapi account as a series of bundles you can filter, count or export.

When to use it
before an Upload File, to spot an older copy you want to replace or remove.
Watch out
each file becomes a bundle; when you only need one line in a sheet, add an aggregator right after.
Vapi29

Get File

ActionIn the docs only

Get File fetches one file from Vapi so a scenario can check it or pass it along to another app.

When to use it
a colleague asks which version sits in Vapi, and you want a copy dropped in a shared folder.
Watch out
it expects a single file; map it from List Files so the scenario always follows the right one.
Vapi30

Delete File

ActionIn the docs only

Delete File removes a file from your Vapi account, the cleanup step once a document is out of date.

When to use it
right after Upload File has sent the new version, to drop the old one in the same run.
Watch out
the doc mentions no way to recover a deleted file, so check with Run once that the bundle holds the old file and not the new one.
Vapi31

Update File

ActionIn the docs only

Update File changes a file already stored in Vapi instead of adding a second copy next to it.

When to use it
you would rather keep one file in Vapi than upload a new one and delete the old one in turn.
Watch out
the doc does not say what you can edit on a file; open the module in Make to see what it offers before you rely on it.

Other

1 module
Vapi32

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call reaches any endpoint of the Vapi API with the connection you already set up, which covers what the other modules leave out.

When to use it
you need a request missing from the list, such as removing a squad or adding a phone number, when the Vapi API offers it.
Watch out
you write the request yourself, so keep the Vapi API reference open while you fill in the module.

Other modules

2 modules
Vapi33

Create an Outbound Phone Call

Action

In Make“Creates an outbound phone call to Twilio or Vonage number added on your dashboard.”

Create an Outbound Phone Call has your assistant dial out through a Twilio or Vonage number you added in the Vapi dashboard.

When to use it
an appointment request comes in and the assistant should call the customer back to confirm the slot.
Watch out
without a Twilio or Vonage number in your Vapi dashboard, the module has nothing to call from; add one there first.
Vapi34

Respond to a Tool Call

Action

In Make“Returns the response to the function call be it error or result.”

Respond to a Tool Call sends the answer back to Vapi after Watch Tool Call Request, so the assistant can carry on with the conversation.

When to use it
at the end of every scenario that starts with Watch Tool Call Request, once the data has been fetched from your other app.
Watch out
the module accepts an error as well as a result, so use that option when the lookup finds nothing.
Need help

Need help automating Vapi with Make?

A person reads every message.

FAQ

Vapi and Make: common questions

01Is the Vapi Make integration free?
Yes, Vapi is a standard app in Make, so you can use it from the Free plan. That plan allows 2 active scenarios, a minimum of 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) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one execution of one module on one bundle. Your Vapi subscription is a separate matter.
02What do you need to connect Vapi to Make?
You need a Vapi account and its private API key. In Vapi, open Build then Vapi API Keys in the left sidebar and copy the Private Key value; if none exists, click Add Key to create one. In Make, add any Vapi module, click Create a connection, give it a name if you like, paste the key in the API Key field and click Save. If Make asks you to authenticate and confirm access, do so. Every Vapi module in your scenarios then reuses that single connection.
03Do the Vapi triggers in Make react in real time?
Yes, both Vapi triggers are instant. Watch Tool Call Request and Watch End of Call Report are called by Vapi through a webhook as soon as the event happens, so the scenario starts without waiting for a schedule. That matters for tool calls, since the caller is still on the line. In the editor, these modules carry a lightning badge rather than the clock of a scheduled trigger. There is no scheduled Vapi trigger in Make, so the 15 minute default schedule does not apply to them.
04What if a Vapi module is missing in Make?
Use Make an API Call. It calls any endpoint of the Vapi API with the connection you already created, which is the way to fill gaps such as deleting a squad or managing phone numbers beyond the list module. The doc gives no numbered limit for this app. Also note that the five Workflow modules are marked as deprecated, so a new scenario should rely on the Assistants, Squads or Tools groups, or on an API call, rather than on them.
05Should you pick Make or n8n for Vapi?
It depends on the tool your team already builds in. On the Make side, Vapi comes with 36 modules, including 2 instant triggers for tool calls and end of call reports, plus Make an API Call for anything missing. The same app often has an n8n node too, so check that side before deciding. This page ranks neither tool: the n8n vs Make comparison linked above sets out the criteria side by side, and the choice comes down to the modules you need for your calls.
Same platform

Other docs you might need on this stack.

Browse all integrations