Resources · Make integration

SlimEmail Make integrationAutomate SlimEmail with Make.

Tired of copying new sign-ups into SlimEmail by hand? The SlimEmail Make integration gives you 7 action modules to manage subscribers and campaigns from any scenario. This guide shows what each one does, how to link your account and how to build a first working flow.

Try the SlimEmail integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the SlimEmail Make integration do for you?

The SlimEmail Make integration lets Make act on your SlimEmail account for you: add or remove subscribers, check where someone stands, count your audience and create campaigns. Make runs this inside a scenario, which is the automation you build as a chain of bricks called modules.

Every sign-up lands in SlimEmail. A form, a shop or a CRM in another app starts the scenario, and Add a Subscriber puts the person into SlimEmail without anyone copying an address.

Opt-outs stay in sync. When a customer asks to stop hearing from you in your support tool, Unsubscribe a User records it in SlimEmail, and Get a Subscriber Status lets you confirm it before another step runs.

A campaign starts from an event. A new product entry or an approved brief elsewhere can trigger Create a Campaign, and Get a Subscriber Count tells the rest of the scenario how large the audience is.

Know the limit before you start: SlimEmail has no trigger module, so the scenario always starts from another app or from a schedule, and the official documentation is thin. Make itself says it cannot document SlimEmail fully, so test each module with Run once to see what it asks for. If you are still weighing tools, the Make review and the n8n vs Make comparison help, and Make training covers the editor step by step.

Connect

How do you connect SlimEmail to Make?

  1. 01

    Add a SlimEmail module

    In your scenario, click the +, search for SlimEmail and pick any of its modules. Then click Create a connection. A connection is your SlimEmail account linked to Make once and reused by every SlimEmail module.

  2. 02

    Name the connection

    This step is optional, but a clear name helps when you manage several accounts. Something like the name of the list owner or the brand makes it easy to pick the right one later in a crowded scenario.

  3. 03

    Authorize and save

    Depending on what SlimEmail offers, you either approve Make on the SlimEmail page or paste the key SlimEmail gives you. Click Save, and the module fields become available right away.

First scenario

Your first scenario with SlimEmail

GoalWhen someone signs up in another app, Make adds them to SlimEmail and checks their status.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. The first module must come from the app where sign-ups happen, since SlimEmail has no trigger of its own.

  2. 02

    Pick the starting app

    Search for your form or shop tool, choose its trigger and link your account. Each new sign-up it sends becomes a bundle, meaning one item passed from one module to the next.

  3. 03

    Add the subscriber

    Click the + on the right, add Add a Subscriber from SlimEmail, create the connection, then map the sign-up details from the previous module into the fields it shows.

  4. 04

    Check the result

    Add Get a Subscriber Status after it and map the same contact. Later steps can then react to what SlimEmail says about that person instead of assuming the insert worked.

  5. 05

    Test with Run once

    Click Run once and submit a test sign-up. Open the bubble above each module to read the bundles it received, and fix any mapping that came through empty.

  6. 06

    Schedule and switch on

    Set the schedule on the first module (a new scenario checks every 15 minutes by default) if your starting trigger is a scheduled one, then turn the scenario on. From then on, each sign-up flows into SlimEmail by itself.

Modules

What each SlimEmail module does

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

SlimEmail1

Add a Subscriber

ActionIn the docs only

This one puts a new person into your SlimEmail audience, so contacts collected anywhere else end up ready for your next send without a manual import.

When to use it
right after a form submission, a purchase or a new CRM contact coming from another app.
Watch out
the documentation does not list its fields, so run it once with a test address and read what comes back.
SlimEmail2

Create a Campaign

ActionIn the docs only

With this module a campaign gets set up in SlimEmail from inside your scenario, which saves you rebuilding the same draft by hand whenever content is ready elsewhere.

When to use it
when an event in another tool, such as a published article or an approved brief, should lead to a new mailing.
Watch out
test it once and open the result in SlimEmail before letting it run on real content.
SlimEmail3

Delete a Subscriber

ActionIn the docs only

You get a clean list: judging by its name, this module removes the person from SlimEmail rather than just unsubscribing them. That fits a data removal request.

When to use it
when someone asks to be erased, not just to stop receiving emails; for a simple opt-out, prefer Unsubscribe a User.
Watch out
a deletion cannot be undone from Make, so test it on a dummy contact first and put a check before it.
SlimEmail4

Get a Subscriber Count

ActionIn the docs only

This returns how many subscribers you have, giving the rest of the scenario a number it can write to a sheet, post in a team chat or compare against a threshold.

When to use it
when a report or a decision in the scenario depends on the size of your audience.
Watch out
it reads, it does not change anything, but each run still counts as one operation, meaning one module execution billed on your plan.
SlimEmail5

Get a Subscriber Status

ActionIn the docs only

Here you find out where one person stands in SlimEmail before acting, so the scenario avoids adding someone twice or writing to a contact who opted out.

When to use it
as a check placed before Add a Subscriber, or after it to confirm the insert went through.
Watch out
read the status it returns during your Run once test before you let later modules depend on it.
SlimEmail6

Make an API Call

ActionIn the docs only

Anything the six other modules leave out can still be reached: this one calls any endpoint of the SlimEmail API with the connection you already set up.

When to use it
when a task you need has no dedicated module in the list above.
Watch out
you need to know the endpoint and its parameters from SlimEmail's own material, because Make's documentation of the app is limited.
SlimEmail7

Unsubscribe a User

ActionIn the docs only

Your opt-outs are honored everywhere: this module unsubscribes a person in SlimEmail so they stop getting your sends.

When to use it
when a customer clicks a stop link in another tool or tells your support team they want no more emails.
Watch out
it is not a deletion; if the request is to erase all data, use Delete a Subscriber instead and confirm with Get a Subscriber Status.
Need help

Need help automating SlimEmail with Make?

A person reads every message.

FAQ

SlimEmail and Make: common questions

01Is the SlimEmail Make integration free?
Yes, SlimEmail is a standard app in Make, so it works on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, lift the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations per month. Your SlimEmail subscription is a separate matter.
02What is needed to connect SlimEmail to Make?
A SlimEmail account and a Make account. Make's documentation lists no specific prerequisite for SlimEmail and gives no dedicated connection steps, so the generic flow applies: add a SlimEmail module, click Create a connection, optionally name it, then either authorize Make on SlimEmail's page or paste the key SlimEmail provides, and click Save. The connection is then reused by all 7 SlimEmail modules in any scenario you build, so you only set it up one time.
03Can SlimEmail start a Make scenario in real time?
No, SlimEmail has no trigger module in Make, so it cannot start a scenario by itself. You start the flow another way. The first option is a trigger from another app, such as a form tool or a shop, which hands each new item to the SlimEmail modules. The second option is a schedule set on the first module: a new scenario runs every 15 minutes by default, and the Free plan does not go below that interval, while paid plans go down to 1 minute.
04What if a SlimEmail module is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the SlimEmail API with the connection you already created, which covers what the other 6 modules do not. The catch is that Make says its SlimEmail documentation is incomplete, for lack of public information about the app. You will need the endpoint details from SlimEmail itself, and a Run once test with a sample contact is the quickest way to check the answer before switching the scenario on.
05Is Make or n8n the better fit for SlimEmail?
It depends on which tool you already work in. On Make, SlimEmail comes with 7 action modules, a guided connection and Make an API Call for the rest, which suits someone who prefers building visually from a list of ready modules. Many apps also have an n8n node, so check whether one exists for SlimEmail before deciding. Compare the two on what matters to your team: the modules you need, where your other apps already run, and who will maintain the scenarios.
Same platform

Other docs you might need on this stack.

Browse all integrations