Resources · Make integration

ReachInbox Make integrationAutomate ReachInbox with Make.

Can Make keep your ReachInbox campaigns fed without importing leads by hand? The ReachInbox Make integration gives you 1 instant trigger and 3 lead actions. This guide is for sales and growth teams and takes you from the connection to a first working scenario.

Try the ReachInbox integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the ReachInbox Make integration do for you?

The ReachInbox Make integration links your ReachInbox account to Make, a no-code tool where you build a scenario, meaning an automation made of chained modules. ReachInbox can alert Make the moment an event happens in your account, and Make can add, update or remove leads in your campaigns without you opening ReachInbox.

Fill a campaign from your CRM. A new contact lands in your CRM or in a spreadsheet, and the Add Lead module drops it into the right ReachInbox campaign. The Airtable Make integration covers the source side if your prospects live in a base.

Keep lead data current. A record gets corrected in the tool your team treats as the reference, and Update Lead rewrites that lead inside its campaign so the next email uses the right information.

Stop writing to people who should leave the sequence. When a prospect becomes a customer or asks to be left alone through another channel, Remove Lead takes them out of the campaign. On the other side, Watch Events starts your own flow whenever ReachInbox reports an event.

Make's documentation for ReachInbox is flagged as limited: it lists neither the event types, nor the fields, nor any connection prerequisite. Test each module with Run once before relying on it, and keep the Make troubleshooting guide nearby. ReachInbox may also have an n8n node; the n8n vs Make comparison lays out the criteria for choosing.

Connect

How do you connect ReachInbox to Make?

  1. 01

    Add a ReachInbox module

    Open your scenario, click the +, search for ReachInbox and pick any of its modules. In the module panel, click Create a connection. A connection is your ReachInbox account linked to Make once, then reused by every ReachInbox module.

  2. 02

    Name it and authorize Make

    Give the connection a name you will recognize later, such as the workspace it belongs to; this part is optional. Then authorize Make on the ReachInbox page that opens, or paste the key ReachInbox gives you, depending on what the window asks for.

  3. 03

    Save and test

    Click Save. Make returns to the module, and the new connection now sits in its dropdown. Select it, fill the module, and click Run once to confirm Make can reach your account before you build anything bigger.

First scenario

Your first scenario: send new CRM contacts to a ReachInbox campaign

GoalWhen a new contact shows up in another app, Make adds it as a lead to your ReachInbox campaign.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Pick the app where your contacts start, a CRM or a spreadsheet, and choose its module that watches for new records.

  2. 02

    Connect the source app

    Click Create a connection for that app and fill its fields. Once the connection exists, Make lists the sheets or objects it can read, so you pick yours from a list instead of typing it.

  3. 03

    Add the ReachInbox action

    Click the + on the right of the first module, search for ReachInbox and choose Add Lead. Connect your account, choose the campaign the lead should join, then map the contact details from the first module.

  4. 04

    Test with Run once

    Add a test contact in your source app, then click Run once. Open each module to read the bundles it received: a bundle is one item, here one contact, handed from a module to the next.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module; a new scenario checks every 15 minutes by default. Then switch the scenario on. Each module run on one bundle counts as one operation on your Make plan.

Triggers

What starts a ReachInbox scenario?

1 module starts a scenario when something happens in ReachInbox. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by ReachInbox as soon as it happens.

ReachInbox1Watch Events

Watch Events

Instant trigger

In Make“Triggers when new events occur.”

Watch Events lets ReachInbox tell Make that something happened in your account, so your scenario starts right away instead of waiting for a scheduled check. Each event arrives as one bundle that the following modules can read and reuse.

How it fires
instant: ReachInbox calls Make through a webhook as soon as it happens, which is why the module carries the lightning badge.
When to use it
push campaign activity into your CRM, a sheet or a team chat the moment ReachInbox records it.
Watch out
Make's documentation does not list which event types this trigger sends, so run the scenario once with a real event and read the bundle before mapping anything.
Modules

What can Make do in ReachInbox?

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

ReachInbox1

Add Lead

Action

In Make“Add lead to campaign”

Add Lead puts a contact into one of your ReachInbox campaigns, so a prospect captured elsewhere starts receiving your sequence without a manual import.

When to use it
a form submission, a new CRM contact or a row added to a prospect sheet should join outreach right away.
Watch out
test with Run once and check the lead in ReachInbox, since the documentation says nothing about how duplicates are handled.
ReachInbox2

Remove Lead

Action

In Make“Remove Lead from Campaign”

With Remove Lead, a contact leaves a campaign and stops getting its next emails, which keeps you from writing to someone who has already signed or declined.

When to use it
a deal moves to won in your CRM, or a prospect asks through another channel to be left alone.
Watch out
the module acts on the campaign only; the contact stays in your source tool, so clean it there separately if needed.
ReachInbox3

Update Lead

Action

In Make“Update lead of a campaign”

Update Lead corrects a lead that already sits in a campaign, so the next personalized emails go out with the fixed information instead of the old record.

When to use it
your CRM is the reference and a contact changes there after the lead was added to ReachInbox.
Watch out
the documentation lists none of the lead fields, so connect first, open the module and check which details Make offers before mapping your CRM data.
Need help

Need help automating ReachInbox with Make?

A person reads every message.

FAQ

ReachInbox and Make: common questions

01Is the ReachInbox Make integration free?
Yes. ReachInbox is a standard app in Make, available from the Free plan. That plan allows 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) bring the interval down to 1 minute, lift the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one per module run on one bundle. Your ReachInbox subscription is billed separately and is not covered by Make.
02What do you need to connect ReachInbox to Make?
A ReachInbox account and a Make account; Make's documentation lists no other prerequisite. Add any ReachInbox module, click Create a connection, name it if you like, then authorize Make on the ReachInbox page or paste the key the app provides, and click Save. The connection is created once and reused by every ReachInbox module in your scenarios. Since the official help page is flagged as limited, test the connection right away with Run once so an access problem shows up before you build the full flow.
03Does the ReachInbox trigger in Make fire instantly?
Yes. Watch Events is an instant trigger: ReachInbox calls Make through a webhook as soon as an event happens, so the scenario does not wait for a schedule. It is the only trigger in the app. The other three modules, Add Lead, Update Lead and Remove Lead, are actions: they run when an earlier step hands them a bundle, such as a trigger from your CRM or a scheduled start. Scheduled starts run every 15 minutes by default and can go down to 1 minute on paid plans.
04What if the ReachInbox module you need is missing in Make?
It depends on the step you are missing. The app has four modules: one instant trigger and three actions on campaign leads. There is no Make an API Call module for ReachInbox, so this integration cannot reach other parts of the ReachInbox API. If your process needs more than adding, updating or removing leads, check whether another app in your stack can handle that step, or ask the team for help designing the scenario. The documentation is limited, so test every module with Run once before going live.
05Should you use Make or n8n for ReachInbox?
It depends on the tool your team already runs. On Make, ReachInbox offers 1 instant trigger and 3 actions to add, update and remove campaign leads, all available from the Free plan. ReachInbox may also have an n8n node, so check which operations it covers before deciding. Compare both options on the exact modules your process needs and on where your other automations already live. Neither choice is ranked here: the right one is the tool that covers your steps with the least rebuilding.
Same platform

Other docs you might need on this stack.

Browse all integrations