Resources · Make integration

VoiceDrop Make integrationAutomate VoiceDrop with Make.

What if every new lead got a voicemail without anyone picking up a phone? The VoiceDrop Make integration gives you 3 action modules for ringless voicemail. This guide is for sales and ops teams: connect your key, then build your first scenario.

Try the VoiceDrop integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the VoiceDrop Make integration do?

The VoiceDrop Make integration lets a Make scenario, the automation you build in Make, drop a ringless voicemail (RVM) through your VoiceDrop account. Each scenario is a chain of modules, one brick per step, and VoiceDrop supplies the steps that send the message.

Call back a fresh lead without dialing. An insurance broker receives a quote request from a web form. The form app starts the scenario, and Send a Static Audio RVM drops the recording the broker already prepared, so the prospect hears a familiar voice before the first real call.

Personalize the message per contact. A roofing contractor wants each homeowner to hear a message that fits the job. Send an AI Voice RVM is the module to try here, the one whose name points to an AI voice rather than a fixed file.

Reach a VoiceDrop feature the other modules skip. Make an API Call calls any endpoint of the VoiceDrop API with the same connection, which covers what the two send modules leave out.

One limit to keep in mind: the app has no trigger, so nothing in VoiceDrop can start a scenario. Another app, or the schedule of Make, has to open the flow. Before you commit, read the Make review and check the Make pricing page. If you are weighing both tools, the n8n vs Make comparison lays out the criteria.

Connect

How do you connect VoiceDrop to Make?

  1. 01

    Copy your API key

    In VoiceDrop, open the API section with the API button in the left menu, pick the Ringless Voicemail endpoint and click Headers. The key shown there is what Make needs. You also need an active VoiceDrop account.

  2. 02

    Start the connection

    In your Make scenario, add any VoiceDrop module and click Create a connection. A connection is your VoiceDrop account linked to Make once; every VoiceDrop module in your scenarios reuses it afterward.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when you run several accounts. Paste the key you copied, or follow the instructions on screen, then save. The module can now use your account.

First scenario

Build your first scenario with VoiceDrop

GoalWhen a new lead lands in another app, Make sends that person a VoiceDrop ringless voicemail.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. This first module has to come from another app, your form tool or CRM, because VoiceDrop has no trigger.

  2. 02

    Set up the starting app

    Search the app that receives your leads, pick its module and link its account. From now on, each new lead reaches the next step as a bundle, one item passed from module to module.

  3. 03

    Add the VoiceDrop action

    Click the + on the right, search VoiceDrop and choose Send a Static Audio RVM. Select your connection, then map the lead details from the first module into the fields the module shows you.

  4. 04

    Test with Run once

    Click Run once to run the scenario a single time. Open each module to read the bundles it received and check that the voicemail went to the right person before going further.

  5. 05

    Schedule and switch on

    On the first module, set the clock: a new scenario checks every 15 minutes by default. Then switch the scenario on. Each module run counts as an operation, the unit Make bills on your plan.

Modules

What each VoiceDrop module does

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

VoiceDrop1

Make an API Call

ActionIn the docs only

Gives you access to any endpoint of the VoiceDrop API from inside your scenario, using the connection you already set up. You write the request yourself instead of filling a ready form.

When to use it
you need a VoiceDrop feature that neither send module covers, and you are comfortable reading the VoiceDrop API docs.
Watch out
this is the technical option, so start with the two send modules and only fall back on it when they fall short.
VoiceDrop2

Send a Static Audio RVM

ActionIn the docs only

Puts a ringless voicemail in a contact's inbox using a static audio, which by its name means a set recording rather than a generated voice. Everyone who receives it hears the same message.

When to use it
a new quote request comes in and you want the prospect to hear the recording your sales rep already made.
Watch out
no field is documented for this module yet, so check in Make which inputs it asks for before you map data.
VoiceDrop3

Send an AI Voice RVM

ActionIn the docs only

Delivers a ringless voicemail spoken by an AI voice, as the module name tells you, which is the route to try when a single recording cannot fit every contact.

When to use it
each homeowner or client should hear something tied to their own request, and you have that detail in the previous module.
Watch out
run it once on your own number first and listen to the result before it reaches real contacts.
Need help

Need help automating VoiceDrop with Make?

A person reads every message.

FAQ

Common questions about VoiceDrop and Make

01Is the VoiceDrop Make integration free?
Yes, on the Make side. VoiceDrop is a standard app, available from the Free plan. That plan gives you 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 (Core, Pro, Teams and Enterprise) lower the interval to one minute and remove the cap on active scenarios. You still need an active VoiceDrop account, and its subscription is a separate matter covered on the VoiceDrop pricing page.
02What do you need to connect VoiceDrop to Make?
Two things: an active VoiceDrop account and its API key. You find the key in VoiceDrop under the API section of the left menu, inside the Ringless Voicemail endpoint, on the Headers tab. In Make, add a VoiceDrop module, click Create a connection, give it a name if you like and paste the key. That connection is then reused by every VoiceDrop module you add later, so you only do this once per account.
03Can a VoiceDrop scenario start by itself?
Not from VoiceDrop. The app has no trigger, only three action modules, so nothing that happens in VoiceDrop can launch a scenario. Two options remain. Put a trigger from another app first, such as the form or CRM where leads arrive, and Make picks up the new items, on your schedule or right away, depending on that trigger's type. Or run the scenario on the Make schedule alone, which checks every 15 minutes by default on a new scenario. Either way, VoiceDrop acts at the end of the flow.
04What if the VoiceDrop module you need is missing?
Use Make an API Call. It reaches any endpoint of the VoiceDrop API with the connection you already have, so you are not limited to the two send modules. You write the request yourself, which asks for a look at the VoiceDrop API documentation. Keep in mind that the Make documentation for this app is marked as AI-generated from the VoiceDrop docs and may contain mistakes, so for any doubt about a vendor detail, VoiceDrop support is the right place to ask.
05Should you use Make or n8n for VoiceDrop?
It depends on the tool your team already runs. In Make, VoiceDrop offers three modules: two ready ways to send a ringless voicemail and Make an API Call for the rest, all available on the Free plan. Many apps also have an n8n node, so if n8n is already your platform, check whether one exists for VoiceDrop before switching. The two tools are not ranked here on speed or cost; the deciding factor is where your other automations already live.
Same platform

Other docs you might need on this stack.

Browse all integrations