Resources · Make integration

Magileads Make integrationAutomate Magileads with Make.

Can Make push new leads into Magileads without copy and paste? Yes. The Magileads Make integration gives you 4 action modules for contact lists, the blacklist and opt-outs. This page shows how to link your account and build a first scenario around them.

Try the Magileads integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Magileads Make integration do?

The Magileads Make integration lets a Make scenario, the automation you build in Make, write contacts into your Magileads account. It has 4 modules, the bricks of a scenario, and all of them are actions: they add, block or opt out a contact. None of them watches Magileads, so another app or a schedule starts the flow.

Leads that land in the right list. A sales rep collects a signup in a form tool, and Add a Contact to Contact List files it in the Magileads list your campaign reads. If the person is already there, Magileads updates the record instead of creating a twin.

Opt-outs honored everywhere. When someone asks to stop hearing from you in another tool, Add a Subscriber to Unsubscribers records it on the Magileads side too, by email, domain or SIREN number.

A blacklist kept up to date. Some companies should never get a cold email from you. Competitors, existing customers or partners go into a blacklist with Add a Contact to Blacklist. For anything the three ready modules do not cover, Make an API Request sends your own call to the Magileads API.

What Make does not do here: react on its own to something that happens inside Magileads, because the app has no trigger module. Weighing n8n as well? The n8n vs Make page lays out how the two editors differ. New to the editor? The Make training starts from zero, and the Make pricing page explains plans and operations.

Connect

How do you connect Magileads to Make?

  1. 01

    Copy your API key in Magileads

    You need an active Magileads account. Open the Settings section, click the API subsection and copy the API key shown on screen. Keep that tab open, you paste the key into Make in a moment.

  2. 02

    Add a Magileads module in Make

    In your scenario, add any Magileads module and click Create a connection. A connection is your Magileads account linked to Make once; every Magileads module of your scenarios reuses it afterwards.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps if you manage several accounts. Paste the API key you copied, or follow the instructions Make shows on screen, then save the connection.

First scenario

Your first scenario with Magileads

GoalWhen a lead fills in a form in another app, Make adds that person to a Magileads contact list.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Here that first module comes from the app that receives your leads, such as a form tool.

  2. 02

    Set up the lead source

    Search that app by name, pick its module that returns new entries and connect your account. Each new entry becomes a bundle: one item, here one lead, passed to the next module.

  3. 03

    Add Add a Contact to Contact List

    Click the + on the right of the first module, search Magileads and choose Add a Contact to Contact List. Pick your connection, choose the target list and map the lead data from the form.

  4. 04

    Test with Run once

    Submit a test entry in your form, then click Run once. Make runs the scenario one time and shows the bundles each module received, so you can confirm the contact reached the right Magileads list.

  5. 05

    Schedule and switch it on

    Open the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. Each module run on one bundle is an operation, the unit Make counts on your plan.

Modules

What can Magileads do in Make?

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

Magileads1

Add a Contact to Blacklist

Action

In Make“Imports a contact into a specified blacklist. If the contact already exists, it will be updated.”

Puts a contact on a Magileads blacklist you pick, so the people your team has decided to leave alone stay out of reach. A contact that is already known gets updated rather than duplicated.

When to use it
a deal closes in your CRM and the new customer should never again receive a cold sequence.
Watch out
this module blocks a contact; to record that a person asked to unsubscribe, the opt-out module fits better.
Magileads2

Add a Contact to Contact List

Action

In Make“Imports a contact into a specified contact list. If the contact already exists, it will be updated.”

Files a person into the Magileads contact list of your choice, ready for your next campaign. Existing contacts are refreshed with the new data instead of appearing twice, which keeps lists clean when leads come back.

When to use it
a webinar signup or a demo request should feed a prospecting list the moment your scenario picks it up.
Watch out
map the fields from the previous module carefully, a wrong mapping updates a real contact with the wrong values.
Magileads3

Add a Subscriber to Unsubscribers

Action

In Make“Add unsubscriber to an organization using various data types (email, domain, SIREN, etc.).”

Records an opt-out for your organization in Magileads, and the identifier can be an email, a whole domain or a SIREN number, among other data types. The person or company then counts as unsubscribed on the Magileads side.

When to use it
someone clicks unsubscribe in your newsletter tool and you want the same wish respected in your outreach.
Watch out
a domain entry covers everyone at that company, so choose it only when that is really the request.
Magileads4

Make an API Request

Action

In Make“Allows you to make a custom API request to the Magileads API.”

Sends a request you write yourself to the Magileads API, using the connection you already set up. It is the way out when none of the three ready-made modules does what your process needs.

When to use it
you need a Magileads operation that exists in its API but has no dedicated module in Make.
Watch out
you write the address and content of the call yourself, so keep the Magileads API documentation open.
Need help

Need help automating Magileads with Make?

A person reads every message.

FAQ

Magileads and Make: common questions

01Is the Magileads Make integration free?
Yes, on the Make side. Magileads is a standard app, so its modules work on the Free plan, which allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run and files up to 5 MB. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios. You still need your own active Magileads account, whose subscription is separate from Make.
02What do you need to connect Magileads to Make?
Two things: an active Magileads account and its API key. In Magileads, open Settings, then the API subsection, and copy the key displayed there. In Make, add a Magileads module, click Create a connection, optionally give it a name and paste the key. That single connection then serves all 4 Magileads modules across your scenarios, so you only do this once per account. If the key changes later, update the connection rather than rebuilding each module.
03Can a Magileads Make scenario start on its own when something changes in Magileads?
No. Magileads has no trigger module in Make, so nothing in Magileads can start a scenario by itself. You start the flow elsewhere: with a trigger from another app, such as a new form entry or a new CRM deal, or with the schedule on the first module, which runs every 15 minutes by default. The Magileads actions then come after that first module in the chain. Pick whichever start matches the moment the lead actually appears.
04What if the Magileads module you need is missing in Make?
It depends on what you need. The app has no universal Make an API Call module, but it does offer Make an API Request, which sends a custom call to the Magileads API through your existing connection. That requires knowing the API route yourself. If the operation is not in the API either, another app in your stack may cover it, or the Hackceleration team can help you design the workaround.
05Should you use Make or n8n for Magileads?
It depends on your criteria, not on a winner. On Make, the facts are clear: 4 action modules, no trigger, and availability from the Free plan, with the custom Make an API Request module for anything else. Before choosing n8n, check whether a Magileads node exists there and which operations it covers, then compare it line by line with the modules described on this page for your own use case.
Same platform

Other docs you might need on this stack.

Browse all integrations