Resources · Make integration

Romulus Make integrationAutomate Romulus with Make.

What if every finished Romulus call could trigger the next step by itself? The Romulus Make integration gives you 9 modules: 6 scheduled triggers and 3 actions. Below, you link your account, build a first scenario and learn which module fits which job.

Try the Romulus integration on MakeSee the 9 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Romulus Make integration do for you?

The Romulus Make integration plugs your Romulus account into Make, a no-code tool where you assemble a scenario (the automation itself) from modules, small bricks that each do one job. Six modules watch what happens to your calls and robocalls. Three act: they create a robocall task, send a WhatsApp template message or reach the Romulus API directly.

Follow up a call on WhatsApp. Watch Call Completed picks up each finished call, and Send a WhatsApp Template Message sends the approved follow-up without anyone copying a number by hand.

Launch robocalls from the tool where the list lives. A new row in a spreadsheet or a new deal in your CRM, handled by that other app's module, feeds Create a Robocall Task. Your campaign starts from the data your team already keeps up to date.

Put robocall results where people read them. Watch New Robocall Results hands each result to the next module, which can post it to a team channel or update a record in another app.

Know the limits before you build. Make's documentation for Romulus is short: it names the modules but describes none of them, so read the bundles after a test run before mapping anything. When a listed module does not cover your case, Make an API Call reaches the rest of the Romulus API with the same connection. If a scenario stalls, the Make troubleshooting guide walks through the usual causes, and the Make training covers the editor from scratch. Still choosing a tool? The n8n vs Make comparison lays out the criteria side by side.

Connect

How do you connect Romulus to Make?

  1. 01

    Add a Romulus module

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

  2. 02

    Name the connection

    This step is optional, but a clear name such as Romulus sales team saves time later, when several accounts or several people share the same Make organization and you must pick the right one from a list.

  3. 03

    Authorize Make and save

    Depending on what Romulus offers, either approve access on the Romulus page that opens, or paste the key Romulus gives you into the field. Click Save and the connection appears in the module.

First scenario

Your first scenario: a WhatsApp follow-up after each call

GoalWhen a call is completed in Romulus, Make sends a WhatsApp template message.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario. An empty canvas opens with a large + in the middle: click it to place the first module, the one that starts everything.

  2. 02

    Set the trigger

    Search for Romulus and choose Watch Call Completed. Click Create a connection, link your account and save. This trigger is scheduled: Make checks Romulus on the scenario's schedule.

  3. 03

    Add the WhatsApp action

    Click the + to the right of the trigger and choose Send a WhatsApp Template Message. Fill its fields, mapping values from the completed call wherever the module asks for them.

  4. 04

    Test with Run once

    Finish a test call in Romulus, then click Run once. A bubble appears above each module: open it to read the bundle it received and check the message went out as planned.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A new scenario runs every 15 minutes by default, the minimum on the Free plan; paid plans go down to 1 minute. Then switch the scenario on.

Triggers

Which Romulus triggers start a scenario?

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

Romulus1Watch Agent Call Action Completed

Watch Agent Call Action Completed

triggerIn the docs only

Reacting to each step inside an agent call, not just to the call as a whole, is what this trigger is for: its name points to actions completed during an agent call, each one reaching Make as a bundle, one item handed to the next module.

How it fires
scheduled: Make checks the app on the scenario's schedule, so an action completed between two checks waits for the next one.
When to use it
when a single step of the call, not its end, should set off the follow-up.
Watch out
no official description exists, so check the first bundles with Run once before building on them.
Romulus2Watch Agent Call Action Type Completed

Watch Agent Call Action Type Completed

triggerIn the docs only

You get a scenario that ignores the noise and wakes up only for one kind of action. Compared with Watch Agent Call Action Completed, the extra word Type in its name suggests you narrow it to a single action type within agent calls.

How it fires
scheduled: Make checks the app on the scenario's schedule, every 15 minutes on a new scenario.
When to use it
when only one action type deserves a follow-up and the others would just burn operations, the executions Make counts on your plan.
Watch out
the documentation lists no settings, so confirm in the module itself how the type is chosen.
Romulus3Watch Agent Call Completed

Watch Agent Call Completed

triggerIn the docs only

After an agent call ends, this trigger picks it up at the next check and hands it to your scenario, so the next step runs without anyone reopening Romulus. It sits one level above the action triggers: the whole call, not its individual steps.

How it fires
scheduled: Make polls Romulus at the rhythm set on the scenario's clock, never faster than your plan allows.
When to use it
for a recap after each agent call, such as a note in your CRM or a message to the account owner.
Watch out
since the docs describe nothing, run it once after a real agent call to see what the bundle holds.
Romulus4Watch Call Action Type Completed

Watch Call Action Type Completed

triggerIn the docs only

Here the filter works on calls in general rather than agent calls: going by its name, the trigger passes along completed actions of one chosen type, one bundle each, and skips the rest.

How it fires
scheduled: Make asks Romulus for new items each time the scenario's schedule comes around.
When to use it
when a precise outcome in a call, and nothing else, should feed another tool, for example a sales pipeline.
Watch out
the word Agent is missing from this name, which is the clue that separates it from the agent version; if your calls go through agents, test both and compare the bundles.
Romulus5Watch Call Completed

Watch Call Completed

triggerIn the docs only

The simplest way in: every completed call becomes a bundle that the rest of your scenario can use. It is the trigger of the first scenario on this page, and a sensible default when you are unsure which of the six to pick.

How it fires
scheduled: Make looks for completed calls on the scenario's schedule, 15 minutes by default on a new scenario.
When to use it
to log each call elsewhere or send a follow-up once it ends.
Watch out
one scenario run can return several calls at once, and each one costs its own operations in the modules that follow.
Romulus6Watch New Robocall Results

Watch New Robocall Results

triggerIn the docs only

Robocalls are automated calls, and this trigger closes the loop on them: each new result lands in your scenario, ready to be stored, shared or acted on. It pairs naturally with Create a Robocall Task, which starts the campaign on the other end.

How it fires
scheduled: Make fetches new results on the scenario's schedule rather than the moment they appear.
When to use it
when results must reach a spreadsheet, a CRM or a team channel without a manual export.
Watch out
the documentation says nothing about the content of a result, so read one bundle before mapping its values.
Modules

What can Romulus do inside a scenario?

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

Romulus1

Create a Robocall Task

ActionIn the docs only

Your robocalls start from data that already lives elsewhere: this action creates a robocall task in Romulus from whatever the previous module passes along.

When to use it
when a new contact list, form entry or sheet row should launch a campaign without anyone opening Romulus.
Watch out
each bundle creates its own task, so filter the incoming items first if only some of them should be called.
Romulus2

Make an API Call

ActionIn the docs only

This module is your way past the list: it calls any endpoint of the Romulus API from the scenario, reusing the connection you already created.

When to use it
when the other 8 modules do not cover what you need, for instance a request none of the triggers or actions handles.
Watch out
you write the request yourself, so you need the Romulus API reference at hand; Make does not supply it here.
Romulus3

Send a WhatsApp Template Message

ActionIn the docs only

A contact receives a ready-made WhatsApp message sent through Romulus, triggered by an event instead of a person typing it.

When to use it
right after a completed call or a robocall result, to confirm an appointment or share the next step while the exchange is fresh.
Watch out
the name says template, not free text, so check in the module which templates your Romulus account offers before you plan the wording.
Need help

Need help automating Romulus with Make?

A person reads every message.

FAQ

Romulus and Make: common questions

01Is the Romulus Make integration free?
Yes. Romulus is a standard app in Make, so its 9 modules work on the Free plan. That plan has limits: 2 active scenarios, at least 15 minutes between two 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) lift the number of active scenarios, allow runs every minute and count usage in credits per month. You still need your own Romulus account.
02What do you need to connect Romulus to Make?
A Romulus account and a Make account are enough to start, since the documentation lists no other prerequisite. Add any Romulus module, click Create a connection, give it a name if you want, then either authorize Make on the Romulus page or paste the key Romulus provides, and click Save. That single connection then serves all 9 modules, including Make an API Call, so you only go through these steps once per account.
03How quickly do Romulus triggers react in Make?
On the scenario's schedule, not the instant something happens. All 6 Romulus triggers are scheduled: Make checks Romulus each time the clock on the first module comes around. A new scenario uses every 15 minutes by default, which is also the shortest interval on the Free plan. Paid plans let you go down to 1 minute. Romulus has no instant trigger in Make, so if speed matters, shorten the schedule rather than looking for a webhook.
04What if the Romulus module you need is missing in Make?
Use Make an API Call. It is one of the 9 Romulus modules and lets a scenario call any endpoint of the Romulus API with the connection you already set up, so you are not stuck with the 3 listed actions. Keep in mind that Make's documentation for Romulus is limited and describes none of the modules, so for this module you will need the Romulus API reference to know which request to send.
05Should you pick Make or n8n for Romulus?
It depends on what you need to build. In Make, Romulus comes with 9 ready-made modules: 6 scheduled triggers, 2 actions for robocalls and WhatsApp, plus Make an API Call for everything else. The same app often has an n8n node too, but this page has no detail on one for Romulus, so check the n8n catalog before deciding. Compare the modules each tool offers for your exact case, not the brand.
Same platform

Other docs you might need on this stack.

Browse all integrations