Resources · Make integration

Simplero Make integrationAutomate Simplero with Make.

Every purchase, subscription and tag in Simplero can start work somewhere else. The Simplero Make integration gives you 16 modules: 6 instant triggers, 9 actions and 1 search. This guide is for course creators and ops leads who connect their account, then build a first scenario step by step.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Simplero Make integration automate?

The Simplero Make integration links your Simplero account to Make, a visual tool where you build a scenario: the automation itself, a chain of modules where each module is one brick (a trigger, an action or a search). Simplero tells Make when a purchase, a list subscription or a tag changes, and Make updates contacts, tags, lists and purchases for you.

Welcome every buyer without touching a spreadsheet. Watch Purchase Added fires the moment someone buys, then Subscribe to a List files that person on your onboarding list and Add a Tag to the Contact marks them as a customer. Your welcome sequence starts on its own.

Clean up after a refund. When Watch Purchase Deleted fires, Remove a Tag from the Contact takes the buyer tag away and Unsubscribe from a List pulls the person out of the customer emails, so nobody receives content they no longer paid for.

Feed Simplero from your other tools. A signup captured in a form or a CRM can land in Simplero through Create a Contact, or refresh an existing record with Update a Contact. For a sale closed outside Simplero, Create a Purchase records it against the right product.

What the listed modules do not cover, such as an endpoint with no dedicated module, goes through Make an API Call with the same connection. The Simplero documentation in Make gives no quota or special limit, and it warns that its text is AI-generated, so check anything critical with Simplero. If you also weigh n8n, read n8n vs Make. To go further, the Make training covers the editor from scratch, and Make pricing explains how operations are counted.

Connect

How do you connect Simplero to Make?

  1. 01

    Copy your API key in Simplero

    In the Simplero admin, open Settings, then Integrations, and copy the API key shown on screen. Make uses it as Basic Auth credentials. You need an active Simplero account for the key to exist.

  2. 02

    Add a Simplero module in Make

    In your scenario, add any Simplero module and click Create a connection. You can type a label in Connection name, which helps when several Simplero accounts sit in the same Make organization.

  3. 03

    Paste the key and save

    Paste the API key you copied, or follow the instructions Make shows, then confirm. The connection, meaning your Simplero account linked to Make once, is now reused by every Simplero module you add later.

First scenario

Build your first scenario with Simplero

GoalWhen someone buys in Simplero, Make subscribes that buyer to your onboarding list and tags the contact as a customer.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big +. Search for Simplero and pick Watch Purchase Added as the first module.

  2. 02

    Set up the webhook and connection

    Click Create a webhook, then Create a connection and paste your API key. From now on, Simplero calls Make each time a purchase is added.

  3. 03

    Add the list subscription

    Click the + to the right of the trigger and add Subscribe to a List. Pick your onboarding list and map the buyer's email from the purchase bundle, the item the trigger passed along.

  4. 04

    Tag the buyer

    Add Add a Tag to the Contact after it. This module finds the contact by email, so map the same email again and choose the customer tag you want.

  5. 05

    Test with Run once

    Click Run once, then place a test purchase in Simplero. Open each module's bubble to read the bundles it received and check the list and tag on the contact.

  6. 06

    Switch it on

    Save the scenario and turn it on. Because the trigger is instant, every new purchase now runs the scenario, and each module that executes counts as one operation on your Make plan.

Triggers

Simplero triggers: what starts your scenario

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

Simplero1Watch Purchase Added

Watch Purchase Added

Instant trigger

In MakeTriggers when a new purchase is added.

You get a scenario that starts the second a new purchase appears in Simplero, carrying the purchase details as a bundle for the next modules. It is the natural starting point for onboarding, receipts sent from another tool or a sale logged in your books.

How it fires
instant: Simplero calls Make through a webhook as soon as the purchase is added, with no polling interval.
When to use it
when a buyer should reach a list, a tag or a welcome sequence right after checkout.
Watch out
click Create a webhook before Create a connection, or the trigger never hears from Simplero.
Simplero2Watch Purchase Deleted

Watch Purchase Deleted

Instant trigger

In MakeTriggers when a purchase is deleted.

This trigger lets you undo what a purchase set up, because Simplero warns Make whenever a purchase is removed. Map what the bundle carries into the next modules, so the cleanup targets the right person.

How it fires
instant: Simplero calls Make through a webhook as soon as the purchase is deleted.
When to use it
after a refund or a cancelled order, to remove the customer tag and take the person off buyer-only lists.
Watch out
it reacts to deletions only; a purchase that simply changes does not start the scenario.
Simplero3Watch Subscription Added

Watch Subscription Added

Instant trigger

In MakeTriggers when a contact is subscribed to the list.

Here the start signal is a contact joining a list, so your scenario can greet a new lead or copy them into another tool the moment they sign up. Make receives the subscription as a bundle and passes the contact on to whatever comes next.

How it fires
instant: Simplero calls Make through a webhook as soon as the contact is subscribed.
When to use it
a lead magnet list whose new members should also land in your CRM or a team spreadsheet.
Watch out
the trigger follows list subscriptions, not purchases; a buyer who never joins a list stays invisible to it.
Simplero4Watch Subscription Deleted

Watch Subscription Deleted

Instant trigger

In MakeTriggers when a contact is unsubscribed from the list.

Your other tools stay in step with Simplero when someone leaves a list, because this trigger reports every unsubscribe to Make. That keeps a CRM or an ad audience from targeting people who already said no to your emails.

How it fires
instant: Simplero calls Make through a webhook as soon as the contact is unsubscribed.
When to use it
when an opt-out in Simplero must also update a status field in your CRM or remove the person from a sync.
Watch out
avoid pairing it with Subscribe to a List on the same list, or you rebuild what the reader just left.
Simplero5Watch Tag Added

Watch Tag Added

Instant trigger

In MakeTriggers when a tag is added to the contact.

Tags become switches: the moment a tag lands on a contact, Make receives that contact and your scenario can act on it. If you already tag contacts by interest or progress, this trigger turns that habit into automation without new forms.

How it fires
instant: Simplero calls Make through a webhook as soon as the tag is added to the contact.
When to use it
a tag such as completed-module-one that should notify a coach or open a task in a project tool.
Watch out
it most likely fires for every tag added, including tags your own scenario adds through Add a Tag to the Contact, so filter on the tag you care about.
Simplero6Watch Tag Removed

Watch Tag Removed

Instant trigger

In MakeTriggers when a tag is removed from the contact.

The mirror of the previous trigger: you learn in Make that a tag left a contact, and your scenario can close whatever that tag had opened. The contact comes through as a bundle, ready to be mapped into the next module.

How it fires
instant: Simplero calls Make through a webhook as soon as the tag is removed from the contact.
When to use it
when losing a VIP or trial tag should also revoke access or update a record in another app.
Watch out
Remove a Tag from the Contact in another scenario will start this one too; check that the two do not chain into a loop.
Modules

Simplero modules: what each one does

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

Simplero1

Add a Tag to the Contact

Action

In MakeAdds a tag to the contact with the given email.

Puts a tag on a contact you point to by email, which is the quickest way to segment people in Simplero from any scenario. Another scenario can then react to it through Watch Tag Added.

When to use it
right after a purchase, a form entry or a call booked in another tool.
Watch out
the lookup is by email, so map a clean address; a typo means the wrong contact or none at all.
Simplero2

Create a Contact

Action

In MakeCreates a new contact.

Adds a brand-new person to your Simplero contacts, so leads captured elsewhere stop living in a separate tool. Everything else, from tags to lists, can follow in the next modules.

When to use it
a webinar signup or a CRM lead that should exist in Simplero before any email goes out.
Watch out
if the person may already exist, Update a Contact is the safer choice, since it works on the contact with the same email.
Simplero3

Create a Purchase

Action

In MakeCreates a new purchase for a selected product.

Records a purchase of a product you select, so a sale paid outside Simplero still shows up on the contact in Simplero.

When to use it
a deal paid through an invoice tool or a bank transfer that should appear in Simplero like any other sale.
Watch out
the doc does not say whether this purchase also starts Watch Purchase Added; if a scenario uses both, test it with Run once and add a filter if it loops.
Simplero4

Get a Contact

Action

In MakeGets an information about the contact, looked up by the internal ID or email.

Fetches one contact's details from Simplero, found by internal ID or by email, so later modules can use data the trigger did not carry. Think of it as a lookup before a decision.

When to use it
before sending a message from another tool, to check who the person is in Simplero.
Watch out
when nobody matches the email, the following modules have nothing to work with; add a filter after it.
Simplero5

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Opens the whole Simplero API from your scenario, with the connection you already set up, for everything the other fifteen modules leave out. You write the request yourself, so it suits someone at ease with the Simplero API.

When to use it
an object or action with no dedicated module in the list.
Watch out
test each request with Run once and read the bundle it returns before you switch the scenario on.
Simplero6

Remove a Tag from the Contact

Action

In MakeRemoves a tag from the contact with the given email.

Takes a tag off a contact identified by email, which ends whatever that tag was driving in Simplero. It is the tidy counterpart to Add a Tag to the Contact.

When to use it
after a refund, a finished trial or a lead who moved to another stage.
Watch out
if a scenario listens with Watch Tag Removed, this removal will most likely start it too; check with Run once that the two do not loop.
Simplero7

Subscribe to a List

Action

In MakeAdds a new subscriber to a list.

Adds a person to one of your Simplero lists, so they start getting the emails tied to it. For most course sellers, this is the action that turns a buyer or lead into a reader.

When to use it
a purchase, a booked call or a form in another app that should begin a nurture sequence.
Watch out
List Subscriber Lists shows which lists exist if you are unsure of the right one.
Simplero8

Unsubscribe from a List

Action

In MakeUnsubscribes a customer from a list.

Removes a customer from a list, which stops the emails of that list for them while leaving the contact in place. You pick it over a full cleanup when only one sequence should end.

When to use it
moving a buyer out of the prospect list once Watch Purchase Added has fired.
Watch out
Watch Subscription Deleted will most likely react to this action too, so test both together if they sit in your scenarios.
Simplero9

Update a Contact

Action

In MakeUpdates an existing contact with the same email.

Refreshes an existing Simplero contact that shares the email you send, keeping names and details in line with your other tools. No duplicate is created when the person is already there.

When to use it
a CRM change or a profile form that should rewrite what Simplero knows.
Watch out
the match relies on the email; if the address itself changed elsewhere, the update will not find the old record.
Simplero10

List Subscriber Lists

Search

In MakeReturns all the account's lists.

Returns every list in your Simplero account, one bundle per list, so a scenario can loop through them or you can see what exists before choosing. It is the only search module of the app.

When to use it
building a sync that copies list names into a spreadsheet, or checking list names while testing.
Watch out
one bundle per list means the next module runs once per list, and each run counts as an operation.
Need help

Need help automating Simplero with Make?

A person reads every message.

FAQ

Simplero and Make: frequently asked questions

01Is the Simplero Make integration free?
Yes, on the Make side. Simplero is a standard app, so it is available from the Free plan, like the 3000+ standard apps Make offers on every plan. The Free plan gives you 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lift those limits and count usage in operations each month. Your Simplero subscription is separate, and the API key only exists on an active Simplero account.
02What do you need to connect Simplero to Make?
An active Simplero account and its API key. In the Simplero admin, go to Settings, then Integrations, and copy the key shown there. In Make, add any Simplero module, click Create a connection, give it a name if you like and paste the key; Make uses it as Basic Auth. For a Watch module, click Create a webhook first and then Create a connection. The same connection then serves all 16 Simplero modules, including Make an API Call.
03Do Simplero triggers in Make react in real time?
Yes. All 6 Simplero triggers are instant: Simplero calls Make through a webhook as soon as a purchase is added or deleted, a contact joins or leaves a list, or a tag is added or removed. There is no polling interval to set, unlike scheduled triggers, which Make checks every 15 minutes by default. Each event that reaches the scenario still uses operations for every module it runs, so a busy store consumes more of the plan than a quiet one.
04What if a Simplero module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Simplero API with the connection you already have, so an object or action outside the 15 other modules is still within reach. You write the request yourself from the Simplero API reference. The Simplero documentation in Make lists no specific quota or limit; it does say its text is AI-generated and may contain mistakes, so confirm anything important with Simplero before you rely on it.
05Should you use Make or n8n for Simplero?
It depends on which tool the rest of your stack already runs in. The facts on the Make side: 16 Simplero modules, 6 instant triggers, and Make an API Call for the rest, all available from the Free plan. Many apps also have an n8n node, but this guide does not confirm one for Simplero, so check the n8n catalog before choosing. The n8n vs Make comparison linked above sets out the criteria without ranking either tool.