Resources · Make integration

YouLead Make integrationAutomate YouLead with Make.

Can Make push your leads into YouLead without any code? Yes: the YouLead Make integration offers 4 action modules, from contact sync to custom events. This guide is for marketers who know YouLead but are new to Make, and it walks you through your first working scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the YouLead Make integration do?

The YouLead Make integration lets a scenario, the automation you build in Make, write into your YouLead account on its own. Every one of its 4 modules is an action: it sends something to YouLead, such as a contact, an event or a form, whenever the scenario reaches it. Nothing has to be copied by hand anymore.

A contact list that stays current. When a lead lands in another tool, say a webinar signup sheet or a CRM, Create a Contact or Update a Contact carries it into YouLead. The module name says it covers both cases, so a returning lead should not end up as a second record.

Activity that YouLead can see. Send a Custom Event and Send a Form hand YouLead things that happened elsewhere: a demo booked in a calendar app, a form filled on a landing page built with another tool. The exact fields each module accepts are not public, so open the module in Make and read what it asks for.

Anything else the API offers. Make an API Call reaches any YouLead endpoint with the same connection. It is the fallback when the three named modules stop short.

Two limits to keep in mind. YouLead has no trigger in Make, so a scenario starts from another app or from a schedule. And Make itself warns that its YouLead documentation is limited, because little public information exists about the app. The Make review explains how the editor works in general, Make pricing covers the plans, and if you are weighing tools, n8n vs Make compares both side by side.

Connect

How do you connect YouLead to Make?

  1. 01

    Add a YouLead module

    In your scenario, click the + and search for YouLead, then pick any of its modules. The first time, Make shows a Create a connection button. A connection is your YouLead account linked to Make once, then reused by every YouLead module.

  2. 02

    Name the connection

    Giving it a name is optional but handy. If you manage several YouLead accounts, for instance one per client or brand, a clear name tells you later which account a scenario writes to.

  3. 03

    Authorize and save

    Depending on what YouLead asks, you either approve access on a YouLead page or paste the key YouLead gives you. Then click Save. Make can now read the lists and objects your account exposes when you fill in a module.

First scenario

Your first YouLead scenario in Make

GoalWhen a new lead appears in another app, Make creates or updates the contact in YouLead and logs a custom event.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Since YouLead has no trigger, this first module comes from the app where your leads arrive.

  2. 02

    Add the YouLead contact module

    Click the + on the right of that module, search for YouLead and choose Create a Contact or Update a Contact. Create the connection if this is your first YouLead module.

  3. 03

    Map the lead data

    Fill the fields by mapping values from the first module, such as the email and name of the lead. Each lead travels as a bundle, one item passed from module to module.

  4. 04

    Log the event

    Add Send a Custom Event after the contact module and map the same contact into it, so YouLead records that this lead just came in from the other tool.

  5. 05

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received. Check in YouLead that the contact and the event are there before going further.

  6. 06

    Schedule and switch on

    Open the clock on the first module. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan. Adjust it if needed, then switch the scenario on.

Modules

What the YouLead modules do

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

YouLead1

Create a Contact or Update a Contact

ActionIn the docs only

You get one clean YouLead record per person, whether the lead is brand new or already known. As its name says, the module handles both creating and updating in a single step.

When to use it
at the heart of any sync, right after the module that brings in a new signup, purchase or CRM change from another app.
Watch out
Make does not document how YouLead decides a contact already exists, so run a test with a known email first and check the result.
YouLead2

Make an API Call

ActionIn the docs only

This gives you access to any endpoint of the YouLead API, using the connection you already created. No second login, no separate key to manage.

When to use it
when what you need is not one of the three other modules, for example reading data back from YouLead, since all four listed modules are actions that send data.
Watch out
you have to know the endpoint and its parameters from YouLead's own API reference, because Make offers only limited documentation for this app.
YouLead3

Send a Custom Event

ActionIn the docs only

With this module, something that happened outside YouLead shows up there as an event you name yourself. That way your YouLead data reflects actions taken in tools it cannot see on its own.

When to use it
after a meaningful moment in another app, such as a booked call or a paid invoice, once the contact exists in YouLead.
Watch out
keep event names consistent across scenarios; the fields it expects are not public, so check them in the module itself.
YouLead4

Send a Form

ActionIn the docs only

Form answers collected somewhere other than YouLead end up in YouLead anyway, as a form submission. It suits teams whose landing pages or surveys live in a different tool.

When to use it
when the answers come from a signup or survey page built elsewhere and you want them to reach YouLead as a form, not only as a contact.
Watch out
each submitted entry costs one operation, meaning one run of one module that Make counts on your plan, so avoid sending the same entry twice.
Need help

Need help automating YouLead with Make?

A person reads every message.

FAQ

YouLead and Make: common questions

01Is the YouLead Make integration free?
Yes, YouLead is a standard app, so it works on the Make Free plan. That plan has real limits though: 2 active scenarios, at least 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) bring the interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, each one being one module run on one bundle. Any YouLead subscription is a separate matter handled with YouLead.
02What do you need to connect YouLead to Make?
A YouLead account and a Make account. Make lists no special prerequisite for this app. You add any YouLead module, click Create a connection, optionally name it, then either approve access on the YouLead side or paste the key YouLead gives you, and save. The connection is then reused by all four YouLead modules. Keep in mind that Make describes its YouLead documentation as limited, so if a key is requested, you will find it in your YouLead account rather than in the Make docs.
03Does YouLead trigger a Make scenario in real time?
No, because YouLead has no trigger module in Make at all. All four modules are actions, so something else has to start the scenario. You can begin with a trigger from another app, such as a form tool or a CRM, and then send the data to YouLead. You can also rely on the scenario schedule set on the first module, every 15 minutes by default. Whether the start is instant then depends on that other app and on how its own trigger works in Make.
04What if the YouLead module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the YouLead API with the connection you already have, so you are not limited to the three named modules. That covers, for example, reading information back from YouLead, while the listed modules are all actions that send data. The catch is documentation: Make says it cannot fully document YouLead because too little public information exists, so you will need YouLead's own API reference to know which endpoint to call and what to send.
05Should you use Make or n8n for YouLead?
It depends on the tool your team already works in. On the Make side, the facts are clear: four action modules, no trigger, and Make an API Call to reach the rest of the YouLead API. The same app often has an n8n node too, but whether it exists and what it covers has to be checked on the n8n side before deciding. Compare the modules each tool actually offers for YouLead, then pick the platform where your other scenarios already run, to keep everything in one place.