Resources · Make integration

Runo Call Management CRM Make integrationAutomate Runo Call Management CRM with Make.

Can Make push work into your Runo account without anyone typing it in? The Runo Call Management CRM Make integration gives you 2 action modules, one to create an allocation and one to call the Runo API directly. This guide is for sales and ops teams, and it walks you from connection to a live scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Runo Call Management CRM Make integration do?

The Runo Call Management CRM Make integration lets a Make scenario, the automation you build as a chain of bricks called modules, write into your Runo account for you. Runo has no trigger in Make, so something else starts the flow: another app, or a schedule you set on the first module.

Allocations created from your lead sources. A web form or an ad platform collects a new prospect, and the next module, Create an Allocation, records it in Runo. Each item that travels between modules is called a bundle, and each bundle handled by a module costs one operation on your Make plan.

Everything the listed modules leave out. Make an API Call reuses the same connection to reach any endpoint of the Runo API. It is the route to take when a need goes beyond creating an allocation.

A clear view of the limits. The official Make documentation for this app is short: it flags that not enough public information exists to describe it in full, and it lists no required fields or quotas. Test each module with real data before relying on it, and keep Make troubleshooting close by when a run fails.

New to the editor? The Make training covers the basics, and the n8n vs Make comparison helps if you are still choosing a platform.

Connect

How do you connect Runo Call Management CRM to Make?

  1. 01

    Add a Runo module

    In your scenario, add Create an Allocation or Make an API Call, then click Create a connection. A connection is your Runo account linked to Make once and reused by every Runo module afterwards.

  2. 02

    Name the connection

    Giving it a name is optional, but a label such as the team or the account owner saves guessing later, especially when several Runo accounts end up linked to the same Make organization.

  3. 03

    Authorize and save

    Depending on what Make asks for, approve access on the Runo page that opens or paste the key Runo gives you. Then click Save and the module is ready to fill in.

First scenario

Build your first scenario with Runo Call Management CRM

GoalWhen a new lead lands in another app, Make creates an allocation in Runo Call Management CRM.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Pick the app where your leads arrive, since Runo has no trigger of its own.

  2. 02

    Add Create an Allocation

    Click the + on the right of that first module, search for Runo Call Management CRM and choose Create an Allocation. Select your connection or create one.

  3. 03

    Map the lead data

    Fill the module fields by mapping values from the previous module. Once the connection exists, Make lists what it can read from Runo, so you pick instead of typing.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Then read the bundles each module received and check that the allocation appears in Runo.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. From there, each new lead follows the same path without a manual step.

Modules

What can Runo Call Management CRM do in Make?

Runo Call Management CRM gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Runo Call Management CRM1

Create an Allocation

ActionIn the docs only

This action adds a new allocation to your Runo account from data another module sends it, so records stop being typed in by hand.

When to use it
place it right after the module that receives new contacts, such as a form or a lead ad, and map their details into it.
Watch out
the Make documentation describes none of its fields, so run it once with a test record and check the result in Runo first.
Runo Call Management CRM2

Make an API Call

ActionIn the docs only

With this module you reach any endpoint of the Runo API while keeping the connection you already set up, which covers whatever Create an Allocation cannot do.

When to use it
choose it as soon as your need goes beyond creating an allocation, since it is the only other Runo module in Make.
Watch out
you build the request yourself, with no form to guide you, so test it with Run once before the scenario goes live.
Need help

Need help automating Runo Call Management CRM with Make?

A person reads every message.

FAQ

Runo Call Management CRM and Make: common questions

01Is the Runo Call Management CRM Make integration free?
Yes, on the Make side. Runo Call Management CRM is a standard app, so it is available from the Free plan, which gives you 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 and lift the limit on active scenarios. Whatever Runo itself charges is a separate matter: this answer only covers the Make side.
02What do you need to connect Runo Call Management CRM to Make?
An active Runo account and a Make account are enough to start. The Make documentation gives no specific prerequisite for this app. You add one of its modules, click Create a connection, optionally name it, then either approve access on the Runo page or paste the key Runo provides, and save. The connection is then shared by both Runo modules, so you only do this once per account, and every new scenario can pick it from the list.
03Can a Runo Call Management CRM scenario start on its own in Make?
Not from Runo itself, because the app has no trigger module in Make, neither scheduled nor instant. The scenario has to start elsewhere. The usual choice is a trigger from another app, such as the tool that collects your leads, placed before Create an Allocation. You can also rely on the schedule of the first module, which runs every 15 minutes by default on a new scenario and never faster than 15 minutes on the Free plan.
04What if the Runo Call Management CRM Make integration is missing a module?
Use Make an API Call. It sends a request to any endpoint of the Runo API through the connection you already have, which is the way to cover anything that Create an Allocation does not handle. Keep in mind that the Make documentation for this app is limited and says so openly, so there is no list of fields or limits to lean on. Test every call with Run once before switching the scenario on.
05Should you use Make or n8n with Runo Call Management CRM?
It depends on the platform your team already works in. On Make, this app offers 2 modules, Create an Allocation and Make an API Call, both usable from the Free plan. The same app often has a node in n8n too, so check what is available there before deciding. The criteria that matter are the actions you need, the editor your team is comfortable with, and whether one connection can cover every step of your flow.