Resources · Make integration

RocketReach Make integrationAutomate RocketReach with Make.

Can a finished RocketReach lookup start the rest of your prospecting on its own? The RocketReach Make integration gives you 4 modules: one instant trigger, two actions and one search. This guide is for sales and growth teams, and it walks you from the API key to a working scenario.

Try the RocketReach integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the RocketReach Make integration do for you?

The RocketReach Make integration links your RocketReach account to Make, a visual tool where you build a scenario: the automation itself, a chain of modules that runs on a schedule or when an app calls Make. Each module is one brick, such as a trigger, an action or a search, and RocketReach brings four of them.

Widen one contact into a team. When a lookup finishes, Watch Lookups hands the result to Make, and Search Profiles looks for more people who match your criteria. One name found by a rep becomes a short list of colleagues to approach.

Enrich leads that arrive elsewhere. A form, a spreadsheet or a CRM can pass a LinkedIn URL, a profile ID or a company to Lookup a Profile. The profile comes back into the scenario, ready for the next module.

Reach what the menu does not show. Make an API Call reuses the same connection to call any endpoint of the RocketReach API, which keeps you inside one scenario when no ready module fits.

What Make does not do for you: it does not create the RocketReach account or the API key, and the official Make documentation for this app is marked as AI-generated, so check important details with RocketReach itself. The same app often has an n8n node too; the n8n vs Make page lays out the criteria, the Make review covers the tool as a whole, and Make troubleshooting helps when a run fails.

Connect

How do you connect RocketReach to Make?

  1. 01

    Generate your API key

    Log in to RocketReach, open the Account page and go to API Usage and Settings. If no key is there yet, click Generate New API Key, then copy the key shown on screen. You need an active RocketReach account for this.

  2. 02

    Add a RocketReach module

    In your Make scenario, add any RocketReach module and click Create a connection. A connection is your RocketReach account linked to Make once, then reused by every RocketReach module. The Connection name field is optional; a clear name helps later.

  3. 03

    Paste the key and save

    Enter the API key you copied, or follow the instructions Make shows on screen, and confirm. Make can now read your RocketReach data, and the connection appears in the list the next time you add a module from this app.

First scenario

Build your first scenario with RocketReach

GoalWhen a lookup finishes in RocketReach, Make searches for more matching profiles so one contact turns into a short list.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big + to place the first module. The canvas stays empty until you choose an app.

  2. 02

    Place the Watch Lookups trigger

    Search for RocketReach, pick Watch Lookups, click Create a webhook, then Create a connection and paste your API key. This module starts the scenario each time a lookup completes.

  3. 03

    Add Search Profiles

    Click the + on the right of the trigger and add Search Profiles. Map data from the finished lookup into its criteria so the search stays close to the person you just found.

  4. 04

    Test with Run once

    Click Run once, then run a lookup in RocketReach. Each module shows the bundles it received; a bundle is one item passed along, here one profile. Zero results from the search is a normal answer.

  5. 05

    Switch it on

    Turn the scenario on. Because the trigger is instant, RocketReach calls Make as soon as a lookup finishes, with no polling clock to wait for. Every module run counts as an operation on your plan.

Triggers

What starts a RocketReach scenario?

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

RocketReach1Watch Lookups

Watch Lookups

Instant trigger

In Make“Triggers when a lookup has been completed.”

Watch Lookups gives you the result of a RocketReach lookup the moment it is done, so the profile a rep just found can move on to the next step without anyone copying it by hand. It is the only trigger this app offers.

How it fires
instant: RocketReach calls Make through a webhook as soon as the lookup completes, which is why the module shows a lightning badge rather than a clock.
When to use it
your team already runs lookups inside RocketReach and you want each finished one to feed a search, a sheet or a CRM.
Watch out
create the webhook before the connection, otherwise the module never receives anything.
Modules

What can RocketReach do inside a scenario?

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

RocketReach1

Lookup a Profile

Action

In Make“Looks for a profile of the specified profile ID, linkedin URL or company.”

Hand this module a profile ID, a LinkedIn URL or a company, and it returns the matching RocketReach profile into your scenario, ready to map into the modules that follow.

When to use it
a lead lands in a form or a sheet with only a LinkedIn URL, and you want the full profile before anyone writes to them.
Watch out
it targets one known profile; to explore several people, pick Search Profiles instead.
RocketReach2

Make an API Call

Action

In Make“Performs an arbitary authorized API call.”

This one lets you reach any endpoint of the RocketReach API while keeping the connection you already set up, so no second key or login is needed.

When to use it
the RocketReach feature you need has no ready module in Make, and you would rather stay in the same scenario than switch tools.
Watch out
you write the request yourself, so keep the RocketReach API documentation open while you fill it in.
RocketReach3

Search Profiles

Search

In Make“Searches for profiles based on the specified criterias.”

Search Profiles brings back every RocketReach profile that matches the criteria you set, one bundle per person, so the next module can handle each one in turn.

When to use it
you know the kind of person you are after rather than a precise name, for instance more contacts close to someone a lookup just found.
Watch out
a search can return zero, one or many results, and each result costs an operation in the modules after it.
Need help

Need help automating RocketReach with Make?

A person reads every message.

FAQ

RocketReach and Make: common questions

01Is the RocketReach Make integration free?
Yes on the Make side: RocketReach is a standard app, so it works from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs and 5 minutes of execution per run. Paid plans go down to 1 minute between runs and remove the cap on active scenarios. You still need an active RocketReach account with an API key, and its subscription is set by RocketReach on its own pricing page, not by Make.
02What is needed to connect RocketReach to Make?
An active RocketReach account and an API key. In RocketReach, open the Account page, go to API Usage and Settings, click Generate New API Key if none exists, and copy it. In Make, add a RocketReach module, click Create a connection, give it a name if you like and paste the key. For the Watch Lookups trigger, click Create a webhook first. The connection is then shared by every RocketReach module in your scenarios.
03Does the RocketReach trigger in Make work in real time?
Yes. Watch Lookups is an instant trigger: RocketReach calls Make through a webhook as soon as a lookup completes, so the scenario starts right away instead of waiting for a polling interval. This is also why the module carries a lightning badge in the editor. The other three RocketReach modules are actions or a search, so they only run when something earlier in the scenario reaches them, whether that is this trigger or a module from another app.
04What if a RocketReach module is missing in Make?
Use Make an API Call. It calls any endpoint of the RocketReach API with the connection you already have, so a feature without its own module is still within reach from the same scenario. You write the request yourself, which means reading the RocketReach API documentation. Keep in mind that the Make documentation for this app is flagged as AI-generated and may contain mistakes, so confirm anything important with RocketReach directly before relying on it.
05Should RocketReach be automated with Make or n8n?
It depends on the tool your team already works in. Make offers 4 RocketReach modules, including an instant trigger on finished lookups, and a visual editor where you test with Run once. Apps found in Make often have an n8n node as well, so check whether RocketReach does before choosing. Neither tool is ranked above the other here: the comparison page linked in the section above sets out the criteria side by side so you can match them to your own setup.
Same platform

Other docs you might need on this stack.

Browse all integrations