Resources · Make integration

SalesBlink Make integrationAutomate SalesBlink with Make.

Every open, click and reply in your cold emails can start work somewhere else. The SalesBlink Make integration gives you 3 triggers and 2 actions. This page walks sales teams through the connection, a first scenario and each module.

Try the SalesBlink integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the SalesBlink Make integration do?

The SalesBlink Make integration links your SalesBlink account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that watches or acts in one app. SalesBlink tells Make when a prospect opens an email, clicks a link or replies, and Make can add a lead to one of your lists.

Sort interested prospects without reading reports. Watch New Link Click spots the people who clicked in your email, and Add a Lead to a List drops them into a separate SalesBlink list, so your follow-up goes to readers who showed intent.

Hand replies to the right person. Watch New Reply Received picks up answers to your cold emails. From there, the scenario can pass each reply to another app your team already reads, such as a chat tool or a CRM, so nobody has to watch the inbox.

Keep a trace of opens. Watch New Email Open collects every open so you can log it in a spreadsheet or score the lead elsewhere.

Know the limits before you start. There are only 5 modules, no search module and no instant trigger: all three triggers are scheduled, so Make checks SalesBlink on the scenario's schedule rather than hearing from it the moment something happens. When you need an endpoint the list does not cover, Make an API Call reaches the SalesBlink API with the same connection. The SalesBlink documentation on the Make side is also flagged as AI-generated, so double-check anything important with SalesBlink.

Still choosing a platform? Read our n8n vs Make comparison, check Make pricing, or follow the Make training to get comfortable in the editor.

Connect

How do you connect SalesBlink to Make?

  1. 01

    Get your API key in SalesBlink

    You need an active SalesBlink account. Log in, open the Account Settings section, register a new API key and copy it somewhere safe. Make will ask for it in a moment.

  2. 02

    Open the connection window in Make

    In your scenario, add any SalesBlink module and click Create a connection. A connection is your SalesBlink account linked to Make once, then reused by every SalesBlink module you add later.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when you run several accounts. Paste the API key you copied from SalesBlink, save, and Make confirms the link.

First scenario

Your first scenario: move clickers to a hot list

GoalWhen a prospect clicks a link in a SalesBlink email, Make adds that lead to a SalesBlink list for warmer follow-up.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to add the first module. The first module is the trigger, the one that starts everything.

  2. 02

    Add the click trigger

    Search for SalesBlink, pick Watch New Link Click and pick the connection you created, or click Create a connection if this is your first SalesBlink module.

  3. 03

    Add the list action

    Click the + on the right of the trigger and choose Add a Lead to a List. Pick the target list, then map the lead's details from the click bundle, the item the trigger passes along.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received, so you can check that the right lead reached the right list.

  5. 05

    Schedule it and switch it on

    Open the clock on the first module. A new scenario checks every 15 minutes by default, which is also the shortest interval on the Free plan. Save, then switch the scenario on.

Triggers

SalesBlink triggers in Make

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

SalesBlink1Watch New Email Open

Watch New Email Open

Scheduled trigger

In Make“Triggers when an email is opened.”

Brings the opens of your SalesBlink emails into your scenario, each one as a bundle you can store, count or forward to another tool.

How it fires
scheduled. Make checks SalesBlink on the scenario's schedule and collects the opens found since the last check.
When to use it
you want a log of who reads your emails, for example a row per open in a spreadsheet your manager can filter.
Watch out
an open is a weak signal, so every run can bring a lot of bundles, and each module that handles one uses an operation on your plan.
SalesBlink2Watch New Link Click

Watch New Link Click

Scheduled trigger

In Make“Triggers when a link in email is clicked.”

Gives you the prospects who went one step further and clicked a link inside your email, which is often the clearest sign of interest SalesBlink can send to Make.

How it fires
scheduled. Make checks SalesBlink on the scenario's schedule, so a click shows up at the next check, not the second it happens.
When to use it
a link points to your pricing or booking page and you want those clickers moved to a list that gets a more personal follow-up.
Watch out
one person may well click more than once, so expect possible repeats and test with Run once before you add them anywhere.
SalesBlink3Watch New Reply Received

Watch New Reply Received

Scheduled trigger

In Make“Triggers when a reply is received on a cold email.”

Catches the answers prospects send back to your cold emails, so a reply can reach your team in the tool they already watch instead of waiting in an inbox.

How it fires
scheduled. Make checks SalesBlink on the scenario's schedule and picks up the replies received since the previous run.
When to use it
you want each reply posted to a sales channel or turned into a task for the rep who owns the account.
Watch out
the trigger does not judge the tone of a reply, so an unsubscribe request arrives just like a meeting request; add a check before acting on it.
Modules

SalesBlink actions in Make

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

SalesBlink1

Add a Lead to a List

Action

In Make“Adds leads to a SalesBlink List”

Puts a lead into one of your SalesBlink lists from inside a scenario, so contacts coming from a form, a CRM or a SalesBlink trigger land where your outreach can use them.

When to use it
a web form collects a new prospect and you want that person ready in the list your next email sequence reads.
Watch out
map the contact details from the previous module carefully and test with Run once, since a wrong mapping fills the list with empty leads.
SalesBlink2

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Opens the whole SalesBlink API to your scenario through the connection you already set up, for the jobs the four other modules leave out.

When to use it
you need something SalesBlink offers in its API but Make lists no module for, and you have the SalesBlink API reference open to find the right endpoint.
Watch out
here you write the request yourself, so check the endpoint and body against the SalesBlink documentation, and see Make troubleshooting if the call fails.
Need help

Need help automating SalesBlink with Make?

A person reads every message.

FAQ

SalesBlink and Make: common questions

01Is the SalesBlink Make integration free?
Yes, on the Make side. SalesBlink is a standard app, so its modules work on the Free plan, which allows 2 active scenarios, a shortest interval of 15 minutes between scheduled runs, 5 minutes of execution per run and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios, with usage counted in operations each month. You still need your own SalesBlink account, which is billed by SalesBlink.
02What is needed to connect SalesBlink to Make?
Two things: an active SalesBlink account and a SalesBlink API key. You create the key in the Account Settings section of SalesBlink by registering a new one, then copy it. In Make, add any SalesBlink module, click Create a connection, give it a name if you like, and paste the key. That single connection is then reused by every SalesBlink module in your scenarios, so you only do this once per account.
03Does the SalesBlink trigger fire instantly in Make?
No. All three SalesBlink triggers are scheduled, not instant. Make checks SalesBlink on the scenario's schedule and processes the opens, clicks or replies found since the last check. A new scenario checks every 15 minutes by default, and 15 minutes is also the shortest interval on the Free plan. Paid plans let you go down to 1 minute between checks. If you need faster reactions, a paid plan with a short interval is the lever the Make side gives you.
04What if a SalesBlink module is missing in Make?
Use Make an API Call. It sends any request the SalesBlink API accepts, with the connection you already created, so the 5 listed modules are not the end of the road. You write the endpoint and the request body yourself, based on the SalesBlink API documentation. Keep in mind that the SalesBlink documentation shown by Make is marked as AI-generated, so confirm important details with SalesBlink before you build on them.
05Make or n8n for SalesBlink: which one fits?
It depends on what you need. In Make, SalesBlink comes with 3 scheduled triggers on opens, clicks and replies, one action to add a lead to a list, and Make an API Call for the rest, all usable on the Free plan. The same app often has an n8n node too, so check what that node covers before choosing. Compare the modules each side offers for your exact workflow, then pick the tool your team is already comfortable building in.
Same platform

Other docs you might need on this stack.

Browse all integrations