Resources · Make integration

Revox Make integrationAutomate Revox with Make.

Can Make place a Revox call when a new contact shows up elsewhere? Yes: the Revox Make integration gives you 4 action modules and no trigger. This guide is for teams who already use Revox, and it walks you through the connection, a first scenario and each module.

Try the Revox integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Revox Make integration do for you?

The Revox Make integration links your Revox account to Make, the no-code tool where you build a scenario, meaning the automation itself, out of modules, the bricks that each do one job. Revox brings 4 action modules to Make, so another app or a schedule starts the flow and Revox does the calling part.

Calls that start on their own. Pair a form or a spreadsheet with Start call: each new entry becomes a call request, with no copy and paste between tools.

Call details where your team works. Get call info fetches what Revox knows about a given call so a later module can write it into your CRM or a shared sheet.

Everything else through the API. Make an API call reuses your Revox connection to reach any endpoint of the Revox API that the listed modules leave out.

Keep the limits in mind. Revox has no trigger in Make, so a scenario never wakes up because something happened inside Revox; it starts from another app or from the schedule. Make also flags its Revox documentation as AI-generated, so check important details with Revox directly. If you are weighing tools, the n8n vs Make comparison lays out both, and Make pricing explains how operations are counted. Want a hand building it? See Make agency.

Connect

How do you connect Revox to Make?

  1. 01

    Copy your API key

    In your Revox account, open the dashboard, go to the API Keys section and copy the key shown on screen. You need an active Revox account for this; the plan you pick is set on the Revox side.

  2. 02

    Add a Revox module

    In your Make scenario, add any Revox module, for example Start call, then click Create a connection. The connection is your Revox account linked to Make once, and every Revox module reuses it.

  3. 03

    Paste the key and save

    Give the connection a name in the Connection name field if you like; it is optional but handy with several accounts. Paste the API key you copied, or follow the on-screen instructions, and save.

First scenario

Your first scenario with Revox

GoalWhen a new lead lands in another app, Make asks Revox to start a call for it.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Pick the app that holds your leads, such as a form or a spreadsheet, and its trigger for new entries.

  2. 02

    Add Start call

    Click the + to the right of that first module, search for Revox and choose Start call. Select your Revox connection, or click Create a connection if this is your first Revox module.

  3. 03

    Map the lead data

    Fill the fields of Start call by mapping data from the first module: each new lead reaches Revox as a bundle, one item carrying that lead's details. Make shows what it can read once the connection works.

  4. 04

    Test with Run once

    Add a test lead in your source app, then click Run once. Make runs the scenario one time and shows the bundles each module received, so you can see whether Revox accepted the request.

  5. 05

    Schedule and switch on

    Open the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. Each module run on a bundle counts as one operation on your Make plan.

Modules

What each Revox module does

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

Revox1

Get call info

ActionIn the docs only

You get the details Revox holds about one call, ready to pass to the next module, for example to update a CRM record or a report sheet.

When to use it
after a call has run, when your team wants its outcome stored next to the contact instead of looking it up in Revox.
Watch out
the module acts on a single call, so feed it the call you mean; Make publishes no description for this module, so look at the fields the editor shows once connected.
Revox2

Make an API call

ActionIn the docs only

This one opens the whole Revox API to your scenario, with the same connection as the other modules, so you are not stuck when the ready-made modules stop short.

When to use it
when you need an endpoint that none of the other three Revox modules covers.
Watch out
you write the request yourself, so keep the Revox API reference open and try each request with Run once before switching the scenario on.
Revox3

On call finished

ActionIn the docs only

The name points to the end of a call, but Make gives it no description, so what it expects and returns is unknown. It is listed with the actions, so it runs when your scenario reaches it and does not start the scenario itself.

When to use it
in a flow already started by another app or the schedule, for a step tied to a finished call.
Watch out
open it in the editor and read its fields, then test it with Run once before relying on it.
Revox4

Start call

ActionIn the docs only

Your scenario asks Revox to begin a call, which turns a new lead, a booking or a form entry into a call request without anyone dialing by hand.

When to use it
right after the module that brings in the contact, as the step that actually reaches out.
Watch out
every bundle that reaches this module starts a call, so filter the flow first and test with a single test contact before activation.
Need help

Need help automating Revox with Make?

A person reads every message.

FAQ

Revox and Make: common questions

01Is the Revox Make integration free?
Yes, on the Make side. Revox is a standard app, so it works from the Make Free plan, which allows 2 active scenarios, a minimum of 15 minutes 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) drop the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes per run. Usage is counted in operations per month. Your Revox subscription is separate and set on the Revox pricing page.
02What do you need to connect Revox to Make?
An active Revox account and its API key. In Revox, open the dashboard, go to the API Keys section and copy the key. In Make, add any Revox module, click Create a connection, optionally name it in the Connection name field, paste the key and save. That connection is then reused by all 4 Revox modules, so you only set it up once per account. If it fails, copy the key again from the dashboard and create a new connection.
03Does Revox trigger Make scenarios in real time?
No. Revox has no trigger module in Make, neither scheduled nor instant, so nothing in Revox can start a scenario by itself. You start the flow another way: with the trigger of another app, such as a new form entry or a new spreadsheet row, or with the schedule on the first module, every 15 minutes by default and down to 1 minute on paid plans. The Revox modules then run as actions further down the scenario.
04What if a Revox module you need is missing in Make?
Use the Make an API call module. It reuses your Revox connection and can reach any endpoint of the Revox API, which covers what Start call, Get call info and On call finished do not. Test each request with Run once first. Also note that Make labels its Revox documentation as AI-generated and possibly wrong in places, so confirm important behavior with Revox directly before building a scenario that depends on it.
05Should you use Make or n8n for Revox?
It depends on the tool your team already knows. On Make, Revox gives you 4 action modules, including Make an API call, and a connection based on an API key, and every scenario starts from another app or from the schedule. The same app often has an n8n node as well, so check whether one exists for Revox and compare the modules each tool offers for your use case. Pick the editor where your other automations already live, which keeps them in one place.
Same platform

Other docs you might need on this stack.

Browse all integrations