Resources · Make integration

UNISENDER Make integrationAutomate UNISENDER with Make.

Keep your UNISENDER lists in step with the rest of your stack. The UNISENDER Make integration offers 12 modules: 4 triggers, 7 actions and 1 search. This guide walks email marketers through the connection, a first working scenario and every module.

Try the UNISENDER integration on MakeSee the 12 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the UNISENDER Make integration automate?

The UNISENDER Make integration links your UNISENDER account to Make, a visual tool where you build a scenario, meaning an automation made of modules placed one after the other. It watches campaigns and subscriptions, and it manages contact lists and subscribers without any code.

Signups that reach every tool. Watch New Subscriptions fires the moment someone joins, and Get a Contact pulls that person's record so a CRM or a spreadsheet gets the contact record, not just a notification.

Opt-outs respected everywhere. When Watch New Unsubscriptions reports a recipient leaving, the next modules can flag that person in your other tools, so nobody keeps receiving messages from a side channel.

Leads that land on the right list. Start from a form or a shop in another app and finish with Subscribe a Contact, which places the person on one list or several at once.

Know the edges before you plan. No listed module creates or sends a campaign; the two campaign triggers only report what already happened in UNISENDER. For anything the list does not cover, Make an API Call reaches the rest of the API with the same connection. If you are weighing tools, the n8n vs Make comparison lays out the criteria, the Make pricing page explains how operations are counted, and the Make training takes you further once this first scenario runs.

Connect

How do you connect UNISENDER to Make?

  1. 01

    Copy your API key

    In UNISENDER, open Settings, then the Integration and API tab. Click Enabled under API Access if needed, then Show Full next to the key, type your password, hit Send and copy the key.

  2. 02

    Add a UNISENDER module

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

  3. 03

    Name it and paste the key

    Give the connection a clear label in Connection name if you like; this field is optional. Paste the API key you copied, or follow the on-screen instructions, and save to finish.

First scenario

Your first scenario: send new leads to a UNISENDER list

GoalWhen a lead arrives in another app, Make subscribes that person to your UNISENDER list.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. The first module comes from the app where your leads show up, such as a form or a shop.

  2. 02

    Add Subscribe a Contact

    Click the + on the right of that first module, search for UNISENDER and pick Subscribe a Contact. Select your connection, or create it with the steps above.

  3. 03

    Map the lead to the list

    Pick the target list from the choices Make shows once connected, then map the lead's details from the first module. Each bundle, one lead here, flows into this module.

  4. 04

    Test with Run once

    Click Run once and create a test lead in the source app. Open the bundles each module received and check the person now appears on the list in UNISENDER.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module; a new scenario runs every 15 minutes by default, and the Free plan cannot go below that. Then switch the scenario on.

Triggers

What starts a UNISENDER scenario

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

UNISENDER1Watch New Completed Campaigns

Watch New Completed Campaigns

Scheduled trigger

In Make“Triggers when a campaign has been completed.”

This trigger hands your scenario each campaign that has finished in UNISENDER, so the follow-up work starts without anyone checking the dashboard. One finished campaign equals one bundle for the modules that come after it.

How it fires
scheduled: Make checks the app on the scenario's schedule, shown by the clock badge.
When to use it
once a campaign wraps up, post a note to your team channel or log it in the sheet where you track sends.
Watch out
expect the event after the next scheduled check, not at the exact second the campaign ends.
UNISENDER2Watch New Scheduled Campaigns

Watch New Scheduled Campaigns

Scheduled trigger

In Make“Triggers when a new campaign has been scheduled.”

Here you learn about a campaign as soon as it is queued for sending, which gives the rest of your tools a heads-up before recipients see anything. Every newly scheduled campaign becomes one bundle.

How it fires
scheduled: Make checks the app on the scenario's schedule; the clock badge marks it.
When to use it
warn support or sales that a mailing is about to go out, so they are ready for the replies it brings.
Watch out
with a long interval, a campaign may already be sent by the time Make notices it was scheduled.
UNISENDER3Watch New Subscriptions

Watch New Subscriptions

Instant trigger

In Make“Triggers when there is a new subscription to a campaign.”

Every new subscription reaches your scenario right away, which makes this the natural starting point for welcoming or recording a fresh subscriber elsewhere. Each subscription arrives as its own bundle.

How it fires
instant: the app calls Make through a webhook as soon as it happens, hence the lightning badge.
When to use it
copy each newcomer into your CRM, then chain Get a Contact when you need more than the event itself.
Watch out
when adding it, click Create a webhook before Create a connection, or the setup stays incomplete.
UNISENDER4Watch New Unsubscriptions

Watch New Unsubscriptions

Instant trigger

In Make“Triggers when a recipient has unscubsribed from a campaign.”

Opt-outs land in your scenario the moment a recipient leaves, so your other systems can honor that choice without waiting on a manual export. One unsubscribe produces one bundle.

How it fires
instant: the app calls Make through a webhook as soon as it happens, marked by the lightning badge.
When to use it
tag the person as unsubscribed in your CRM so sales stops emailing them from a different tool.
Watch out
avoid pairing it with Subscribe a Contact on the same list, or you would undo the choice the recipient just made.
Modules

Everything UNISENDER can do in a scenario

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

UNISENDER1

Create a Contact List

Action

In Make“Creates a new contact list.”

A new contact list appears in UNISENDER without you opening the app, ready to receive subscribers from the modules that follow. That keeps segments consistent when they are born from events elsewhere.

When to use it
a new product, webinar or client project needs its own audience, and you want the list created at the moment that project appears in your other tools.
Watch out
run it once per new segment only, otherwise every pass leaves another list behind.
UNISENDER2

Delete a Contact List

Action

In Make“Deletes a selected contact list.”

Removes the list you select from UNISENDER, which keeps the account tidy when an audience has served its purpose. Pair it with List Contact Lists if you need to find the right list first.

When to use it
an event or a temporary campaign is over and its dedicated list should not linger among the active ones.
Watch out
treat the deletion as permanent and test it on a throwaway list with Run once before pointing it at real data.
UNISENDER3

Get a Contact

Action

In Make“Gets a single contact of a list.”

You receive the record of one contact from a list, so later modules can reuse that person's details instead of relying on a bare event. The result is a single bundle.

When to use it
right after Watch New Subscriptions, to enrich the signal before sending the newcomer to a CRM or a spreadsheet.
Watch out
it reads one contact of one list, so make sure the scenario already knows which list and which person to ask for.
UNISENDER4

Make an API Call

Action

In Make“Performs an arbitary authorized API call.”

Covers whatever the other UNISENDER modules leave out by calling any endpoint of the UNISENDER API, reusing the connection you already created. Nothing new to authorize.

When to use it
you need a campaign action or some data that no listed module offers, and you do not want to leave the scenario to get it.
Watch out
this module expects you to read the UNISENDER API documentation and build the request yourself, so keep it for the gaps.
UNISENDER5

Subscribe a Contact

Action

In Make“Subscribes a contact to a list or several lists.”

Adds a person to one list or to several lists in the same step, which is how leads collected elsewhere become UNISENDER subscribers. It closes the loop between capture and mailing.

When to use it
a form, a checkout or a CRM stage produces a new lead and you want that person on the right mailing list immediately.
Watch out
check the list choice carefully during Run once, because a wrong mapping sends every lead to the same place.
UNISENDER6

Unsubscribe a Contact

Action

In Make“Unsubscribes a contact from selected lists.”

Takes a contact off the lists you pick, so an opt-out recorded somewhere else is honored in UNISENDER as well. No manual edit in the UNISENDER interface.

When to use it
a customer asks your support team or your CRM to stop receiving mailings and you want UNISENDER to follow without a manual edit.
Watch out
choose the lists explicitly, since leaving one out keeps the person subscribed there.
UNISENDER7

Update a Contact List

Action

In Make“Updates an existing contact list.”

Changes an existing contact list rather than creating a duplicate, which keeps the same audience and its subscribers while its details evolve. Handy when a project gets renamed in another tool.

When to use it
a product, event or client changes name in your project tool and the matching UNISENDER list should reflect it.
Watch out
the scenario must know which list to edit; List Contact Lists placed earlier helps you pick it.
UNISENDER8

List Contact Lists

Search

In Make“Gets all contact lists.”

Returns every contact list of the account, one bundle per list, so the scenario can loop over them or pick the one it needs. As a search, it can also return nothing.

When to use it
before Update a Contact List or Delete a Contact List, or to copy the current list inventory into a spreadsheet.
Watch out
each returned list counts as a bundle for the next module, so operations add up on large accounts.
Need help

Need help automating UNISENDER with Make?

A person reads every message.

FAQ

UNISENDER and Make: common questions

01Is the UNISENDER Make integration free?
Yes, on the Make side. UNISENDER is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes per execution and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Each module run on one bundle is one operation, and that usage is counted in credits per month. You still need your own UNISENDER subscription.
02What do you need to connect UNISENDER to Make?
An active Selzy account with UNISENDER and an API key. You find the key in UNISENDER under Settings, then the Integration and API tab: enable API access if asked, click Show Full next to the key, confirm with your password and copy it. In Make, add a UNISENDER module, click Create a connection, optionally fill Connection name, and paste the key. For the two instant triggers, click Create a webhook before creating the connection. After that, every UNISENDER module in your scenarios reuses the same connection.
03Does the UNISENDER trigger fire in real time?
It depends on which one. Watch New Subscriptions and Watch New Unsubscriptions are instant triggers: UNISENDER calls Make through a webhook as soon as the event happens, so the scenario starts immediately. Watch New Completed Campaigns and Watch New Scheduled Campaigns are scheduled triggers: Make checks UNISENDER on the scenario's schedule, every 15 minutes by default, and never below 15 minutes on the Free plan. On a paid plan, the interval can drop to 1 minute.
04What if a UNISENDER module is missing in Make?
Use Make an API Call. It reaches any endpoint of the UNISENDER API with the connection you already have, which covers what the 11 other modules do not, such as working on campaigns themselves: no listed module creates or sends one. You build the request from the UNISENDER API documentation, so it takes a bit more care than a ready-made module. The Make documentation page for UNISENDER is itself AI-generated, and it recommends checking important details with UNISENDER directly.
05Should you use Make or n8n for UNISENDER?
It depends on your criteria rather than on a winner. In Make, UNISENDER comes with 12 native modules, including 2 instant triggers for subscriptions and unsubscriptions, plus Make an API Call for the rest, and it runs from the Free plan. The same app often has an n8n node too, so check what that node covers against the scenarios you plan. Compare the triggers you need, the list actions and how each tool counts executions before you choose.
Same platform

Other docs you might need on this stack.

Browse all integrations