Resources · Make integration

Voicenter Make integrationAutomate Voicenter with Make.

Can your phone system talk to the rest of your tools without code? The Voicenter Make integration offers 22 modules: 4 triggers, 17 actions and 1 search. This guide is for support and sales ops teams, and it takes you from the connection to a first live scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Voicenter Make integration do?

The Voicenter Make integration links your Voicenter account to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules that runs on a schedule. Each module is one brick of that chain, so Voicenter events can start work in other apps, and other apps can drive your Voicenter campaigns and agents.

Answer callers from your own data. Pair Watch New IVR Notifications with Respond to IVR and your IVR menu can reply with information pulled from a CRM or a spreadsheet, instead of a fixed recording. The IVR trigger is scheduled, though, so the reply arrives on the scenario's rhythm, not while the caller waits.

Keep dialer campaigns in step with your sales pipeline. When a list of leads is ready in another tool, Add Destinations In Bulk loads the numbers and Start Campaign launches the calls. Stop Campaign and Clear Campaign Calls tidy up once the push is over.

Staff the queue from your HR or shift tool. Add Agent and Remove Agent follow the roster, so the people who take calls match who is actually on duty.

Know the limits before you build. Make's own documentation for Voicenter is short: it lists the modules without describing their fields, because little public information exists about the app, so what this page says about each module is read from its name. Test each module with Run once before trusting it, and keep the Make troubleshooting guide nearby. If you are still choosing a platform, the n8n vs Make comparison and our Make review lay out the criteria.

Connect

How do you connect Voicenter to Make?

  1. 01

    Add a Voicenter module

    In your scenario, click the + and search for Voicenter. Pick any of its modules, then click Create a connection. A connection is your Voicenter account linked to Make once, then reused by every Voicenter module.

  2. 02

    Name it and authorize

    Give the connection a clear name if you like, such as the account it belongs to. Then either authorize Make on the Voicenter page that opens, or paste the key Voicenter gives you, depending on what the window asks for.

  3. 03

    Save and check

    Click Save. The connection now appears in the module's dropdown, and Make can list what it reads from your account. If nothing loads, the account or key is the first thing to check.

First scenario

Your first scenario: turn new team members into Voicenter agents

GoalWhen a new person joins your roster in another app, Make adds them to Voicenter with Add Agent.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + in the middle of the canvas to place your first module. This canvas is where your automation takes shape.

  2. 02

    Start from your roster

    Pick the app where your team schedule lives, such as a spreadsheet or your HR tool, and choose its module that watches new entries. That app starts the flow, and Voicenter comes right after it.

  3. 03

    Add the agent

    Click the + on the right, search for Voicenter and choose Add Agent. Create the connection if needed, then map the person's details from the previous module into its fields.

  4. 04

    Test with Run once

    Add a test person to your roster, then click Run once. Open each module's bubble to read the bundle it received, one item passed along, and check that the agent appears in Voicenter.

  5. 05

    Schedule and switch on

    Set the clock on the first module, every 15 minutes by default, then turn the scenario on. Each module run counts as an operation on your Make plan.

Triggers

What can start a Voicenter scenario?

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

Voicenter1Watch Custom Webhook

Watch Custom Webhook

triggerIn the docs only

Gives you a way to start a scenario from a custom notification you set up on the Voicenter side, rather than one of the ready-made event types below. The module name is all Make's documentation provides, so treat it as the open door for events the other three triggers do not cover.

How it fires
scheduled. Make checks the app on the scenario's schedule, not the moment the event happens.
When to use it
your team configured a specific notification in Voicenter and none of the named triggers matches it.
Watch out
no fields are documented, so run it once with a real event and inspect the bundle before you map anything.
Voicenter2Watch New CDR Notification

Watch New CDR Notification

triggerIn the docs only

Brings each new CDR notification from Voicenter into Make, so the details of a finished call can land in your CRM, a sheet or a ticket without anyone copying them. It is the natural starting point for call logging and reporting scenarios.

How it fires
scheduled. Make checks the app on the scenario's schedule.
When to use it
a sales manager wants every call attached to the matching contact in the CRM.
Watch out
the documentation lists no fields; read the first bundle from Run once to see what a record contains.
Voicenter3Watch New IVR Notifications

Watch New IVR Notifications

triggerIn the docs only

Lets your scenario react to what happens in your IVR menu, the automated voice menu callers move through. Each new notification becomes a bundle you can route, log or answer with the Respond to IVR module further down the chain.

How it fires
scheduled. Make checks the app on the scenario's schedule, so pick an interval your callers can live with.
When to use it
you want menu choices written to a support tool, or a dynamic reply built from your data.
Watch out
the free plan's minimum interval is 15 minutes, which is slow for a live caller.
Voicenter4Watch New Popup Notifications

Watch New Popup Notifications

triggerIn the docs only

Picks up the notifications behind Voicenter's popup, the window agents see for an incoming call, so another app can learn that a call is coming in. Paired with Respond to Chrome Popup Extension, it closes the loop between the phone and the agent's browser.

How it fires
scheduled. Make checks the app on the scenario's schedule.
When to use it
you want each popup event recorded next to the customer's file in your helpdesk.
Watch out
fields are undocumented; test with a real call and read the bundle before mapping.
Modules

What can Make do in Voicenter?

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

Voicenter1

Add Agent

ActionIn the docs only

Puts an agent into Voicenter from another tool, so a new hire or a shift change reaches the phone system without a manual step in the admin panel. The roster stays the single place where staffing is decided.

When to use it
a person is added to your HR or scheduling app and should start taking calls.
Watch out
run it once with a test agent to learn which details Voicenter expects.
Voicenter2

Add Destinations In Bulk

ActionIn the docs only

Loads many destinations in one go, which keeps a campaign fed with a whole list rather than one number at a time and saves operations on your plan. Reach for it whenever the list already exists somewhere else.

When to use it
a lead export is ready in your CRM and the whole batch should join a dialer campaign.
Watch out
for a single contact, Add a Destination is simpler to map.
Voicenter3

Add a Destination

ActionIn the docs only

Adds one destination, which suits scenarios where contacts arrive one by one, such as a web form or a new deal. Each bundle becomes one entry, so the mapping stays easy to read and to debug.

When to use it
a prospect asks for a callback on your site and should enter the calling list right away.
Watch out
with a long list, this module costs one operation per contact; the bulk version is lighter.
Voicenter4

Clear Campaign Calls

ActionIn the docs only

Empties the calls queued in a campaign, a clean slate before you reload it or once the campaign has served its purpose. It spares your agents from dialing people who no longer belong on the list.

When to use it
a promotion ends in your e-commerce tool and the remaining calls about it should go.
Watch out
treat it as destructive; add a filter so it only runs on the campaign you mean.
Voicenter5

Create an IVR Response

ActionIn the docs only

Builds a response for your IVR from data your scenario holds, so the menu can say something specific instead of a generic message. It is the building step, while Respond to IVR is the one that sends the answer back.

When to use it
the caller's account status, found in your billing tool, should shape what the menu tells them.
Watch out
the fields are undocumented; check the result with Run once on a test line.
Voicenter6

Get Call History by ID

ActionIn the docs only

Fetches the history of one specific call when you already know its identifier, handy for enriching a ticket or a CRM note after the fact. You get one call back, not a list to sift through.

When to use it
a support ticket mentions a call and the agent wants its details attached automatically.
Watch out
the module needs the ID from an earlier step, so map it from a trigger or another app.
Voicenter7

Get Campaign Details

ActionIn the docs only

Reads the details of a campaign so a later module can decide what to do, or so a report somewhere else shows where the campaign stands. It changes nothing in Voicenter, which makes it a safe first test.

When to use it
a dashboard sheet should show the state of an outbound campaign next to sales figures.
Watch out
inspect the bundle before mapping, since the returned fields are not documented.
Voicenter8

Get Campaign Members List

ActionIn the docs only

Returns who belongs to a campaign, useful for comparing that list with your CRM or for checking that the right people are on it. It answers the question of who is in, where Get Campaign Details describes the campaign itself.

When to use it
before a launch, a manager wants the member list checked against opt-outs.
Watch out
a list may come back as one bundle; look at the output shape before looping over it.
Voicenter9

Get Campaign Pending Calls

ActionIn the docs only

Shows the calls still waiting in a campaign, so your scenario can report on the backlog or decide whether to stop, clear or reload it. It pairs well with Clear Campaign Calls and Stop Campaign.

When to use it
a team lead wants an alert in the chat tool when the queue of pending calls stays high.
Watch out
read-only data can still cost operations if the scenario runs often; set a sensible schedule.
Voicenter10

List Accounts

SearchIn the docs only

Retrieves the Voicenter accounts your connection can see, the search module of the app. Like any search, it can return zero, one or several bundles, and each one flows separately into the next module.

When to use it
an agency managing several client accounts wants each one listed in a sheet.
Watch out
every account found runs the following modules again, so the operation count grows with the list.
Voicenter11

Make an API Call

ActionIn the docs only

Reaches any endpoint of the Voicenter API from your scenario, with the connection you already set up. It is the fallback when none of the 17 actions or the search covers what you need.

When to use it
your developer points to a Voicenter API feature that has no dedicated module.
Watch out
you write the request yourself, so get the endpoint details from your Voicenter admin or developer, and test with Run once.
Voicenter12

Remove Agent

ActionIn the docs only

Takes an agent out of Voicenter when your source of truth says so, which keeps departed staff or off-duty people from receiving calls. It mirrors Add Agent and usually lives in the same roster scenario.

When to use it
someone leaves the company and the offboarding checklist in your HR app should cover the phones too.
Watch out
a wrong mapping removes the wrong person; filter carefully and test on a dummy agent.
Voicenter13

Remove Call

ActionIn the docs only

Deletes a single call from where it waits, a precise tool when one contact should not be dialed while the rest of the campaign goes on. Clear Campaign Calls is the heavy option; this one is surgical.

When to use it
a lead books a meeting on their own and no longer needs the scheduled callback.
Watch out
check the identifier you map, and try it on a test call before a real campaign.
Voicenter14

Respond to Chrome Popup Extension

ActionIn the docs only

Sends information back to the Voicenter popup in the agent's Chrome browser, so the person answering sees context pulled from your other tools. It is the answer half of Watch New Popup Notifications.

When to use it
agents should see the caller's open orders from your shop before they pick up.
Watch out
a scheduled trigger may reply after the call is answered; keep expectations on timing modest.
Voicenter15

Respond to IVR

ActionIn the docs only

Answers your IVR with the reply your scenario prepared, turning the menu into something that reacts to your data. Use it after Watch New IVR Notifications, and after Create an IVR Response when you build the reply first.

When to use it
a caller's menu choice should get a follow-up built from your order data.
Watch out
the IVR trigger is scheduled, so the reply can come minutes after the call; test the full path with a real call first.
Voicenter16

Start Campaign

ActionIn the docs only

Launches a Voicenter campaign from a scenario, so calling begins when the conditions in your other tools are met rather than when someone remembers to click. It is the natural last step after loading destinations.

When to use it
a lead list is approved in your CRM and the outbound team should start calling it.
Watch out
make sure the destinations are in place first, or the campaign starts empty.
Voicenter17

Stop Campaign

ActionIn the docs only

Halts a running campaign when something outside Voicenter says it should end, such as a quota reached or an offer withdrawn. Your agents stop dialing without anyone logging in to the admin panel.

When to use it
the event a campaign promotes sells out in your ticketing tool.
Watch out
the name does not say whether stopping also drops pending calls; check the campaign in Voicenter after a test.
Voicenter18

Webhook Response

ActionIn the docs only

Sends a reply back to whatever called your scenario through a webhook, the address an app uses to contact Make. It lets Voicenter, or another caller, receive a clear answer instead of silence.

When to use it
a custom notification expects a confirmation or a piece of data in return.
Watch out
place it on the path the scenario actually takes, or the caller never hears back.
Need help

Need help automating Voicenter with Make?

A person reads every message.

FAQ

Voicenter and Make: common questions

01Is the Voicenter Make integration free?
Yes, Voicenter is a standard app in Make, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between 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 credits, the operations your modules run each month. Your Voicenter subscription is separate from Make.
02What do you need to connect Voicenter to Make?
A Voicenter account and access to its authorization or key. Make's documentation for Voicenter lists no specific prerequisites and no dedicated connection steps, so the generic flow applies: add a Voicenter module, click Create a connection, name it if you want, then authorize Make on the Voicenter page or paste the key the app gives you, and click Save. The connection is then reused by all 22 modules. If you do not have the key, ask whoever administers your Voicenter account.
03Do Voicenter triggers in Make fire in real time?
No. All 4 Voicenter triggers are listed as scheduled, so Make checks for new events on the scenario's schedule rather than being alerted the instant they happen. A new scenario runs every 15 minutes by default, which is also the minimum on the Free plan; paid plans go down to 1 minute. For IVR or popup replies where a caller is waiting, keep that delay in mind and pick a paid plan if the interval matters to your team.
04What if the Voicenter module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the Voicenter API with the connection you already have, so you are not limited to the 17 actions and the one search. Be aware that Make's documentation for Voicenter is limited: it names the modules without describing their fields, because little public information about the app exists. Plan to test each module with Run once and read the bundles it returns before you rely on it.
05Make or n8n for Voicenter?
It depends on your criteria rather than on a winner. On Make, Voicenter comes with 22 ready modules, including triggers for CDR, IVR and popup notifications, plus Make an API Call for the rest, all usable from the Free plan. Many apps also have an n8n node, so check whether one exists for Voicenter and what it covers before you decide. Compare the modules each tool offers for your use case, how your team prefers to build, and how each platform counts usage.