Resources · Make integration

RevReply Make integrationAutomate RevReply with Make.

Can Make sort and answer your RevReply replies for you? The RevReply Make integration gives you 6 modules, 5 actions and 1 search, with no trigger. This guide is for sales teams: connect the account, build a first scenario and learn when each module fits.

Try the RevReply integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the RevReply Make integration do for you?

The RevReply Make integration links your RevReply account to Make, a tool where you build a scenario (an automation made of bricks called modules) without writing code. Its 6 modules act on replies, threads and inbox managers from inside that scenario, but none of them can start it on its own.

Replies sorted before anyone reads them. A module from another app brings a reply into the scenario, then Classify Response puts it in a category, going by the module's name. That category can decide what happens next.

A draft answer waiting for review. Generate Response, as its name says, produces an answer you can pass to the next module. Pause Thread fits the moment a conversation should stop moving, for example when a prospect asks to talk later.

A clear view of your inbox managers. List Inbox Managers is the only search module: it can return zero, one or several bundles (a bundle is one item passed from a module to the next). Create Inbox Manager adds a new one.

What Make does not give you here is documentation. Make itself says it lacks public information about RevReply, so field names are learned in the editor. Many apps also exist as an n8n node; the n8n vs Make comparison helps you pick, while the Make review and the Make training cover the basics.

Connect

How do you connect RevReply to Make?

  1. 01

    Add a RevReply module

    Open your scenario, click the + and search for RevReply. Pick any of its modules, for instance Generate Response. The connection (your RevReply account linked to Make once) is created from this first module and reused by the other five.

  2. 02

    Create the connection

    Click Create a connection. Naming it is optional, though it helps when you manage several RevReply accounts. Then, depending on what the window asks for, authorize Make on the RevReply page that opens or paste the key RevReply gives you.

  3. 03

    Save and check it

    Click Save. Back in the module, Make can now read what your account holds. If the fields offer choices, the connection works; if they stay empty, delete it and create it again from the same button.

First scenario

Your first scenario with RevReply

GoalWhen a reply reaches your other tool, Make classifies it with RevReply and prepares an answer.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. RevReply has no trigger, so the first module comes from the app where your replies arrive.

  2. 02

    Add Classify Response

    Click the + on the right of that first module, search for RevReply and pick Classify Response. Create the connection if this is your first RevReply module, then map data from the previous module into its fields.

  3. 03

    Chain Generate Response

    Add Generate Response with the + on the right; the connection is already there. The documentation does not list its fields, so read what the editor offers and fill them with outputs from the two modules before it.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario one time and shows the bundles each module received. Open the output of Classify Response: it is the only place you will see what RevReply actually sends back.

  5. 05

    Schedule and switch it on

    On the first module, open the clock: every 15 minutes by default, down to 1 minute on a paid plan. Then switch the scenario on. Each module run on one bundle counts as one operation on your plan.

Modules

What each RevReply module does

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

RevReply1

Classify Response

ActionIn the docs only

You get a category for each reply, which lets the rest of the scenario treat an interested answer differently from a refusal. That is what the name Classify Response announces; this guide knows nothing more about how it sorts.

When to use it
right after the module that brings the reply in, before you split the flow.
Watch out
the possible categories are not documented, so read them in the bundle of a test before you build a filter on them.
RevReply2

Create Inbox Manager

ActionIn the docs only

This module adds a new inbox manager to your RevReply account straight from a scenario, going by its name, so nobody has to set it up by hand. Make does not say which settings it accepts.

When to use it
when a new sales rep joins and another app already holds their details.
Watch out
every run creates one more manager, so test it with Run once on a single bundle before you switch the scenario on.
RevReply3

Generate Response

ActionIn the docs only

What comes out of Generate Response, as its name promises, is an answer to a reply, ready to hand to the next module for review or sending. Placed after Classify Response, it can build on the category found.

When to use it
when a reply calls for an answer and you would rather start from a draft than a blank page.
Watch out
Make does not describe what it returns, so check the text in the bundle before any module mails it to a prospect.
RevReply4

List Inbox Managers

SearchIn the docs only

List Inbox Managers brings back the managers set up in your RevReply account, one bundle each. As the app's single search module, it can also come back with nothing at all.

When to use it
before Create Inbox Manager, to see whether the manager you need already exists.
Watch out
with several bundles, every module placed after it runs once per manager, and each of those runs counts as an operation.
RevReply5

Makes an API call

ActionIn the docs only

RevReply lists an action called Makes an API call which, judging by its name, opens the parts of RevReply the other five modules leave out. This guide has no field list or example to give you for it.

When to use it
only when none of the named modules does what you need and you know what RevReply expects on its side.
Watch out
this is not Make's universal API module, and nothing in the documentation explains how to fill it in.
RevReply6

Pause Thread

ActionIn the docs only

A conversation that stops moving forward is what the name Pause Thread describes, handy so a prospect who asked for time is not chased by the next message. It acts on one thread per bundle.

When to use it
after Classify Response, when the category says the person wants to wait.
Watch out
Make does not document how a paused thread resumes, so check that in RevReply before you pause many at once.
Need help

Need help automating RevReply with Make?

A person reads every message.

FAQ

RevReply and Make: common questions

01Is the RevReply Make integration free?
Yes. RevReply is a standard app in Make, so its modules are available from the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution at most, 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 allow 40 minutes per run. Make counts usage in operations, one per module per bundle. Your RevReply subscription is a separate matter.
02What do you need to connect RevReply to Make?
A RevReply account and a Make account; the documentation mentions no other prerequisite. It gives no app-specific connection steps either, so the generic flow applies: add a RevReply module, click Create a connection, name it if you like, authorize Make on the RevReply page or paste the key RevReply provides, then click Save. All 6 modules share that connection afterwards. If the window asks for an access you do not have, ask RevReply what your account includes, because the documentation cannot tell you.
03Does RevReply have a real-time trigger in Make?
No. RevReply has no trigger at all, neither scheduled nor instant, so it cannot start a scenario by itself. There are two ways around it. Open the scenario with a module from another app, ideally an instant trigger, which that app calls through a webhook as soon as something happens. Or let the scenario run on its schedule: the clock on the first module is set to every 15 minutes by default, and a paid plan allows intervals down to 1 minute. RevReply's modules then act on whatever that first module passes along.
04What if a RevReply module is missing in Make?
It depends on what you need. RevReply does not have Make's universal Make an API Call module, the usual fallback when a module is missing. The app does list its own action called Makes an API call, but Make documents neither its fields nor its behavior, and Make admits that public information on RevReply is thin. If the 6 modules do not cover your case, look for another app that can handle that step, or ask the team to look at the scenario with you.
05Make or n8n for RevReply?
It depends on where your other automations already live. In Make, RevReply brings 6 modules on every plan, Free included, and the editor shows after Run once what each module received, which helps with an app this lightly documented. Many apps also have an n8n node, so check whether RevReply is one of them before you decide. Neither tool is ranked here: pick the one your team already uses, so replies, contacts and follow-ups stay in the same scenarios. The comparison linked above walks through the criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations