Resources · Make integration

Snov.io Make integrationAutomate Snov.io with Make.

Every reply and every click in Snov.io can start work elsewhere, without code. The Snov.io Make integration gives you 3 triggers, 4 actions and 3 searches. This guide is for sales and growth teams: link your account, build a first scenario, then pick the right module.

Try the Snov.io integration on MakeSee the 10 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Snov.io Make integration automate?

The Snov.io Make integration links your Snov.io account to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules. A module is one brick of that chain, such as a trigger, an action or a search. With Snov.io, those bricks watch your email engagement, find and verify addresses, and update recipients.

Replies that never sit unread. Watch Email Replied picks up each new answer, and Change a Recipient's Status marks that person in Snov.io so the follow-up logic stays clean. You can also push the reply to your team chat or your CRM with a module from another app.

A cleaner list before you send. Add Emails for Verification places addresses in the Snov.io verification queue, and Get Emails Verification Status tells you which ones are valid and deliverable. Bad addresses stay out of your next sequence.

Emails found from a name and a domain. Search Emails looks for an address using a first name, a last name and a company domain. When nothing comes back, Add Names to Find Emails asks Snov.io to search, and you run Search Emails again later.

Know the limits: Make marks its Snov.io documentation as limited, so some fields come without explanation, and every trigger is scheduled rather than instant. Snov.io may also exist in n8n; the n8n vs Make comparison helps you choose. To see what each run costs you, read Make pricing, and the Make training covers the editor from zero.

Connect

How do you connect Snov.io to Make?

  1. 01

    Add a Snov.io module

    In a new scenario, click the +, type Snov.io and pick any module, for example Watch Email Replied. Then click Create a connection. A connection is your Snov.io account linked to Make once and reused by every Snov.io module.

  2. 02

    Name it and authorize

    Give the connection a clear name if you like, such as the name of the team that owns the account. Then follow what Make asks: either approve Make on the Snov.io page that opens, or paste the key Snov.io gives you.

  3. 03

    Save and check

    Click Save. The module now shows your account, and Make can list what it reads from Snov.io in the fields below. If the list stays empty, open the connection again and redo the authorization.

First scenario

Your first scenario: update a recipient when a prospect replies

GoalWhen a prospect replies to an email in Snov.io, Make changes that recipient's status in Snov.io.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + in the middle of the canvas. This first module decides when everything starts.

  2. 02

    Add Watch Email Replied

    Search Snov.io, choose Watch Email Replied and select your connection, or click Create a connection if this is your first Snov.io module. Fill the fields Make shows once the account is linked.

  3. 03

    Add Change a Recipient's Status

    Click the + on the right of the trigger and pick Change a Recipient's Status. Map the recipient from the reply the trigger received, then set the status you want Snov.io to apply.

  4. 04

    Test with Run once

    Reply to one of your own test emails, then click Run once. Make runs the scenario a single time; open the bubble above each module to read the bundle it received, meaning one item passed along, here one reply.

  5. 05

    Schedule and switch on

    Click the clock on the first module to set how often Make checks Snov.io. A new scenario runs every 15 minutes by default. Then flip the switch to turn the scenario on.

Triggers

Which Snov.io triggers can start a scenario?

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

Snov.io1Watch Email Opened

Watch Email Opened

Scheduled trigger

In Make“Triggers when an email has been opened.”

Watch Email Opened hands your scenario each email a recipient has opened, so an open can lead to a task, a note or a message instead of sitting in a report. It suits signals you want to act on while the prospect still remembers you.

How it fires
it is a scheduled trigger, so Make checks Snov.io on the scenario's schedule and collects the opens found since the last check.
When to use it
a sales rep wants a reminder in their task list when a key account opens a proposal email.
Watch out
Make's documentation for this module is limited, so click Run once after a real open and read which details the bundle actually carries.
Snov.io2Watch Email Replied

Watch Email Replied

Scheduled trigger

In Make“Triggers when an email has been replied.”

Watch Email Replied brings every new answer to your emails into Make, which makes it the trigger to pick when a human conversation has started and someone should take over. It is the natural start for anything that needs a person to answer back.

How it fires
scheduled, which means Make asks Snov.io for new replies each time the scenario runs, based on the clock you set on this module.
When to use it
route each reply to the account owner in your team chat and update the recipient in Snov.io in the same run.
Watch out
the reply reaches Make at the next scheduled check, not the second it lands in the inbox.
Snov.io3Watch Link Clicked

Watch Link Clicked

Scheduled trigger

In Make“Triggers when a link with the email has been clicked”

Watch Link Clicked tells Make when a recipient clicked a link inside one of your emails. Pick it when an open is too weak a signal and you only want to act once a prospect has gone as far as the link.

How it fires
the module is scheduled; Make polls Snov.io at the interval of the scenario and returns the clicks recorded since its previous run.
When to use it
someone clicks the pricing or demo link in a cold email, and a marketer wants that contact added to a warm list in another tool.
Watch out
each click is one bundle and each module that processes it costs an operation, the unit Make counts on your plan.
Modules

What can Make do in Snov.io?

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

Snov.io1

Add Emails for Verification

Action

In Make“Adds a list of email addresses you need to add to the verification queue.”

Add Emails for Verification sends a batch of addresses to the Snov.io verification queue, so a list collected from a form or a spreadsheet gets checked before anyone writes to it.

When to use it
new leads land in a sheet from an event and you want them checked before import.
Watch out
this module only queues the addresses; read the result later with Get Emails Verification Status.
Snov.io2

Add Names to Find Emails

Action

In Make“Pushes the request for email search using this method. If an email is found, you can collect it by using the Search Emails request again.”

Add Names to Find Emails asks Snov.io to start looking for an address you do not have yet. It is the fallback when Search Emails returns nothing for a person.

When to use it
a founder's name and company domain are known from a CRM record, but the email field is empty.
Watch out
nothing comes back right away; collect the address later by running Search Emails again.
Snov.io3

Change a Recipient's Status

Action

In Make“Changes a status of a recipient.”

Change a Recipient's Status updates one person in Snov.io from your scenario, which keeps Snov.io in step with what happens in your other tools.

When to use it
right after Watch Email Replied, or when a deal moves forward in your CRM and the contact should no longer be treated as cold.
Watch out
the documentation does not list the statuses, so try one on a test recipient with Run once and check it in Snov.io first.
Snov.io4

Make an API Call

Action

In Make“Performs an arbitrary API call.”

Make an API Call lets you reach any endpoint of the Snov.io API with the connection you already set up. It covers whatever the nine other modules leave out.

When to use it
you need a Snov.io feature that no listed module offers, and you know which API endpoint handles it.
Watch out
you write the request yourself, so keep the Snov.io API reference open while you fill the module.
Snov.io5

Get Emails Verification Status

Search

In Make“Checks if the provided email addresses are valid and deliverable.”

Get Emails Verification Status tells you whether each address you pass is valid and deliverable, so your scenario can keep the good ones and set the rest aside.

When to use it
after Add Emails for Verification, before an address is written into your CRM or a campaign.
Watch out
as a search, it can return several bundles; add a filter after it to route valid and invalid addresses separately.
Snov.io6

Search Emails

Search

In Make“Searches emails by first name, last name and domain. If an email address is not found, you can use the Add Names to Find Emails module to push this email address for search. After that try the Search Emails module again.”

Search Emails looks up an address from a first name, a last name and a domain, which turns a bare contact record into someone you can actually write to.

When to use it
a new company lands in your CRM with a contact name but no email.
Watch out
when it finds nothing, pass the same name to Add Names to Find Emails and run this search again afterwards.
Snov.io7

Search Prospects

Search

In Make“Searches for prospects.”

Search Prospects pulls prospects from Snov.io into your scenario, so you can copy them to a sheet, a CRM or another list without exporting by hand.

When to use it
a growth marketer wants the prospects found in Snov.io mirrored in the CRM the sales team works from.
Watch out
a search returns zero, one or many bundles, and each module after it runs once per prospect.
Need help

Need help automating Snov.io with Make?

A person reads every message.

FAQ

Snov.io and Make: frequent questions

01Is the Snov.io Make integration free?
Yes, Snov.io is a standard app in Make, so you can use it on the Free plan. That plan allows 2 active scenarios, a scheduled run every 15 minutes at most, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the limit on active scenarios and allow 40 minutes per run. Usage is counted in operations each month. Your Snov.io subscription is a separate matter.
02What do you need to connect Snov.io to Make?
A Snov.io account and a Make account are enough; the Make documentation lists no other prerequisite. Add any Snov.io module, click Create a connection, give it a name if you want, then either approve Make on the Snov.io page or paste the key Snov.io provides, and click Save. The connection is created once and every Snov.io module in your scenarios reuses it. If the lists in a module stay empty after that, open the connection again and redo the authorization.
03Do Snov.io triggers in Make fire in real time?
No. Watch Email Opened, Watch Email Replied and Watch Link Clicked are all scheduled triggers. Make checks Snov.io each time the scenario runs and picks up what happened since the previous check. A new scenario runs every 15 minutes by default. On a paid plan you can bring the interval down to 1 minute, which gets closer to live without becoming instant, since Snov.io does not call Make through a webhook here.
04What if the Snov.io module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the Snov.io API with the same connection as the other modules, so a feature without its own module is still available. Keep in mind that Make describes its Snov.io documentation as limited, which means you will rely on the Snov.io API reference and on Run once tests to understand each field. If a problem remains, Make's troubleshooting resources are the next stop.
05Should you use Make or n8n for Snov.io?
It depends on the tool your team already runs. In Make, Snov.io comes with 10 modules: 3 scheduled triggers, 4 actions and 3 searches, plus Make an API Call for the rest. The same app often has a node in n8n too, so check what that node covers before deciding. Compare the exact modules you need for your case, not a general reputation, and choose the tool whose editor your team will actually maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations