Resources · Make integration

Cloudonix Make integrationAutomate Cloudonix with Make.

Can a phone call drive an automation without a line of code? The Cloudonix Make integration gives you 29 modules: 4 instant triggers, 20 actions and 5 searches. This page shows how to link your account, build a first call flow and pick the right module for each job.

Try the Cloudonix integration on MakeSee the 29 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Cloudonix Make integration let you automate?

The Cloudonix Make integration links your Cloudonix voice platform to Make, so calls can start a scenario (the automation you build in Make, a chain of modules) and the scenario can answer back. A module is one brick of that chain: a trigger, an action or a search. Here, the bricks speak, listen, transfer and hang up.

Every finished call lands in your reporting. Watch New Call Details Report receives the call record Cloudonix sends once a call is over. Pass it to a spreadsheet or a CRM module from another app, and your sales team sees each conversation logged without typing anything.

A small phone menu, built visually. Watch New Voice Application Request [Attached] fires when someone dials a number tied to your voice application. Chain [CXML] Say Something (Text-To-Speech) to greet the caller, then [CXML] Gather Input to read the digit pressed on the keypad and send the call where it belongs.

Outbound calls from any event. Make Call and Do Something Smart dials a phone number or a Cloudonix subscriber, then acts on the connected call. A form entry or a new ticket in another app can be the spark.

What the listed modules do not cover, Make an API Call reaches through the same connection, against the Cloudonix REST API. The Cloudonix documentation for Make is flagged as AI-generated, so check an important detail with Cloudonix before relying on it. Before you pick a plan, read Make pricing; if you hesitate between the two tools, the n8n vs Make comparison lays out the criteria, and Make training helps if this is your first scenario.

Connect

How do you connect your Cloudonix account to Make?

  1. 01

    Get your API key in Cloudonix

    In Cloudonix, open the API keys management area (under account, customer or domain administration, depending on your access). Create a new key, give it a name, then note its keyId: a string that starts with the letters XI.

  2. 02

    Add a Cloudonix module in Make

    In your scenario, add any Cloudonix module and click Create a connection. A connection is your Cloudonix account linked to Make once, then reused by every Cloudonix module. The Connection name field is optional.

  3. 03

    Paste the credential and save

    Enter the keyId you copied, or follow the instructions Make shows on screen, then confirm. Once the connection exists, Make lists what it can read from your account when you fill a module.

First scenario

Your first scenario with Cloudonix

GoalWhen someone submits a callback form in another app, Make calls them back through Cloudonix.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big +. Add the trigger of the app that collects your callback requests, a form tool or your CRM.

  2. 02

    Add the Cloudonix call

    Click the + on the right of that trigger, search Cloudonix and pick Make Call and Do Something Smart. Click Create a connection and paste your keyId.

  3. 03

    Map the phone number

    Fill the module fields: Make lists the data from the form, so drag the phone number the visitor typed into the destination. Choose what happens once the call connects.

  4. 04

    Test with Run once

    Click Run once and submit the form with your own number. Your phone should ring. The bubble above each module shows the bundle it received, meaning the item passed from one module to the next.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module (every 15 minutes by default, or instant if the form app offers it) and switch the scenario on. Each run counts operations: one module run on one bundle.

Triggers

What starts a Cloudonix scenario?

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

Cloudonix1Watch New Call Details Report

Watch New Call Details Report

Instant trigger

In Make“A HTTP Endpoint for processing CDR records reported by Cloudonix.”

You get the full record of each call the moment Cloudonix reports it, ready to feed a log, a dashboard or a billing check. The report is what telecom people call a CDR, one per call.

How it fires
instant, Cloudonix calls Make through a webhook as soon as the record exists, nothing to poll.
When to use it
a support desk that wants every finished call written into its ticket history without anyone copying numbers by hand.
Watch out
if a call carried data from Store Session Data, that data travels with the report, so plan a place for it in your destination.
Cloudonix2Watch New Voice Application Request [Attached]

Watch New Voice Application Request [Attached]

Instant trigger

In Make“An Attached Voice Application is a CXML application that is defined for immediate access inside Cloudonix. A Connected Voice Application will appear in the Cloudonix cockpit - and should have a DNID number (at least one) assigned to it.”

This trigger lets Make decide what happens on an incoming call, for a voice application that lives inside Cloudonix and shows up in the Cloudonix cockpit. Your scenario becomes the call flow.

How it fires
instant, Cloudonix calls Make through a webhook as soon as the request comes in.
When to use it
a hotline number where callers hear a greeting and choose a department with the keypad.
Watch out
the application needs at least one DNID number assigned to it, otherwise no call ever reaches the scenario.
Cloudonix3Watch New Voice Application Request [Detached]

Watch New Voice Application Request [Detached]

Instant trigger

In Make“A Detached Voice Application is a CXML application that is served remotely, and is not available in the Cloudonix cockpit. External Voice Applications are used for executing call flows, that are not directly invoked via a DNID.”

Same idea as the attached version, for a voice application served from outside and absent from the Cloudonix cockpit. It covers call flows that no DNID number starts directly.

How it fires
instant, Cloudonix calls Make through a webhook as soon as the flow hands over.
When to use it
a second stage of a call, such as the branch a caller reaches after pressing a key, or the target of [CXML] Transfer Control.
Watch out
since no number points at it, you only reach it from another application, so build and test the entry point first.
Cloudonix4Watch Session Update Event

Watch Session Update Event

Instant trigger

In Make“A URL to receive session update notifications if no session callback is specified on a session being updated.”

You hear about changes on a live call session and can react while the call is still going. It catches the notifications that no specific session callback already claims.

How it fires
instant, Cloudonix calls Make through a webhook as soon as a session is updated.
When to use it
an operations lead who wants a chat alert when a call of the priority line changes state.
Watch out
a session with its own callback sends its updates there, not to this trigger, so check where your sessions report before blaming Make.
Modules

What can Cloudonix do in a Make scenario?

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

Cloudonix1

[CXML] Connect to Conference

Action

In Make“Start a new conference call, or connect to an existing one. Conference calls are dynamically created.”

Puts the caller into a conference room, creating it on the fly when it does not exist yet. Several callers can meet in the same room without anyone setting it up beforehand.

When to use it
a project team where everyone dials one number and lands in the same call.
Watch out
the room name decides who meets whom, so build it from data you control.
Cloudonix2

[CXML] Connect Voice Agent

Action

In Make“Connect to a remote AI voice agent, using Cloudonix AI connector.”

Hands the live call to a remote AI voice agent through the Cloudonix AI connector, so a bot can talk with the caller. Your scenario decides when the agent takes over.

When to use it
after-hours calls that should still get an answer to common questions.
Watch out
pair it with [CXML] SIP Header when the agent needs extra context about the caller.
Cloudonix3

[CXML] Custom CXML

Action

In Make“Return a custom CXML document, based on the CXML language. Additional information can be obtained at https://dev.docs.cloudonix.io.”

Sends back a CXML document you write yourself, the call-flow language Cloudonix reads. It is the escape hatch when no ready-made CXML module matches the behavior you want.

When to use it
a developer on the team already knows the exact CXML instruction the flow needs.
Watch out
you write the markup yourself, so test it with Run once and a real call before switching the scenario on.
Cloudonix4

[CXML] Gather Input

Action

In Make“Gather input from a connected call, using the phone keypad (DTMF Input Tones). After input is received, transfer call flow to a new application.”

Reads the keys a caller presses on the phone keypad (DTMF tones) and passes the call to a new application with that answer. This is the brick behind any press-one, press-two menu.

When to use it
a clinic line that routes callers to bookings or billing depending on the key pressed.
Watch out
the next application has to exist and be reachable, or the caller hits silence.
Cloudonix5

[CXML] Gather Input (development)

Action

In Make“Gather input from a connected call, using the phone keypad (DTMF Input Tones). After input is received, transfer call flow to a new application.”

A development variant of Gather Input, with the same official description: it collects keypad digits, then transfers the call flow. The directory does not say more about what differs.

When to use it
a copy of your menu scenario kept for trials, away from the one your customers dial.
Watch out
since the documented difference is unknown, keep the regular Gather Input in production.
Cloudonix6

[CXML] Hangup Call

Action

In Make“Hangup the currently connected call.”

Ends the connected call cleanly from inside the flow. It gives your scenario a clear final step instead of leaving the caller waiting on an open line.

When to use it
right after a closing message, once the caller has heard the confirmation they called for.
Watch out
anything placed after it in the same flow never plays, so keep it last.
Cloudonix7

[CXML] Make a call

Action

In Make“Make a call to an external phone number (via a connected carrier trunk), a directly connected subscriber or a conference call.”

Dials out from the current flow to an external number through a connected carrier trunk, to a directly connected subscriber, or into a conference call. The caller stays on the line while it rings.

When to use it
forwarding an incoming customer call to the mobile of the account manager on duty.
Watch out
external numbers need a carrier trunk, and Get Trunks shows which ones you have.
Cloudonix8

[CXML] Pause

Action

In Make“Pause the call for a preset time, then transfer control to a new voice application endpoint.”

Holds the call silent for a preset time, then hands control to a new voice application endpoint. It gives the flow a breath before the next instruction.

When to use it
leaving a short gap after a greeting so the next prompt does not overlap the caller.
Watch out
the call moves to another endpoint afterwards, so point it at an application that exists.
Cloudonix9

[CXML] Play Remote Audio

Action

In Make“Playback a remote audio file (either MP3 or WAV). After the playback, call control can be passed to a new application.”

Plays an MP3 or WAV file stored online into the call, then can pass control to a new application. Recorded voices usually sound warmer than synthetic ones.

When to use it
a studio-recorded welcome message or hold music you already own.
Watch out
the file has to be reachable from the internet, and only those two formats are listed.
Cloudonix10

[CXML] Record a Message

Action

In Make“Record an audio message from the connected call.”

Records what the caller says so the message can be picked up later. It turns a missed call into something your team can actually act on.

When to use it
a voicemail box for a sales line outside opening hours.
Watch out
the Make documentation gives no detail on where the audio ends up, so check it in a Run once before promising callbacks.
Cloudonix11

[CXML] Reject Call

Action

In Make“Reject a call with a specific reason.”

Refuses the incoming call with a specific reason instead of letting it ring into nothing. The caller gets a clear signal right away.

When to use it
a number reserved for known customers, where the scenario turns away callers it does not recognize.
Watch out
a rejected caller hears no message, so prefer Say Something then Hangup Call when politeness matters.
Cloudonix12

[CXML] Say Something (Text-To-Speech)

Action

In Make“Say something using Text-To-Speech, then transfer control to a new voice application endpoint.”

Reads your text aloud to the caller with a synthetic voice, then transfers control to a new voice application endpoint. You can mix fixed words with data from earlier modules.

When to use it
telling a caller the status of their order, read from your shop just before.
Watch out
Get Premium Voices lists the extra voices available if the default one sounds flat.
Cloudonix13

[CXML] SIP Header

Action

In Make“Add a SIP header to `[CXML] Make call` and `[CXML] Connect Voice Agent` modules.”

Adds a SIP header, a label that travels with the call, to [CXML] Make a call and [CXML] Connect Voice Agent. The receiving side learns something about the call before it answers.

When to use it
passing a customer ID to the AI agent so it greets the caller with context.
Watch out
it only works alongside those two modules, not on its own.
Cloudonix14

[CXML] Transfer Control

Action

In Make“Transfer control over the current call to a new voice application URL.”

Moves the current call to another voice application URL, so a different flow takes over. It keeps big call trees split into smaller scenarios you can read.

When to use it
sending callers who chose support to a separate scenario started by the Detached trigger.
Watch out
a wrong URL drops the flow, so test each branch with Run once.
Cloudonix15

[CXML] Voice Application Response

Action

In Make“Render the voice application for processing.”

Renders the voice application so Cloudonix can process it, turning what your scenario built into instructions for the call. Think of it as the reply your flow sends back.

When to use it
at the end of an attached or detached voice application scenario.
Watch out
the documentation does not say which CXML modules require it, so read the Run once output before you publish.
Cloudonix16

Make an API Call

Action

In Make“Performs an arbitrary Cloudonix REST API call. Refer to [Cloudonix REST API](https://developers.cloudonix.com/core-api) for more information.”

Calls any endpoint of the Cloudonix REST API with the connection you already have. Whatever the dedicated modules skip, you can still reach here.

When to use it
an admin task on your Cloudonix domain that no dedicated module offers.
Watch out
you write the request yourself, so keep the Cloudonix API reference open next to it.
Cloudonix17

Make Call and Do Something Smart

Action

In Make“Makes a call to a remote destination or a Cloudonix subscriber, then does something smart with the connected call.”

Starts an outbound call to a remote destination or a Cloudonix subscriber, then acts on the call once it connects. Unlike the CXML dial module, it can start from any event, not only from a call already in progress.

When to use it
ringing a lead back as soon as they fill in a callback form.
Watch out
each call is real, so test with your own number first.
Cloudonix18

Store Session Data

Action

In Make“Store free formed data in the session object. Stored information will be reported in subsequent requests and CDR events.”

Saves free-form data on the call session, and that data comes back in later requests and in the call report. Context gathered early stays with the call.

When to use it
keeping the menu choice of a caller so the final report says why they called.
Watch out
Watch New Call Details Report will carry it, so map it where you store reports.
Cloudonix19

Switch Voice Application

Action

In Make“Switch a currently connected call from its current voice application to a new one.”

Moves a call that is already connected from its current voice application to a new one, from outside the call flow. Another scenario can redirect a live call.

When to use it
a supervisor event elsewhere that should push a waiting caller into a priority flow.
Watch out
inside a flow, [CXML] Transfer Control is the simpler choice.
Cloudonix20

Terminate Active Call

Action

In Make“Terminate (disconnect) a currently active call, identified by a session token.”

Disconnects an active call identified by its session token, from any scenario. You can end calls that are not running through the current flow.

When to use it
closing calls stuck open, found beforehand with Get Active Sessions.
Watch out
a terminated call cannot be resumed, so filter the session tokens carefully before this step.
Cloudonix21

Get Active Sessions

Search

In Make“Get a list of currently connected or new sessions.”

Returns the calls currently connected or just starting, one bundle per session. A bundle is one item that flows from a module to the next.

When to use it
a live count of ongoing calls posted to your team chat on request.
Watch out
a search can return zero, one or many sessions, so the modules after it run once per session.
Cloudonix22

Get Attached Voice Applications

Search

In Make“Get a list of domain attached voice applications.”

Lists the voice applications attached to your domain, the ones visible in the Cloudonix cockpit. You get an inventory without opening the cockpit.

When to use it
checking which call flows exist before pointing a new number or a transfer at one.
Watch out
detached applications live outside the cockpit and are not in this list.
Cloudonix23

Get Premium Voices

Search

In Make“Get a list of supported premium text-to-speech voices.”

Returns the premium text-to-speech voices Cloudonix supports, so you can pick one for Say Something. It saves guessing voice names.

When to use it
choosing a more natural voice before recording a customer-facing message flow.
Watch out
the list comes back as several bundles, so add a filter if you only need one voice.
Cloudonix24

Get Subscribers

Search

In Make“Get a list of domain subscribers.”

Lists the subscribers of your domain, the users or devices registered on Cloudonix. It tells you who can be dialed directly.

When to use it
matching an employee from your HR tool with their Cloudonix subscriber before routing calls to them.
Watch out
every subscriber becomes its own bundle, and each following module costs one operation per subscriber.
Cloudonix25

Get Trunks

Search

In Make“Get a list of domain trunks.”

Returns the trunks of your domain, the carrier links that carry calls to outside numbers. You see which routes exist before dialing.

When to use it
checking a trunk is configured before a [CXML] Make a call step reaches an external number.
Watch out
an empty result means external dialing has no route yet, fix it in Cloudonix first.
Need help

Need help automating Cloudonix with Make?

A person reads every message.

FAQ

Cloudonix and Make: frequent questions

01Is the Cloudonix Make integration free?
Yes, on the Make side. Cloudonix is a standard app, available from the Free plan. That plan allows 2 active scenarios, 15 minutes minimum between scheduled runs, 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and count usage in credits per month. You still need an active Cloudonix account, whose price is not covered here.
02What do you need to connect Cloudonix to Make?
An active Cloudonix account and an API key. In Cloudonix, open API keys management, create a key with a name and note its keyId, a string starting with XI. In Make, add a Cloudonix module, click Create a connection, give it a name if you like and paste the keyId. For an instant trigger, click Create a webhook first, then Create a connection. The same connection then serves every Cloudonix module.
03Do Cloudonix triggers in Make react in real time?
Yes. All 4 Cloudonix triggers are instant: Cloudonix calls Make through a webhook as soon as something happens, whether a call report, a voice application request or a session update. There is no polling interval to set, unlike scheduled triggers that Make checks every 15 minutes by default. That matters here, since a voice application request has to be answered while the caller is still on the line, and a call report is most useful when it lands in your log right after the call ends.
04What if a Cloudonix module is missing in Make?
Use Make an API Call. It sends any request to the Cloudonix REST API through the connection you already set up, so an action outside the 29 modules stays reachable. Keep the API reference from Cloudonix open while you build it. Also note that the Cloudonix documentation for Make is marked as AI-generated and may contain errors, so confirm important details with Cloudonix before a scenario goes live on a real phone line.
05Should you use Make or n8n for Cloudonix?
It depends on the tool your team already uses. On Make, Cloudonix comes with 29 ready modules, 4 of them instant triggers, and runs from the Free plan. The same app often has an n8n node too, so check whether it exists before you choose. Compare the modules each side offers for your call flows, then pick the tool your team is comfortable maintaining. Neither is ranked above the other here.
Same platform

Other docs you might need on this stack.

Browse all integrations