Resources · Make integration

Scan2Lead Make integrationAutomate Scan2Lead with Make.

Can your Scan2Lead leads move on their own once they land in your account? The Scan2Lead Make integration gives you 3 modules: 1 scheduled trigger and 2 actions. This guide shows how to link your account and build a first scenario, no code needed.

Try the Scan2Lead integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Scan2Lead Make integration do for you?

The Scan2Lead Make integration links your Scan2Lead account to Make, a tool where you build a scenario: an automation made of modules, each one a brick that watches, reads or acts. Once the link is set, your leads can travel into the rest of your stack without anyone copying them by hand.

Leads that reach your other tools without copy and paste. Watch Leads starts the scenario when Make finds leads to process, and each lead then flows to the next module as a bundle, meaning one item passed along the chain. From there you add the module of whatever app should receive it.

A fresh batch of recent activity on demand. Get New and Changed Leads is an action, so it can sit in the middle of a scenario started by something else, such as a schedule or another app, and bring back the leads its name points to.

Anything the listed modules skip. Make an API Call reaches any endpoint of the Scan2Lead API with the same connection, so a missing module is rarely a dead end.

Keep the limits in mind. The Make documentation for Scan2Lead is short: it names the 3 modules without describing their fields, and it flags its own content as AI-generated, to be checked against the vendor. Test every module with Run once before you rely on it. If you are still weighing tools, the Make review and the n8n vs Make comparison help, and Make training covers the editor from scratch.

Connect

How do you connect Scan2Lead to Make?

  1. 01

    Copy your API key

    Log in to the Scan2Lead portal and open the Connector page from the main navigation. The button at the top of that page reveals your API key: copy it and keep the tab open.

  2. 02

    Add a Scan2Lead module

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

  3. 03

    Paste the key and save

    Give the connection a clear label in Connection name if you like, it is optional. Paste the API key you copied, or follow the instructions shown on screen, and save.

First scenario

Build your first Scan2Lead scenario

GoalWhen Make finds leads in Scan2Lead, it hands each one to a Scan2Lead API call you choose.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + in the middle of the editor to place the first module.

  2. 02

    Pick Watch Leads

    Search for Scan2Lead, choose Watch Leads, then select the connection you made earlier or click Create a connection if this is your first module.

  3. 03

    Add the API call

    Click the + on the right of Watch Leads and add Make an API Call. Map values from the lead into the request, so the call works on the exact lead Make just found.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time, and the bubble above each module shows the bundles it received. Check that the lead data looks right.

  5. 05

    Schedule and switch on

    Open the clock on Watch Leads to set the schedule, every 15 minutes by default, then turn the scenario on. From now on it runs without you.

Triggers

What starts a Scan2Lead scenario?

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

Scan2Lead1Watch Leads

Watch Leads

triggerIn the docs only

Watch Leads is the entry point of the integration: it lets a scenario start from your Scan2Lead leads, so each one found by Make becomes a bundle the next modules can use. The documentation gives only its name, not the fields it returns.

How it fires
scheduled, Make checks Scan2Lead on the scenario's schedule, every 15 minutes by default and never faster than that on the Free plan.
When to use it
pick it when the lead itself should kick off the work, for example to push new contacts into another app.
Watch out
it is not instant, so a lead waits until the next check before anything happens.
Modules

What else can Make do with Scan2Lead?

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

Scan2Lead1

Get New and Changed Leads

ActionIn the docs only

Get New and Changed Leads pulls leads back into a scenario that something else started, which is handy when Scan2Lead is not the event that opens the flow. Its name suggests it returns the new and updated ones; the documentation adds no detail.

When to use it
after a schedule or another app's trigger, when you want the latest leads at that exact point of the chain.
Watch out
run it once and read the bundles before mapping, since the returned fields are not documented.
Scan2Lead2

Make an API Call

ActionIn the docs only

Make an API Call gives you access to any endpoint of the Scan2Lead API while reusing your existing connection, so you never have to handle the key again. It fills the gap whenever the two other modules do not cover what you need.

When to use it
when a task in Scan2Lead has no ready-made module and the vendor's API documentation lists the endpoint for it.
Watch out
you write the request yourself, so check the endpoint and its parameters with Scan2Lead first.
Need help

Need help automating Scan2Lead with Make?

A person reads every message.

FAQ

Scan2Lead and Make: common questions

01Is the Scan2Lead Make integration free?
Yes, on the Make side. Scan2Lead is a standard app, available from the Free plan, which allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute and remove the cap on active scenarios. Each operation, meaning one module running on one bundle, counts toward your plan. Scan2Lead itself needs its own developer account and subscription, described on its pricing page.
02What do you need to connect Scan2Lead to Make?
A Scan2Lead developer account and its API key. Log in to the Scan2Lead portal, open the Connector page from the main navigation, click the button at the top to reveal the key and copy it. In Make, add a Scan2Lead module, click Create a connection, give it a name if you want, paste the key and save. That single connection then serves all 3 Scan2Lead modules, so you only go through these steps once per account.
03Does the Scan2Lead Watch Leads trigger work in real time?
No. Watch Leads is a scheduled trigger: Make checks Scan2Lead on the schedule set on the first module, every 15 minutes by default. On the Free plan the interval cannot go below 15 minutes; paid plans allow a check every minute. There is no instant version with a webhook listed for this app, so a lead that appears right after a check is picked up at the next one. Pick the interval that matches how fast your team needs the lead.
04What if the Scan2Lead module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the Scan2Lead API with the connection you already set up, so the key stays in one place. You build the request yourself, which means reading the vendor's API documentation for the right endpoint and parameters. Keep in mind that Make flags its Scan2Lead documentation as AI-generated and asks you to verify important points with Scan2Lead directly, so test each call with Run once before switching the scenario on.
05Make or n8n for Scan2Lead?
It depends on the tool your team already runs. This page covers Make, where Scan2Lead has 3 ready modules, a scheduled trigger and an API call module for the rest. Many apps also have an n8n node, so check whether one exists for Scan2Lead before choosing. Compare on what matters to you: the modules available for the tasks you plan, how each tool counts usage, and which editor your team finds easier to maintain. The site's n8n vs Make comparison lays out those criteria in detail.
Same platform

Other docs you might need on this stack.

Browse all integrations