Resources · Make integration

HeyReach Make integrationAutomate HeyReach with Make.

What if every LinkedIn reply, accepted invite or finished campaign in HeyReach moved your pipeline on its own? The HeyReach Make integration offers 35 modules, 11 of them instant triggers. This guide connects your account and walks you through a first scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the HeyReach Make integration do for your outreach?

The HeyReach Make integration links your HeyReach account to Make so that campaign events start automations, called scenarios, without code. A scenario is a chain of modules, and each module is one brick: a trigger that listens, an action that changes something, or a search that fetches records. Here you get 35 of them for campaigns, messages, senders, lists and leads.

Replies that reach the right rep. Watch Message Reply Received fires on the first answer to a campaign message. Follow it with Get Conversation to read the thread, then send the context wherever your sales team works.

Accepted invites that feed a list. Watch Connection Request Accepted tells Make who said yes, and Add Lead To List files that person in a HeyReach list you prepared with Create Empty List. The first scenario below builds exactly this.

Campaigns that report themselves. When Watch Campaign Completed fires, Get Overall Stats pulls the numbers for the filters you set, ready for a recap message or a spreadsheet.

What the integration does not include: HeyReach has no Make an API Call module in Make, so anything outside these 35 modules needs another route, and the doc gives no numeric limit to plan around. Each module run on one item counts as one operation on your Make plan, which our Make pricing page breaks down.

Weighing another tool? The n8n vs Make comparison lays out the criteria, and the Make training covers the editor from the first module to the switch-on.

Connect

How do you connect HeyReach to Make?

  1. 01

    Create an API key in HeyReach

    Log in to HeyReach, click Integrations in the left sidebar, find the Make section and click Connect now. Then click New API key and copy the value somewhere safe: Make needs it in the next step.

  2. 02

    Open a connection from a HeyReach module

    In your Make scenario, add any HeyReach module and click Create a connection. A connection is your HeyReach account linked to Make once, then reused by every HeyReach module. The Connection name field is optional but helps when you run several accounts.

  3. 03

    Paste the key and save

    Paste the key into the Make API Key field and click Save. If HeyReach asks you to authenticate and confirm access, accept. From then on, Make can read your campaigns, lists and leads in the module fields.

First scenario

Your first HeyReach scenario: accepted invites land in a list

GoalWhen a LinkedIn contact accepts a connection request sent by a HeyReach campaign, Make adds that lead to a HeyReach list you picked.

  1. 01

    Create the scenario

    Open the Scenarios page in Make, create a new scenario and click the + to add the first module.

  2. 02

    Add the trigger

    Search HeyReach, pick Watch Connection Request Accepted, click Create a webhook and then Create a connection with your API key. The lightning badge shows the trigger is instant.

  3. 03

    Add the list action

    Click the + on the right of the trigger and choose Add Lead To List. Pick the target list, then map the lead data the trigger passes along. Each accepted invite travels as one bundle, meaning one item.

  4. 04

    Test with Run once

    Click Run once, let a connection request get accepted in a live campaign, then read the bundles each module received.

  5. 05

    Switch it on

    When the test looks right, switch the scenario on. There is no schedule to tune here: the instant trigger starts it. Every accepted invite now lands in your list without a manual export.

Triggers

Which HeyReach events can start a scenario?

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

HeyReach1Watch Campaign Completed

Watch Campaign Completed

Instant trigger

In MakeThis event notifies you when a HeyReach campaign has been completed.

The end of a HeyReach campaign becomes a starting point: the moment a campaign completes, your scenario receives it and can hand off to the next step without anyone watching the dashboard.

How it fires
instant. HeyReach calls Make through a webhook as soon as the campaign is completed.
When to use it
a finished campaign should produce a recap for sales, so chain it with Get Overall Stats and post the result where the team reads it.
Watch out
the setup starts with Create a webhook, then Create a connection, like every HeyReach trigger.
HeyReach2Watch Message Reply Received

Watch Message Reply Received

Instant trigger

In MakeThis webhook is activated when you receive the first reply to a LinkedIn message as part of a HeyReach campaign.

A prospect answering your LinkedIn message is the signal sales waits for, and this trigger passes it to Make on the first reply inside a HeyReach campaign. The reply shows up in your other tools instead of sitting in an inbox.

How it fires
instant. HeyReach notifies Make through a webhook as soon as that first reply arrives.
When to use it
alert the rep who owns the account, or fetch the whole thread with Get Conversation before you do.
Watch out
the doc speaks of the first reply only, so do not build on it for every later message in the thread.
HeyReach3Watch Message Sent

Watch Message Sent

Instant trigger

In MakeThis event occurs when you send a LinkedIn message through a HeyReach campaign. Connection request messages are not tracked by this event.

Every LinkedIn message a HeyReach campaign sends can turn into a record elsewhere, which gives you an outreach log that lives outside HeyReach and that the rest of the company can read.

How it fires
instant. HeyReach calls Make through a webhook each time a campaign message goes out.
When to use it
you want the contact history in your CRM or a spreadsheet to show what was sent and when.
Watch out
connection request messages are not tracked by this event. Pair it with Watch Connection Request Sent to cover them.
HeyReach4Watch InMail Sent

Watch InMail Sent

Instant trigger

In MakeThis event is triggered when you send a LinkedIn InMail message through a HeyReach campaign.

InMails deserve their own track, and this trigger gives it to you: each InMail a HeyReach campaign sends reaches Make, separate from regular messages, so you can count and file them apart.

How it fires
instant. HeyReach calls Make through a webhook as soon as the InMail is sent.
When to use it
your team treats InMail outreach differently from standard messages and wants its own log or its own follow-up rule.
Watch out
regular LinkedIn messages go through Watch Message Sent instead, so plan both triggers if you need a complete history.
HeyReach5Watch InMail Reply Received

Watch InMail Reply Received

Instant trigger

In MakeThis event notifies you when you receive the first reply to a LinkedIn InMail message that is part of a HeyReach campaign.

When someone answers an InMail sent by a HeyReach campaign, Make hears about it and can route that warm lead right away, instead of leaving it for the next inbox review.

How it fires
instant. HeyReach sends the event to Make through a webhook as soon as the first InMail reply comes in.
When to use it
InMail replies go to a senior rep or a dedicated channel, and you want the handoff to happen on the reply itself.
Watch out
like its message counterpart, it covers the first reply, not the rest of the exchange.
HeyReach6Watch Connection Request Sent

Watch Connection Request Sent

Instant trigger

In MakeThis event notifies you when a connection request has been sent to a LinkedIn account through a HeyReach campaign.

Knowing who just received an invite lets you prepare the next touch before they even answer. This trigger reports each connection request a HeyReach campaign sends to a LinkedIn account.

How it fires
instant. HeyReach calls Make through a webhook as soon as the request leaves.
When to use it
mark the contact as invited in your CRM, or fill the gap that Watch Message Sent leaves, since that trigger ignores connection request messages.
Watch out
a busy campaign sends many invites, and each one costs operations on your Make plan.
HeyReach7Watch Connection Request Accepted

Watch Connection Request Accepted

Instant trigger

In MakeThis event is triggered when a LinkedIn account accepts your connection request as part of a HeyReach campaign.

An accepted invite is often the first real yes of a LinkedIn campaign, and this trigger delivers it to Make the moment the contact accepts your request as part of a HeyReach campaign.

How it fires
instant. HeyReach calls Make through a webhook as soon as the acceptance happens.
When to use it
move the person into a follow-up list with Add Lead To List, as in the first scenario above, or create a deal in your CRM.
Watch out
the doc ties this event to HeyReach campaigns, so expect nothing from an invite accepted outside one.
HeyReach8Watch Follow Sent

Watch Follow Sent

Instant trigger

In MakeThis event occurs when you start following a LinkedIn profile through a HeyReach campaign.

Following a profile is a soft first touch, and this trigger lets you record it: each time a HeyReach campaign starts following a LinkedIn profile, Make gets the event.

How it fires
instant. HeyReach notifies Make through a webhook as soon as the follow is done.
When to use it
your sequence warms up prospects before messaging them, and you want each warm-up step visible in a shared sheet or CRM timeline.
Watch out
soft touches add up quickly, so filter in Make if only some campaigns matter to you.
HeyReach9Watch Liked Post

Watch Liked Post

Instant trigger

In MakeThis webhook event is sent when a you have liked a LinkedIn Profile’s post as part of a HeyReach campaign.

Engagement steps usually stay invisible outside HeyReach. This trigger surfaces them: whenever a campaign likes a post from a LinkedIn profile, Make receives the event and can log it next to the contact.

How it fires
instant. HeyReach calls Make through a webhook as soon as the like is placed.
When to use it
a rep wants to see, before a call, which prospects already saw some attention from the campaign.
Watch out
the event covers likes placed by your campaign, not likes your prospects give to your own posts.
HeyReach10Watch Viewed Profile

Watch Viewed Profile

Instant trigger

In MakeThis event is sent when you view a LinkedIn profile as part of a HeyReach campaign.

A profile visit is the lightest step of a campaign, yet it tells you the sequence has started for that person. This trigger reports each LinkedIn profile a HeyReach campaign views.

How it fires
instant. HeyReach calls Make through a webhook as soon as the view happens.
When to use it
you track the full journey of a lead, from first view to reply, in one table outside HeyReach.
Watch out
views tend to be the most frequent event of a campaign, so check the operations they consume before you switch it on for every campaign.
HeyReach11Watch Lead Tag Updated

Watch Lead Tag Updated

Instant trigger

In MakeThis event occurs when you add or remove tags from a contact in HeyReach.

Tags are how many teams sort leads in HeyReach, and this trigger turns each tag change into an automation: adding or removing a tag on a contact sends the event to Make.

How it fires
instant. HeyReach calls Make through a webhook as soon as the tag is added or removed.
When to use it
a tag such as hot lead should create a task in your CRM, or a removed tag should clear a flag somewhere else.
Watch out
both additions and removals fire it, so add a filter after the trigger to keep only the change you care about.
Modules

What can each HeyReach module do in Make?

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

Campaigns

7 modules
HeyReach1

Get Campaigns

Search

In MakeGet a list of campaigns in your HeyReach account based on pre-defined filters

This search returns the campaigns of your HeyReach account that match the filters you set, one bundle per campaign, so later modules can act on each of them.

When to use it
you want to pause or report on a whole group of campaigns without typing their IDs.
Watch out
a search can return zero, one or many campaigns; plan for the empty case.
HeyReach2

Get Campaign by ID

Action

In MakeIt will return the data of the campaign by the Campaign ID

Hand it a campaign ID and it brings back that campaign's data, which is handy when a trigger or a sheet only gives you the ID and you need the full picture.

When to use it
right after Watch Campaign Completed, to enrich the recap with the campaign details before posting it.
HeyReach3

Resume Campaign

Action

In MakeResume paused campaign

A paused campaign starts again with this action, so restarting outreach can depend on an event in another tool rather than on someone remembering to click in HeyReach.

When to use it
a campaign was paused while a list got cleaned, and the cleanup scenario should restart it once done.
Watch out
it only applies to a campaign that is paused.
HeyReach4

Pause Campaign

Action

In MakePause active campaign

Stopping an active campaign from Make gives you an emergency brake that other tools can pull, without logging in to HeyReach.

When to use it
a deal closes in your CRM with the account a campaign targets, and outreach to that company should stop at once.
Watch out
pausing affects the whole campaign; to stop one person only, Stop Lead In Campaign is the finer tool.
HeyReach5

Add Lead To Campaign

Action

In MakeAdding a lead in a HeyReach campaign

This action places a lead into a HeyReach campaign, so prospects coming from a form, a CRM view or a spreadsheet enter your outreach without a CSV import.

When to use it
a new sign-up on your site should receive the LinkedIn sequence that fits their profile.
Watch out
check first with Get Campaigns For A Lead if the person might already be in a campaign.
HeyReach6

Stop Lead In Campaign

Action

In MakeStops the campaign for the provided lead

Where Pause Campaign halts everyone, this action stops the campaign for one lead only, and the rest of the sequence keeps running for everyone else.

When to use it
a prospect books a meeting through your calendar tool, and the automated messages to that person should end right there.
Watch out
the lead you pass must be the one enrolled in that campaign.
HeyReach7

Get Leads for a Lead

ActionIn the docs only

The HeyReach doc lists this Campaigns module without describing what it returns, so treat it as something to explore in the editor before you rely on it in a live scenario.

When to use it
only after a Run once shows you the bundles it produces for your account.
Watch out
with no official description, prefer Get Lead Details or Get Leads From Campaign for anything documented.

Messages

5 modules
HeyReach8

Get Conversations

Search

In MakeGet a collection of LinkedIn conversations.

This search pulls a collection of LinkedIn conversations from HeyReach, each one arriving as a separate bundle you can filter, archive or summarize.

When to use it
you want to copy conversation threads into a shared space where managers review outreach quality.
Watch out
a large collection means many bundles, and every module after it runs once per conversation.
HeyReach9

Get Conversation

Action

In MakeGet a LinkedIn conversation with its messages by Id.

One LinkedIn conversation comes back with its messages when you give this module the conversation ID, so a rep can see the full exchange instead of a single reply.

When to use it
just after Watch Message Reply Received, to attach the whole thread to the alert sent to sales.
HeyReach10

Send Message

Action

In MakeSend a message to a LinkedIn conversation

This action writes into an existing LinkedIn conversation through HeyReach, which lets another tool trigger a reply without anyone opening LinkedIn.

When to use it
a prospect fills your booking form, and a short thank-you should land in the conversation they already have with your sender.
Watch out
it targets a conversation, so find it first with Get Conversations.
HeyReach11

Get Sender Accounts

Action

In MakeGet a list of sender accounts connected to HeyReach

You get the list of LinkedIn sender accounts connected to HeyReach, which helps when several profiles run outreach and a scenario needs to act on each of them.

When to use it
building a report per sender, or checking which accounts exist before you pick one in another module.
HeyReach12

Get Sender By ID

Action

In MakeGet a sender LinkedIn account by id

Pass a sender ID and this module returns that single LinkedIn sender account, useful when an event names the sender only by its ID and you want readable details.

When to use it
a reply alert should show which teammate's profile the conversation belongs to.

Lists

8 modules
HeyReach13

Get List By ID

Action

In MakeGet list details by ID

This action returns the details of one HeyReach list from its ID, a quick way to check a list before a scenario writes into it or reports on it.

When to use it
confirming the name of the list a lead just joined, so the message to your team reads clearly.
HeyReach14

Get Lists

Search

In MakeGet lead lists in your HeyReach account based on pre-defined filters

All the lead lists that match your filters come back from this search, one bundle each, so you can loop over your lists instead of naming them one by one.

When to use it
building an overview sheet of every list in the account.
Watch out
zero results is a normal answer for a search; add a filter if the next step needs a list.
HeyReach15

Get Leads From List

Search

In MakeRetrieves leads in a certain lead list

This search retrieves the leads stored in one HeyReach list, each lead becoming a bundle that the next modules can sync, enrich or move.

When to use it
copying a prospect list into your CRM or a spreadsheet so the rest of the company sees who is being contacted.
Watch out
every lead returned runs the following modules once, which counts on your operations.
HeyReach16

Delete Lead From List

Action

In MakeDeletes a lead from a list based on ID

This action removes a lead from a list based on its ID, keeping lists clean when a contact becomes a customer or asks not to be contacted.

When to use it
a deal marked won in your CRM should pull the person out of the prospect list.
Watch out
a deletion cannot be undone from Make, so test with Run once on a test lead first.
HeyReach17

Get Companies From List

Search

In MakeGet a paginated collection of companies from a company list.

Company lists get their own search: this module returns the companies stored in a HeyReach company list, page by page, as separate bundles.

When to use it
your account-based outreach targets companies, and you want that target list mirrored in your CRM.
Watch out
it reads company lists, not lead lists; for people, use Get Leads From List.
HeyReach18

Add Lead To List

Action

In MakeAdds a lead to a lead list

This action files a lead into a HeyReach lead list, turning lists into living segments that fill themselves from events rather than from imports.

When to use it
every accepted connection request should join a follow-up list, as the first scenario on this page shows.
Watch out
the list must exist first; Create Empty List can prepare it.
HeyReach19

Get Lists For A Lead

Search

In MakeGet the lists associated with a specific lead.

Starting from one lead, this search tells you which HeyReach lists contain that person, so you know where they sit before you change anything.

When to use it
a contact asks to be forgotten, and you need every list to clean before running Delete Lead From List.
Watch out
several lists mean several bundles to handle.
HeyReach20

Create Empty List

Action

In MakeCreate an empty lead or company list.

A new, empty lead or company list appears in HeyReach when this action runs, ready for Add Lead To List to fill it.

When to use it
a new event or trade show should get its own list, created when the event is added to your planning tool.
Watch out
placed in a scenario that runs often, it creates a list on every run; keep it for one-off events.

Leads

1 module
HeyReach21

Get Lead Details

Action

In MakeThis module retrieves the details of a specific lead based on their LinkedIn profile URL.

Give this module a LinkedIn profile URL and it returns what HeyReach knows about that lead, the fastest way to enrich a record that only holds a profile link.

When to use it
a form or a CRM entry contains the LinkedIn URL, and you want the lead data before deciding which campaign fits.
Watch out
it looks leads up by profile URL, so a name alone is not enough.

Stats

1 module
HeyReach22

Get Overall Stats

Action

In MakeGets the overall stats for the specified filters

This action returns the overall HeyReach statistics for the filters you choose, so reporting can leave the HeyReach dashboard and reach the tools your managers already open.

When to use it
after Watch Campaign Completed, to post the campaign results in a team channel or a spreadsheet.
Watch out
the filters decide what the numbers cover; name them clearly in your report.

Other modules

2 modules
HeyReach23

Get Campaigns For A Lead

Search

In MakeRetrieves the list of campaigns where the specified lead is.

This search lists the campaigns where a given lead is enrolled, a quick check that prevents contacting the same person from two sequences at once.

When to use it
before Add Lead To Campaign, or when a prospect replies and you want to stop every campaign they belong to.
Watch out
zero results simply means the lead is in no campaign.
HeyReach24

Get Leads From Campaign

Search

In MakeRetrieves a list of leads in a certain campaign

Every lead enrolled in one campaign comes back from this search as a separate bundle, which gives you the campaign audience outside HeyReach.

When to use it
handing the audience of a finished campaign to your CRM, right after Watch Campaign Completed fires.
Watch out
a large campaign returns many bundles, and each following module counts one operation per lead.
Need help

Need help automating HeyReach with Make?

A person reads every message.

FAQ

HeyReach and Make: common questions

01Is the HeyReach Make integration free?
Yes, on the Make side. HeyReach is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 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, Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and count usage in credits each month. You still need your own HeyReach account, since the integration connects to it with an API key.
02What do you need to connect HeyReach to Make?
A HeyReach account and an API key. In HeyReach, open Integrations in the left sidebar, find the Make section, click Connect now, then New API key, and copy the value. In Make, add a HeyReach module, click Create a connection, paste the key into the Make API Key field and click Save. If HeyReach asks you to authenticate and confirm access, accept. For a trigger, click Create a webhook first and create the connection inside it.
03Do HeyReach triggers in Make fire in real time?
Yes. All 11 HeyReach triggers are instant: HeyReach calls Make through a webhook as soon as the event happens, whether that is a reply, an accepted invite, a tag change or a completed campaign. They do not wait for the 15-minute default schedule that applies to scheduled triggers. The setup order matters: on each trigger, click Create a webhook, then Create a connection. In practice, a reply reaches your CRM or your team channel while the conversation is still fresh.
04What if a HeyReach module is missing in Make?
It depends on the gap. HeyReach has no Make an API Call module in Make, so you cannot reach an endpoint that the 35 modules do not cover. Start by combining modules: a search such as Get Lists For A Lead followed by an action often covers the need. The doc gives no numeric limit for the app. If the job still needs something missing, route it through another app of your stack, or ask the team for help on the design.
05Make or n8n for HeyReach automations?
It depends on what you need to run. On Make, HeyReach brings 35 modules, including 11 instant triggers for replies, invites, tags and campaign events, and the app is open from the Free plan. If you also consider n8n, check what its HeyReach support covers against the events and actions listed on this page. Compare the two on the criteria that matter to your team, such as the modules you need and how you prefer to build, rather than on a general ranking.