Resources · Make integration

Userlist Make integrationAutomate Userlist with Make.

Can Userlist react to what your other tools see, without a developer? The Userlist Make integration gives you 23 modules: 15 instant triggers and 8 actions. This page shows SaaS teams how to connect the account, build a first scenario and pick the right module.

Try the Userlist integration on MakeSee the 23 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Userlist Make integration do?

The Userlist Make integration links your Userlist account to Make, a no-code tool where you build a scenario (the automation itself, a chain of modules). Userlist can start a scenario the moment a user or company changes, and Make can write users, companies and events back into Userlist from any other app.

Signups land in Userlist on their own. A lead fills a form in another tool, and Create or Update User adds the person to Userlist, or refreshes the profile if the identifier already exists. No duplicate to clean afterward.

Sales hears about product signals. With Company Joined a Segment, an account that enters a segment such as trial accounts close to activation can post a message to your team chat or open a deal in your CRM.

Product milestones reach your campaigns. Create an Event records an action that happened elsewhere, like a booked demo, so Userlist can use it to start the right message.

One gap to know: the integration has 0 search modules, so Make cannot look up a user with the listed modules. Make an API Call reaches whatever else the Userlist API exposes, if it offers a lookup at all. If you weigh other tools, the n8n vs Make comparison lays out the criteria, and the Make training walks you through your first builds.

Connect

How do you connect Userlist to Make?

  1. 01

    Copy your Push Key in Userlist

    In Userlist, open Settings, then the Push tab. The API key shown there is the Push Key. Copy it: you need an active Userlist account to see it, and you will paste it into Make in a moment.

  2. 02

    Add a Userlist module in Make

    Open your scenario, add any Userlist module, then click Create a connection. A connection is your Userlist account linked to Make once, then reused by every Userlist module. The Connection name field is optional.

  3. 03

    Paste the key and save

    Paste the Push Key where Make asks for it, or follow the on-screen instructions, and save. Make now lists your Userlist data in the module fields, so you pick values instead of typing them.

First scenario

Build your first scenario: new signups into Userlist

GoalWhen someone signs up in your form or payment tool, Make creates or updates the user in Userlist and logs a signup event.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big +. The first module is the tool where signups arrive: search it by name and pick its new submission or new customer trigger.

  2. 02

    Add Create or Update User

    Click the + to the right of that module, search Userlist and pick Create or Update User. Choose your connection, or click Create a connection and paste your Push Key.

  3. 03

    Map the signup data

    Fill the fields by clicking values from the first module, the email or the ID of the person. Each signup travels as one bundle, one item passed from module to module, so every person is handled on their own.

  4. 04

    Log the signup with Create an Event

    Add Create an Event after the user module and map the same person. Userlist can then use that event to start your onboarding message.

  5. 05

    Test with Run once

    Click Run once, then submit a test signup. Open the bubble above each module to read the bundles it received, and check that the user appears in Userlist.

  6. 06

    Schedule and switch it on

    Set the schedule on the first module (every 15 minutes by default) and switch the scenario on. Each module run on a bundle counts as one operation on your Make plan.

Triggers

What starts a Userlist scenario

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

Userlist1Company Joined a Segment

Company Joined a Segment

Instant trigger

In Make“Triggers when a company joins a segment.”

Your scenario starts as soon as a company enters one of your Userlist segments, so the account shows up in other tools right when it matters.

How it fires
instant, Userlist calls Make through a webhook as soon as it happens.
When to use it
a segment of accounts that look ready to upgrade, and your sales team wants a message in their channel to follow up.
Watch out
the trigger watches segment membership, not every edit, so the segment rules decide what reaches Make.
Userlist2Company Left a Segment

Company Left a Segment

Instant trigger

In Make“Triggers when a company leaves a segment.”

This one catches the opposite move: a company drops out of a segment, and Make gets the account right away so you can react before the signal goes cold.

How it fires
instant, Userlist calls Make through a webhook as soon as it happens.
When to use it
an active-accounts segment, where leaving it means usage is dropping and your success team should reach out.
Watch out
pair it with Company Joined a Segment on a separate scenario if you track both directions, rather than guessing from one.
Userlist3Company Updated

Company Updated

Instant trigger

In Make“Triggers when a company is updated.”

Any change on a company record in Userlist sends the updated account to Make, which keeps a CRM or a spreadsheet aligned with what Userlist knows.

How it fires
instant, Userlist calls Make through a webhook as soon as it happens.
When to use it
your CRM holds the company plan or owner, and you want it to follow every update made in Userlist.
Watch out
if the same scenario writes the company back with Create or Update Company, you create a loop that eats operations.
Userlist4New Company

New Company

Instant trigger

In Make“Triggers when a new company is created.”

Each company created in Userlist becomes a bundle in Make, ready to be copied wherever your team tracks accounts, like a CRM, a sheet or a chat channel.

How it fires
instant, Userlist calls Make through a webhook as soon as it happens.
When to use it
a new customer account should open a record in your CRM without anyone copying the name by hand.
Watch out
updates to that company do not fire this trigger again; use Company Updated for those.
Userlist5New Company Custom Event

New Company Custom Event

Instant trigger

In Make“Triggers when a company performs a custom event.”

When a company performs one of your custom events in Userlist, Make receives it and can act on it outside Userlist, for example in billing or support tools.

How it fires
instant, Userlist calls Make through a webhook as soon as it happens.
When to use it
an account-level milestone, such as a workspace reaching its first project, that should notify the account owner.
Watch out
it only sees company events; events tied to a single person go through New Custom User Event.
Userlist6New Custom User Event

New Custom User Event

Instant trigger

In Make“Triggers when a user performs a custom event.”

This trigger hands Make every custom event a user performs, which turns product behavior into actions in the rest of your stack.

How it fires
instant, Userlist calls Make through a webhook as soon as it happens.
When to use it
a user finishes a key step in your app and you want a row in a reporting sheet or a note in your support tool.
Watch out
if you also send events with Create an Event, add a filter so the scenario does not feed its own output back into itself.
Userlist7New Relationship

New Relationship

Instant trigger

In Make“Triggers when a new relationship is created.”

A relationship created in Userlist reaches Make at once, so the tools around Userlist learn about the new link on the same record.

How it fires
instant, Userlist calls Make through a webhook as soon as it happens.
When to use it
a teammate joins a customer account and your CRM should show that contact under the right company.
Watch out
run Run once on a real case first and read the bundle, so you map the fields Userlist actually sends.
Userlist8New User

New User

Instant trigger

In Make“Triggers when a new user is created.”

Every person added to Userlist starts the scenario, which is the simplest way to push fresh users into a newsletter tool, a CRM or a welcome message.

How it fires
instant, Userlist calls Make through a webhook as soon as it happens.
When to use it
your team wants a chat message for each new user during a launch, or a CRM contact per signup.
Watch out
users created by your own Make scenario fire it too, so keep that in mind before writing back to Userlist.
Userlist9Updated Relationship

Updated Relationship

Instant trigger

In Make“Triggers when a relationship is updated.”

When an existing relationship changes in Userlist, Make gets the new version, which keeps linked records elsewhere from drifting out of date.

How it fires
instant, Userlist calls Make through a webhook as soon as it happens.
When to use it
a contact's place in a customer account changes and the CRM record needs the same update.
Watch out
a scenario that answers with Create or Update Relationship on the same record will fire this trigger again and loop.
Userlist10Updated User

Updated User

Instant trigger

In Make“Triggers when a user is updated.”

Each edit to a user profile in Userlist is sent to Make, so the profile in your CRM or support desk stays in step with Userlist.

How it fires
instant, Userlist calls Make through a webhook as soon as it happens.
When to use it
a user changes plan or role in your product, and your support desk should see the new value on the next ticket.
Watch out
every update starts a run and costs operations, so add a filter to keep only the changes you need.
Userlist11User Joined a Segment

User Joined a Segment

Instant trigger

In Make“Triggers when a user joins a segment.”

The moment a person enters a segment, Make receives that user, so you can act on a behavior Userlist already detected instead of rebuilding the rule.

How it fires
instant, Userlist calls Make through a webhook as soon as it happens.
When to use it
a segment of trial users who reached activation, and the account owner should get a heads-up to call.
Watch out
the segment definition lives in Userlist, so change it there, not in Make.
Userlist12User Left a Segment

User Left a Segment

Instant trigger

In Make“Triggers when a user leaves a segment.”

You get notified when a person drops out of a segment, which is often the earliest sign that engagement is slipping.

How it fires
instant, Userlist calls Make through a webhook as soon as it happens.
When to use it
a user leaves your engaged segment and your success team wants a task created in their project tool.
Watch out
leaving a segment is not the same as unsubscribing; for consent changes, use User Unsubscribed instead.
Userlist13User Submitted a Form

User Submitted a Form

Instant trigger

In Make“Triggers when a user submits a form.”

Answers from a Userlist form travel straight to Make, where they can fill a sheet, open a ticket or reach the right person on your team.

How it fires
instant, Userlist calls Make through a webhook as soon as it happens.
When to use it
an in-app feedback form whose replies your product team reads in a shared spreadsheet.
Watch out
submit one real test answer during Run once, so Make learns the structure of your form before you map it.
Userlist14User Subscribed

User Subscribed

Instant trigger

In Make“Triggers when a user (re-)subscribes to messages.”

This trigger fires when a user subscribes, or subscribes again, to your messages, which lets other tools respect the new consent right away.

How it fires
instant, Userlist calls Make through a webhook as soon as it happens.
When to use it
your newsletter tool or CRM keeps its own opt-in flag and must match Userlist.
Watch out
a re-subscribe fires it as well, so do not treat every bundle as a brand-new contact.
Userlist15User Unsubscribed

User Unsubscribed

Instant trigger

In Make“Triggers when a user unsubscribes from messages.”

When someone opts out of your messages in Userlist, Make hears it at once and can carry the opt-out into every other sending tool.

How it fires
instant, Userlist calls Make through a webhook as soon as it happens.
When to use it
sales sequences run from another tool, and an unsubscribed person should leave them too.
Watch out
test it with a dummy user, not a real customer, since the unsubscribe itself is what starts the run.
Modules

What Make can do in Userlist

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

Userlist1

Create an Event

Action

In Make“Creates an event.”

Records an event in Userlist from outside the product, so a booked demo or a paid invoice can drive your campaigns like any in-app action.

When to use it
a meeting tool or payment app knows about a milestone that Userlist cannot see by itself.
Watch out
name events the same way every time, or your segments and campaigns will miss them.
Userlist2

Create or Update Company

Action

In Make“Creates a new company or updates the existing company when the identifier is already known.”

Adds a company to Userlist, or updates it when the identifier is already known, which gives you one module for both new and existing accounts.

When to use it
your CRM or billing tool is where accounts are born, and Userlist should mirror them.
Watch out
map a stable identifier, since a changing one creates a second company instead of updating the first.
Userlist3

Create or Update Relationship

Action

In Make“Creates or updates a relationship”

Creates a relationship in Userlist or updates the existing one, so the links your other tools manage end up in Userlist too.

When to use it
someone is added to a customer account in your app or CRM and Userlist should reflect it for account-level campaigns.
Watch out
the user and the company usually need to exist first, so place this module after the ones that create them.
Userlist4

Create or Update User

Action

In Make“Creates a new user or updates the existing user when the identifier is already known.”

Adds a person to Userlist or refreshes their profile when the identifier already exists, the go-to module for feeding signups from any form or payment tool.

When to use it
leads from landing pages or ads should start your Userlist onboarding without a CSV import.
Watch out
an identifier that changes between tools creates duplicates, so map the same value every time.
Userlist5

Delete Company

Action

In Make“Deletes a company.”

Removes a company from Userlist, which keeps closed accounts out of your segments and account-level campaigns.

When to use it
an account is closed for good in your billing tool and should stop receiving anything.
Watch out
a deletion cannot be undone from Make, so put a filter in front and test it on a dummy company with Run once.
Userlist6

Delete Relationship

Action

In Make“Deletes a relationship”

Removes one relationship in Userlist while the user and the company themselves stay in place.

When to use it
a person leaves a customer account in your app, but remains a user elsewhere and should keep their own profile.
Watch out
choose this over Delete User or Delete Company when only the link is wrong, since those two remove far more.
Userlist7

Delete User

Action

In Make“Deletes user.”

Erases a user from Userlist, which is what you want when someone asks for their data to be removed or closes their account.

When to use it
a deletion request arrives through your support desk or a form, and Userlist must follow.
Watch out
there is no undo; if the person only opted out of messages, leave the profile alone and rely on the unsubscribe.
Userlist8

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Calls any endpoint of the Userlist API with your existing connection, the way to reach what the other seven modules do not cover.

When to use it
you need an operation the listed actions skip, such as a lookup if the Userlist API offers one, since there is no search module.
Watch out
you write the request yourself, so keep the Userlist API reference open while you build it.
Need help

Need help automating Userlist with Make?

A person reads every message.

FAQ

Userlist and Make: common questions

01Is the Userlist Make integration free?
Yes, on the Make side. Userlist is a standard app, so its modules work on the Make Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes per run, files up to 5 MB and 512 MB of data transfer. Paid plans remove the cap on active scenarios and lower the interval to 1 minute. You still need an active Userlist account, which Userlist bills on its own terms.
02What does it take to connect Userlist to Make?
An active Userlist account and its Push Key. In Userlist, go to Settings, open the Push tab and copy the API key shown as the Push Key. In Make, add a Userlist module, click Create a connection, give it a name if you like, and paste the key. For an instant trigger, Make first asks you to click Create a webhook, then Create a connection. The same connection is then reused by all 23 Userlist modules.
03Do Userlist triggers in Make fire in real time?
Yes. All 15 Userlist triggers are instant: Userlist calls Make through a webhook as soon as the event happens, whether a user is created, a company joins a segment or someone unsubscribes. There is no polling interval to wait for on these triggers. The 15-minute schedule of a new scenario matters only when your scenario starts with another app's scheduled trigger, which can be the case in the signup example on this page, depending on the tool you pick.
04What if the Userlist module you need is missing in Make?
Use Make an API Call. It sends any request the Userlist API accepts, with the connection you already set up. It is the answer to the most visible gap: the integration has 0 search modules, so any lookup goes through that module, provided the Userlist API offers one. The 8 actions cover creating, updating and deleting users, companies and relationships, plus creating events. The Make documentation for this app says it is AI-generated, so confirm critical details with Userlist.
05Should you use Make or n8n with Userlist?
It depends on the tool your team already runs. On Make, Userlist brings 23 modules, 15 of them instant triggers, and works from the Free plan. Apps listed in Make often have an n8n node too, so check whether Userlist does before you decide. Then compare the two tools on the criteria that matter to you, such as how your team builds, where the scenario must run and which other apps it touches. The n8n vs Make comparison linked above covers those points.
Same platform

Other docs you might need on this stack.

Browse all integrations