Resources · Make integration

Customerly Make integrationAutomate Customerly with Make.

Can Make keep your Customerly leads, users and tags in order without code? Yes. The Customerly Make integration gives you 13 modules, including one instant trigger. This guide shows support and growth teams how to connect the account and build a first working scenario.

Try the Customerly integration on MakeSee the 13 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Customerly Make integration do for you?

The Customerly Make integration links your Customerly project to Make, a visual tool where you build a scenario (the automation itself: a chain of modules that runs on a schedule or when an app calls Make). Each module is one brick: it creates a lead, tags a user, or fetches a list. You click them together, and nothing needs to be coded.

Every signup lands in Customerly as a lead. Put a form tool or a spreadsheet at the start of the scenario, then add Create / Update a Lead. Anyone who fills in the form appears in Customerly, and Add a Tag / Untag labels them with the campaign they came from.

Your tag list stays tidy. List Tags returns every tag of the project, so a scenario can spot the ones nobody uses anymore and hand them to Delete a Tag.

Customerly tells Make when something happens. The Universal Trigger is instant: once you attach its webhook to an entity in Customerly, Make starts the scenario the moment that entity fires, with no waiting for a schedule.

What the listed modules do not cover, Make an API Call can reach, since it calls any endpoint of the Customerly API through the same connection. Keep in mind that Make labels its own Customerly documentation as AI-generated and possibly wrong, so check anything critical against Customerly itself. If a scenario breaks, the Make troubleshooting guide covers the usual culprits.

Hesitating between tools? The n8n vs Make comparison lays out the differences, and the Make pricing page explains how operations are counted on each plan.

Connect

How do you connect Customerly to Make?

  1. 01

    Copy your API token in Customerly

    In Customerly, click the Settings icon at the bottom of the left sidebar to open Project Settings. Go to Installation, open the Public API section, and copy the token shown in Your Access Token for Customerly.

  2. 02

    Add a Customerly module in Make

    Log in to Make, open your scenario and add any Customerly module. In its settings, click Create a connection. A connection is your Customerly account linked to Make once, then reused by every Customerly module you add later.

  3. 03

    Paste the token and save

    Give the connection a clear name in Connection name if you like; this field is optional. Paste the API token you copied, or follow the instructions Make shows on screen, then save. The module can now read and write in your Customerly project.

First scenario

Build your first scenario: turn form entries into tagged Customerly leads

GoalWhen a new entry arrives from your form tool, Make creates or updates the matching lead in Customerly and tags it.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Pick the app that collects your signups, such as a form tool or a spreadsheet.

  2. 02

    Add Create / Update a Lead

    Click the + on the right of that first module, search for Customerly and choose Create / Update a Lead. Select your connection, or click Create a connection if this is your first Customerly module.

  3. 03

    Map the form answers

    Fill the lead fields by mapping the answers of the first module into them. Each bundle, meaning one item passed along, here one form entry, becomes one lead in Customerly.

  4. 04

    Tag the new lead

    Add Add a Tag / Untag after the lead module and map the lead it just returned. Choose a tag that tells your support team where this contact came from.

  5. 05

    Test with Run once

    Submit a test entry, then click Run once. Make runs the scenario one time and shows the bundles each module received. Open Customerly and check that the lead exists with its tag.

  6. 06

    Schedule and switch on

    Set the schedule on the first module; a new scenario checks every 15 minutes by default, and 15 minutes is also the shortest interval on the Free plan. Switch the scenario on, and it keeps working without you.

Triggers

What can start a Customerly scenario?

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

Customerly1Universal Trigger

Universal Trigger

Instant trigger

In Make“Triggers when the entity to which you attached the webhook is executed.”

This trigger starts your scenario whenever the Customerly entity you attached its webhook to is executed. It is the only Customerly module that can open a scenario on its own, so it is your door for reacting to what happens inside Customerly rather than pushing data into it.

How it fires
instant, Customerly calls Make through a webhook as soon as it happens, so there is no polling interval to set.
When to use it
you want a follow-up in another tool the moment an event you care about occurs in your Customerly project.
Watch out
click Create a webhook before Create a connection, and attach that webhook to the right entity in Customerly, or nothing will ever arrive.
Modules

What can Make do in Customerly?

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

Customerly1

Add a Tag / Untag

Action

In Make“Adds or deletes a user or lead tag.”

Labels a user or a lead with a tag, or takes that tag off again, all from one module. Tags are how your team slices contacts in Customerly, so this keeps segments accurate without anyone clicking through profiles.

When to use it
right after a lead is created from a campaign form, to record which campaign brought them in.
Watch out
this module handles the link between a contact and a tag; to remove the tag from the whole project, use Delete a Tag instead.
Customerly2

Create / Update a Lead

Action

In Make“Creates or updates a lead.”

Writes a lead into Customerly: a new one if it is not there yet, an updated one if it already exists. You get a single module for both cases, which keeps scenarios short.

When to use it
a contact form, a webinar signup sheet or a CRM export should feed your Customerly leads without manual copying.
Watch out
run it once on a test contact first and check in Customerly whether it created a fresh lead or updated the one you expected.
Customerly3

Create / Update a User

Action

In Make“Creates or updates a user.”

Does for users what the lead module does for leads: it adds a user to your project or refreshes the details of one already there. Your Customerly records follow what happens in your product or billing tool.

When to use it
someone signs up or changes plan in your app, and support should see the current information when that person writes in.
Watch out
leads and users are separate modules here, so pick the one matching the record you actually want to touch.
Customerly4

Delete a Lead

Action

In Make“Deletes a lead.”

Removes one lead from your Customerly project. Handy for keeping the lead list clean once a contact has no reason to stay, for example after a request to be forgotten.

When to use it
another tool marks a contact as a duplicate or as withdrawn, and the lead should disappear from Customerly too.
Watch out
treat the deletion as final. Test it on a throwaway lead and add a filter before the module so only the right bundles reach it.
Customerly5

Delete a Tag

Action

In Make“Deletes a tag.”

Erases a tag from Customerly altogether, not just from one contact. It is the cleanup step for labels created by old campaigns that nobody filters on anymore.

When to use it
after List Tags has shown you which tags are obsolete and you want them gone in one pass.
Watch out
you are removing a label your team may still filter on. Check the exact name in List Tags before you click Run once.
Customerly6

Delete a User

Action

In Make“Deletes a user.”

Removes a user record from Customerly, so an account closed in your product stops showing up for your support team. One user per bundle, one deletion per run of the module.

When to use it
a customer closes their account in your billing or product tool and asks for their data to be erased.
Watch out
make sure you are pointing at a user, not a lead, and try it on a test profile before switching the scenario on.
Customerly7

Get a Lead

Action

In Make“Gets a lead.”

Fetches the details of one specific lead so later modules can use them. Instead of storing contact data twice, you read it from Customerly the moment the scenario needs it.

When to use it
a message from another app mentions a lead, and you want its full Customerly record before deciding what to do next.
Watch out
it returns one lead only; if you need to go through many, List Leads is the better choice.
Customerly8

Get a User

Action

In Make“Gets a user.”

Pulls a single user record out of Customerly and hands its data to the next modules. Useful as a lookup step in the middle of a scenario, before an update or a notification.

When to use it
the Universal Trigger fires about someone and you want their complete user profile to enrich an alert sent to your team.
Watch out
Get a User reads only users; a contact who is still a lead needs Get a Lead.
Customerly9

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Opens the whole Customerly API to your scenario when none of the ready modules fits. It reuses your existing connection, so there is no second login to manage.

When to use it
you need an endpoint of the Customerly API that the other 12 modules do not expose.
Watch out
here you work with the raw API, so keep the Customerly API reference open and test every call with Run once before activating anything.
Customerly10

List Leads

Search

In Make“Gets all leads.”

Returns all the leads of your project, each one as its own bundle. That lets the next modules process your lead base contact by contact, for an export, a sync or a cleanup.

When to use it
you want to copy your Customerly leads into a spreadsheet or another CRM in one pass.
Watch out
every module placed after it runs once per lead, and each run is an operation counted on your Make plan.
Customerly11

List Tags

Search

In Make“Gets all tags.”

Gives you every tag that exists in your Customerly project, one bundle per tag. It is the audit view you need before any tag cleanup or before syncing labels with another tool.

When to use it
you suspect duplicate or forgotten tags and want the full list in a spreadsheet to review with your team.
Watch out
a search can return zero results; add a filter so modules downstream do not run on nothing.
Customerly12

List Users

Search

In Make“Gets all users.”

Brings back all users of your project, one bundle each, so a scenario can walk through your customer base. Good for reporting or for pushing user data to a tool your finance or product team reads.

When to use it
you need a complete, fresh copy of your Customerly users in a spreadsheet or database.
Watch out
a large base means many bundles, and every module after this one spends one operation per user.
Need help

Need help automating Customerly with Make?

A person reads every message.

FAQ

Questions about the Customerly Make integration

01Is the Customerly Make integration free?
Yes, on the Make side. Customerly is a standard app, so it works from the Free plan. That plan allows 2 active scenarios, runs them at most every 15 minutes, stops each run after 5 minutes, and caps files at 5 MB with 512 MB of data transfer. Paid plans lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes per run. Make counts usage in operations, one per module per bundle. Your Customerly subscription is a separate matter handled by Customerly.
02What do you need to connect Customerly to Make?
An active Customerly account and its API access token. You find the token in Customerly under Project Settings, then Installation, then the Public API section, in the field called Your Access Token for Customerly. In Make, add any Customerly module, click Create a connection, optionally name it, and paste the token. If the first module you add is the Universal Trigger, click Create a webhook before Create a connection. After that, every Customerly module in your scenarios reuses the same connection.
03Does the Customerly trigger in Make fire in real time?
Yes. The Universal Trigger is an instant trigger: Customerly calls Make through a webhook as soon as the entity you attached it to is executed, so the scenario does not wait for a schedule. It is the only trigger in the Customerly app. If you would rather start from something outside Customerly, open the scenario with another app or with a schedule on the first module, then use the Customerly actions and searches after it. New scenarios check every 15 minutes by default.
04What if a Customerly module is missing in Make?
Use Make an API Call. It calls any endpoint of the Customerly API with the connection you already have, so you are not limited to the 12 other modules covering leads, users and tags. Keep the Customerly API reference at hand while you set it up and test each call with Run once. Also note that Make marks its Customerly documentation as AI-generated and possibly inaccurate, so confirm important details directly with Customerly before relying on them in production.
05Should you use Make or n8n with Customerly?
It depends on what you already run. On Make, Customerly ships 13 ready modules: one instant trigger, nine actions and three searches, one of which is Make an API Call for everything else. Many apps also have an n8n node, so check the n8n side for Customerly before you decide rather than assuming it is there. Then compare what each side offers for the exact actions you need, and weigh which tool your team already knows; the n8n vs Make comparison on this site sets the two side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations