- Home
- Resources
- Integrations
- Voicenter
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 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.
How do you connect Voicenter to Make?
- 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.
- 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.
- 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.
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.
- 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.
- 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.
- 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.
- 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.
- 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.
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.
Watch Custom Webhook
triggerIn the docs onlyGives 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.
Watch New CDR Notification
triggerIn the docs onlyBrings 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.
Watch New IVR Notifications
triggerIn the docs onlyLets 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.
Watch New Popup Notifications
triggerIn the docs onlyPicks 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.
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.
Modules index
- Add Agent
- Add Destinations In Bulk
- Add a Destination
- Clear Campaign Calls
- Create an IVR Response
- Get Call History by ID
- Get Campaign Details
- Get Campaign Members List
- Get Campaign Pending Calls
- List Accounts
- Make an API Call
- Remove Agent
- Remove Call
- Respond to Chrome Popup Extension
- Respond to IVR
- Start Campaign
- Stop Campaign
- Webhook Response
Add Agent
ActionIn the docs onlyPuts 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.
Add Destinations In Bulk
ActionIn the docs onlyLoads 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.
Add a Destination
ActionIn the docs onlyAdds 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.
Clear Campaign Calls
ActionIn the docs onlyEmpties 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.
Create an IVR Response
ActionIn the docs onlyBuilds 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.
Get Call History by ID
ActionIn the docs onlyFetches 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.
Get Campaign Details
ActionIn the docs onlyReads 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.
Get Campaign Members List
ActionIn the docs onlyReturns 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.
Get Campaign Pending Calls
ActionIn the docs onlyShows 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.
List Accounts
SearchIn the docs onlyRetrieves 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.
Make an API Call
ActionIn the docs onlyReaches 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.
Remove Agent
ActionIn the docs onlyTakes 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.
Remove Call
ActionIn the docs onlyDeletes 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.
Respond to Chrome Popup Extension
ActionIn the docs onlySends 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.
Respond to IVR
ActionIn the docs onlyAnswers 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.
Start Campaign
ActionIn the docs onlyLaunches 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.
Stop Campaign
ActionIn the docs onlyHalts 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.
Webhook Response
ActionIn the docs onlySends 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.
Need help automating Voicenter with Make?
A person reads every message.