Resources · Make integration

Reply.io Make integrationAutomate Reply.io with Make.

Can a new lead land in the right Reply.io campaign without anyone copying it over? The Reply.io Make integration offers 10 modules: 2 triggers, 7 actions and 1 search. This guide is for sales and growth teams, and it walks you from the connection to a first working scenario.

Try the Reply.io integration on MakeSee the 10 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Reply.io Make integration do for your outreach?

The Reply.io Make integration links your Reply.io account to Make, a visual tool where you build a scenario: an automation made of modules, each one a trigger, an action or a search. Make can react to what happens in Reply.io and write contacts back into it, without any code.

Feed campaigns from your other tools. A lead arrives in a form, a spreadsheet or a CRM, and Create a Contact and Push It to Campaign adds that person to Reply.io and enrolls them in the campaign you picked. Nobody retypes an email address.

Act on replies and clicks. Watch Events tells Make when someone replies, opens an email, clicks a link or opts out. From there, a scenario can alert the account owner, update a row in a sheet or move the deal forward in your CRM.

Keep contact data clean. Get a Contact, Update a Contact and Delete a Contact all find a person by email address, so a change made elsewhere can be mirrored in Reply.io. List Contacts pulls the full list when you need an audit.

The listed modules cover contacts, events and call tasks. For anything else in Reply.io, Make an API Call reaches the rest of the API with the same connection. The Reply.io documentation on Make lists no specific limit; if a run fails, the Make troubleshooting guide is the place to start. Wondering which plan fits? Read Make pricing. And if you are still choosing a platform, n8n vs Make sets out the criteria side by side.

Connect

How do you connect Reply.io to Make?

  1. 01

    Add a Reply.io module

    Log in to Make, open your scenario and add any Reply.io module. In the module settings, click Create a connection. A connection is your Reply.io account linked to Make once, then reused by every Reply.io module.

  2. 02

    Name the connection

    The Connection name field is optional, but a clear name helps when several people or several Reply.io accounts share the same Make organization. Something like the team or the inbox it belongs to is enough.

  3. 03

    Paste your API key

    You need an active Reply.io account and an API key. Enter the credentials you copied from your Reply.io account, or follow the on-screen instructions, then save. Make can now read and write your Reply.io contacts.

First scenario

Your first scenario: send new leads straight into a Reply.io campaign

GoalWhen a new lead shows up in another app, Make adds it to Reply.io and pushes it into your campaign.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. This first module is where your leads come from: a form, a sheet or a CRM.

  2. 02

    Pick the lead source

    Search the app that holds your leads, choose its trigger module and connect the account. Make then lists the forms, sheets or objects it can read, so you only select the right one.

  3. 03

    Add the Reply.io action

    Click the + on the right of the first module, search Reply.io and choose Create a Contact and Push It to Campaign. Create the connection if it is your first Reply.io module.

  4. 04

    Map the lead

    Pick the campaign, then map the email address and the name from the previous module into the Reply.io fields. Each lead travels as a bundle, one item passed from one module to the next.

  5. 05

    Test with Run once

    Click Run once and add a test lead in the source app. Read the bundles each module received, then check the contact inside Reply.io.

  6. 06

    Schedule and switch on

    Set the schedule on the first module; a new scenario checks every 15 minutes by default. Switch the scenario on, and every new lead joins the campaign without a manual export.

Triggers

What starts a Reply.io scenario?

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

Reply.io1Watch Call Tasks

Watch Call Tasks

Scheduled trigger

In Make“Runs when a new call task is created by AI SDR”

Watch Call Tasks hands you each new call task that the Reply.io AI SDR creates, so a rep can see it where they already work instead of opening another tab.

How it fires
this is a scheduled trigger, meaning Make checks Reply.io on the scenario's schedule and collects the call tasks created since the last check.
When to use it
your reps live in a CRM or a chat tool and you want every task the AI SDR opens to show up there as a to-do.
Watch out
several tasks can come in at the same check, so plan the next module to handle several bundles.
Reply.io2Watch Events

Watch Events

Instant trigger

In Make“Triggers when a new event happens in Reply, such as email reply, email open, email sent, link click, opt-out, sequence finished, call made, or email account disconnected.”

Watch Events starts your scenario the moment something happens in Reply.io: an email reply, an open, a sent email, a link click, an opt-out, a finished sequence, a call made or a disconnected email account.

How it fires
this is an instant trigger; Reply.io calls Make through a webhook as soon as the event occurs.
When to use it
alert the account owner when a prospect replies, or stop outreach in other tools when someone opts out.
Watch out
it covers many event types at once, so decide which ones the next modules should act on before you map any data.
Modules

What can Make do in Reply.io?

Reply.io gives you 8 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Reply.io1

Create a Contact

Action

In Make“Creates a new contact.”

Create a Contact adds a person to your Reply.io contact base, ready to be picked for a campaign later by you or your team.

When to use it
you want new leads stored in Reply.io first and reviewed by a human before anyone gets enrolled in outreach.
Watch out
this module only creates the contact; if the goal is to start a campaign right away, the next module does both steps.
Reply.io2

Create a Contact and Push It to Campaign

Action

In Make“Creates and pushes a contact to the selected campaign.”

This module creates the contact and enrolls it in the campaign you select, in a single step and a single operation, the unit Make counts on your plan.

When to use it
a demo request or a webinar sign-up should trigger a follow-up sequence without anyone touching Reply.io.
Watch out
the contact enters the sequence straight away. Test with Run once on your own address before switching on.
Reply.io3

Delete a Contact

Action

In Make“Deletes a contact specified by email address.”

Delete a Contact removes a person from Reply.io, found by their email address, so your base stops holding people who asked to leave.

When to use it
a deletion request is logged in your CRM or support tool and must be reflected in your outreach platform too.
Watch out
a deletion cannot be undone from Make; test it with Run once on a dummy address before switching the scenario on.
Reply.io4

Get a Contact

Action

In Make“Retrieves details of a contact specified by the email address.”

Get a Contact fetches the details Reply.io holds on one person, identified by email address, and passes them to the modules that follow.

When to use it
after a reply event, you want the full contact record to enrich a CRM entry or write a useful Slack alert.
Watch out
it reads a single contact by email; to go through many contacts at once, List Contacts is the better choice.
Reply.io5

Make an API Call

Action

In Make“Performs an arbitrary API call.”

Make an API Call lets you reach any endpoint of the Reply.io API from your scenario, reusing the connection you already created, so no second login is needed.

When to use it
you need something the other modules do not cover, such as data outside contacts, events and call tasks.
Watch out
you write the request yourself, so keep the Reply.io API documentation open next to the module while you set it up.
Reply.io6

Mark Contact as Replied

Action

In Make“Marks a selected contact as replied.”

Mark Contact as Replied flags a chosen contact as having answered, so Reply.io knows the conversation has started.

When to use it
the prospect answered outside Reply.io, by phone, on LinkedIn or through a form, and your team logs it in another tool.
Watch out
pair it with a trigger from that other tool, not with Watch Events, which already sees email replies sent inside Reply.io.
Reply.io7

Update a Contact

Action

In Make“Updates a contact specified by email address.”

Update a Contact changes the details of an existing person in Reply.io, found by email address, so outreach uses current information.

When to use it
a job title, a company or a phone number changes in your CRM and should follow into Reply.io.
Watch out
the email address is the key; if it changed in the source, the module will not find the old contact, so look it up first.
Reply.io8

List Contacts

Search

In Make“Retrieves a list of all contacts.”

List Contacts returns every contact in your Reply.io account, one bundle per person, which lets you review or export the whole base in one run.

When to use it
you need a full export to a sheet, or a cleanup pass that compares Reply.io with your CRM.
Watch out
each contact becomes its own bundle, so every module placed after it runs once per contact and counts operations accordingly.
Need help

Need help automating Reply.io with Make?

A person reads every message.

FAQ

Reply.io and Make: common questions

01Is the Reply.io Make integration free?
Yes, on the Make side. Reply.io is a standard app, so its modules work from the Free plan onward. That plan allows 2 active scenarios, runs no more often than every 15 minutes, stops a run after 5 minutes, handles files up to 5 MB and includes 512 MB of data transfer. Paid plans lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes per run. Usage is counted in credits, meaning operations, per month. You still need your own active Reply.io account.
02What do you need to connect Reply.io to Make?
You need an active Reply.io account and an API key. In Make, add any Reply.io module, click Create a connection, optionally give it a name, then enter the credentials copied from your Reply.io account or follow the on-screen instructions. If the first module is Watch Events, the instant trigger, click Create a webhook before Create a connection. After that, every Reply.io module in your scenarios reuses the same connection, so you only do this once per account.
03Does the Reply.io trigger in Make react instantly?
It depends on the trigger. Watch Events is instant: Reply.io calls Make through a webhook as soon as a reply, an open, a click, an opt-out or another listed event occurs, so the scenario starts right away. Watch Call Tasks is scheduled: Make checks Reply.io on the scenario's schedule, every 15 minutes by default, and down to 1 minute on paid plans. Pick Watch Events when speed matters, for example to alert a rep about a reply, and Watch Call Tasks for the tasks created by the AI SDR.
04What if a Reply.io module is missing in Make?
Use Make an API Call. The listed modules cover contacts, events and call tasks, and this module reaches any other endpoint of the Reply.io API with the connection you already have, so there is nothing new to authorize. You write the request yourself, with the Reply.io API documentation at hand. The Make documentation for Reply.io lists no specific limit, and it notes that its content is generated from the vendor documentation, so check important details with Reply.io directly.
05Should you use Make or n8n for Reply.io?
It depends on your criteria. On Make, Reply.io comes with 10 native modules, including an instant trigger for replies and clicks and a Make an API Call module for the rest of the API, and every scenario is built visually in the editor. The same app often exists on n8n as well, so check that its node covers the actions you need. Compare the two on what matters to your team: the tool you already use, the modules available and how you want to maintain your automations.
Same platform

Other docs you might need on this stack.

Browse all integrations