Resources · Make integration

VoiceSpin Make integrationAutomate VoiceSpin with Make.

Can Make feed leads to VoiceSpin and trigger calls or texts for you? The VoiceSpin Make integration gives you 8 action modules and no trigger. This guide is for sales and support teams who want leads, calls and SMS handled by a scenario, and it walks you through your first one.

Try the VoiceSpin integration on MakeSee the 8 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the VoiceSpin Make integration let you automate?

The VoiceSpin Make integration links your VoiceSpin account to Make, a no-code tool where you build a scenario, meaning the automation itself: a chain of modules, each one a single brick such as an action. Here every VoiceSpin module is an action, so something else starts the flow and VoiceSpin carries out the work.

Leads that land in the dialer on their own. A form, a CRM or a spreadsheet collects a contact, and Add a Lead sends it to VoiceSpin. When the record changes elsewhere, Update lead keeps both sides aligned, and Remove Lead takes out a contact who should no longer be called.

A first touch the moment a lead appears. Chain Make a Call, Send SMS or Send Message via Messaging after the lead is added, so the contact hears from you while the interest is fresh. For ideas on the messaging side, the 2Chat Make integration shows another angle.

Follow-up once a call wraps up. End of Call sits at the close of a call flow; combined with modules from your other tools, it lets the rest of your process pick up where the conversation stopped.

A limit to know upfront: Make states that its documentation for VoiceSpin is incomplete because little public information exists about the app. Test each module with real data before you rely on it, and keep Make troubleshooting close. If you are still choosing a platform, read n8n vs Make first.

Connect

How do you connect VoiceSpin to Make?

  1. 01

    Add a VoiceSpin module

    In your scenario, click the +, search for VoiceSpin and pick any of its modules, for instance Add a Lead. Then click Create a connection: a connection is your VoiceSpin account linked to Make once, then reused by all its modules.

  2. 02

    Name it and authorize Make

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

  3. 03

    Save and check the module

    Click Save. The connection now appears in the module, and once it exists Make can list what it reads from your account while you fill in the fields. Every other VoiceSpin module will offer the same connection.

First scenario

Your first scenario with VoiceSpin and Make

GoalWhen a new contact shows up in another app, Make adds it to VoiceSpin and sends it a text.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Since VoiceSpin has no trigger, start with the app where your contacts arrive, such as a form tool or your CRM.

  2. 02

    Add the lead to VoiceSpin

    Click the + on the right of that first module, pick VoiceSpin, then Add a Lead. Select your connection and map the contact data coming from the previous module into the fields.

  3. 03

    Send the first text

    Add one more module with the +: Send SMS. Map the phone number from the earlier modules and write the message. Each bundle, one contact here, gets its own text.

  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 confirm the lead reached VoiceSpin before the SMS left.

  5. 05

    Schedule and switch it on

    On the first module, set the schedule, every 15 minutes by default, then turn the scenario on. On the Free plan, 15 minutes is also the shortest gap between two scheduled runs.

Modules

What can each VoiceSpin module do in Make?

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

VoiceSpin1

Add a Lead

ActionIn the docs only

Add a Lead creates a new lead in VoiceSpin from data another app collected, so nobody has to type contacts into the dialer by hand. It is usually the first VoiceSpin step of a scenario.

When to use it
right after a form submission or a new CRM contact, when that person should enter your calling lists.
Watch out
Make publishes no field list for this module, so run it once and check in VoiceSpin that each value landed where you expected.
VoiceSpin2

End of Call

ActionIn the docs only

Going by its name, End of Call deals with the close of a call in VoiceSpin, which gives your scenario a clear point where a conversation is marked as finished. Make does not describe it further.

When to use it
in a flow that follows a call from start to finish, when the next steps depend on the call being over.
Watch out
because the documentation stays silent on what it expects, test it on a dummy call before placing it in a live scenario.
VoiceSpin3

Make a Call

ActionIn the docs only

With Make a Call, a scenario asks VoiceSpin to place a phone call, so a fresh lead can be contacted without an agent searching for the number first. It pairs naturally with Add a Lead earlier in the flow.

When to use it
when speed matters, for example as soon as someone requests a callback through a web form.
Watch out
every run means a real call; use a test number while you try it with Run once.
VoiceSpin4

Make an API Call

ActionIn the docs only

Make an API Call is your way out when none of the other seven modules covers the task: it reaches any endpoint of the VoiceSpin API while reusing the same connection, so you do not set up authentication again.

When to use it
for an operation VoiceSpin supports but that has no dedicated module in Make.
Watch out
you need the VoiceSpin API reference at hand, since Make gives no detail about which endpoints exist.
VoiceSpin5

Remove Lead

ActionIn the docs only

Remove Lead takes a contact out of VoiceSpin, which keeps your team from calling someone who has already bought, unsubscribed or been disqualified in another tool.

When to use it
when a status change in your CRM means the person should leave your calling lists.
Watch out
Make does not say whether a removal can be undone, so add a filter before this module, so only the right contacts reach it; a wrong mapping could clear leads you still need.
VoiceSpin6

Send Message via Messaging

ActionIn the docs only

Judging by its name, Send Message via Messaging lets a scenario send a written message through the messaging channels VoiceSpin handles, a softer option than a call for a first contact or a reminder.

When to use it
when your contacts prefer to read rather than pick up, or as a follow-up after an unanswered call.
Watch out
Make does not say which channels are covered, so confirm in your VoiceSpin account what is active before building around it.
VoiceSpin7

Send SMS

ActionIn the docs only

Send SMS fires off a text message from VoiceSpin inside your scenario, giving each new lead or customer a quick, short note without anyone opening the dialer.

When to use it
to confirm a request, announce a callback or reach someone who missed your call.
Watch out
the module sends one text per bundle, so a scenario that receives a list of contacts sends as many messages; check the count in Run once.
VoiceSpin8

Update lead

ActionIn the docs only

Update lead edits a contact that already exists in VoiceSpin, so the details your agents see match what changed in your CRM or your forms.

When to use it
when a phone number, an owner or a status is corrected in another tool and should follow into VoiceSpin.
Watch out
the lead has to exist first; if your flow can meet brand new contacts, place Add a Lead on a separate route for them.
Need help

Need help automating VoiceSpin with Make?

A person reads every message.

FAQ

VoiceSpin and Make: common questions

01Is the VoiceSpin Make integration free?
Yes, on the Make side. VoiceSpin is a standard app, so it is available from the Free plan onward. The Free plan comes with limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution at most per run, files up to 5 MB and 512 MB of data transfer. Paid plans drop the interval to 1 minute and remove the cap on active scenarios. Each module run counts as an operation on your plan. Your VoiceSpin subscription is a separate matter that this page does not cover.
02What do you need to connect VoiceSpin to Make?
A VoiceSpin account and a Make account. The Make documentation lists no specific prerequisite for VoiceSpin and gives no official connection steps, so the generic flow applies: add a VoiceSpin module, click Create a connection, name it if you wish, then either approve Make on the VoiceSpin page or paste the key the app provides, and click Save. The connection is reused by all 8 VoiceSpin modules afterward, so this setup happens only once per account.
03Does the VoiceSpin Make integration react in real time?
No, because VoiceSpin has no trigger module in Make, only actions. Your scenario therefore starts somewhere else. You can open it with a trigger from another app, such as a form or a CRM, and add the VoiceSpin actions after it. You can also let the schedule on the first module run the scenario, every 15 minutes by default, with 1 minute as the shortest interval on paid plans. Whether that start is instant depends entirely on the other app you pick.
04What if the VoiceSpin module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the VoiceSpin API from your scenario with the connection you already created, so it covers what the seven named modules leave out. Keep in mind that Make says its VoiceSpin documentation is incomplete, owing to limited public information on the app. Check the VoiceSpin API reference for the endpoint you need, and test the call with Run once before switching the scenario on.
05Should you use Make or n8n with VoiceSpin?
It depends on the tool your team already works in. On Make, VoiceSpin offers 8 action modules and no trigger, including Make an API Call for anything else, and it runs from the Free plan. An app often has an n8n node too, but this page cannot confirm one for VoiceSpin, so check the n8n node list before you decide. Compare what each side covers for your exact use case, leads, calls or texts, rather than picking on reputation.
Same platform

Other docs you might need on this stack.

Browse all integrations