Resources · Make integration

AcyMailing Make integrationAutomate AcyMailing with Make.

Can Make keep your AcyMailing subscribers in step with your other tools? Yes. The AcyMailing Make integration offers 4 triggers and 6 actions for new, confirmed or departing users. This guide links your account and builds a first scenario with you.

Try the AcyMailing integration on MakeSee the 10 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the AcyMailing Make integration do?

The AcyMailing Make integration links your AcyMailing account to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules that each do one job. AcyMailing brings 10 modules, 4 scheduled triggers that notice changes among your users and 6 actions that create, update, subscribe, email or delete them.

Greet readers who really opted in. Watch Confirmed Users spots each person who confirms their email address. Right after it, Subscribe a User can place them on a members list, or Send an Email to a User can welcome them one by one.

Feed AcyMailing from the rest of your stack. When a contact form or an online shop hands over a new person, Add a User or Update a User writes the record, or refreshes it when the address is already known. Your database stays free of duplicates.

Tidy up after a departure. Watch Unsubscribed Users tells you who left, so a CRM can be updated. In the other direction, Unsubscribe a User and Delete a user apply a decision taken in another tool.

The AcyMailing documentation gives no specific limit for these modules. Whatever the six actions leave out, Make an API Call can reach through the same connection. To weigh your options, read n8n vs Make and Make pricing, or learn the editor step by step with Make training.

Connect

How do you connect AcyMailing to Make?

  1. 01

    Copy your API key

    In your AcyMailing account dashboard, open Licenses and copy the API key shown for your license. The documentation asks for an AcyMailing Essential account or higher, with the REST API activated.

  2. 02

    Create the connection

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

  3. 03

    Name it and paste the key

    Type a label you will recognize in the optional Connection name field, for example the site the list belongs to. Paste the credentials copied from AcyMailing, or follow the on-screen instructions, then save.

First scenario

Build your first scenario with AcyMailing

GoalWhen a user confirms their email address in AcyMailing, Make subscribes them to the list you choose.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Search for AcyMailing and pick Watch Confirmed Users.

  2. 02

    Link your account

    Click Create a connection and paste your API key. Then fill the module fields: once the connection exists, Make lists what it can read in AcyMailing.

  3. 03

    Add the subscription

    Click the + on the right of the trigger, choose AcyMailing again and pick Subscribe a User. Map the user from the previous module, then select the list that should receive them.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Open each module to read the bundles it received, a bundle being one item passed along, here one user.

  5. 05

    Schedule and switch on

    Set the schedule on the first module: a new scenario runs every 15 minutes by default, the shortest interval on the Free plan. Then switch the scenario on.

Triggers

Which AcyMailing triggers can start a scenario?

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

AcyMailing1Watch Confirmed Users

Watch Confirmed Users

Scheduled trigger

In Make“Triggers when an AcyMailing user confirms their email address.”

You get the people who have just proved their address works: this trigger picks up each AcyMailing user who confirms their email and hands them to the next module as a bundle. It is the natural starting point for anything aimed at engaged readers.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, so a confirmation appears at the next check rather than the moment it happens.
When to use it
when a double opt-in signup should unlock something, such as a place on a members list.
Watch out
every confirmed user that passes through costs one operation in each module that follows, so keep the chain short while testing.
AcyMailing2Watch New Users

Watch New Users

Scheduled trigger

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

This trigger brings you every user freshly created in AcyMailing, confirmed or not. Choose it when you want to hear about every new record, at the next check, before the person has done anything else.

How it fires
scheduled: Make polls AcyMailing each time the scenario runs, following the clock set on the first module.
When to use it
when a sales or support tool needs a copy of each new contact, including people still waiting to confirm.
Watch out
a scenario that also contains Add a User or Update a User creates users this trigger is watching for, so keep those two in separate scenarios to avoid a loop.
AcyMailing3Watch Subscribed Users

Watch Subscribed Users

Scheduled trigger

In Make“Triggers when an AcyMailing user is subscribed to a list.”

Here you receive each AcyMailing user added to a list. You learn who joined, and also where. Pick it when each of your lists has its own meaning: one per product, say, or one per event.

How it fires
scheduled, with Make checking AcyMailing at the rhythm of the scenario's schedule instead of being notified.
When to use it
when joining one specific list should open a task or a record in another tool.
Watch out
it reacts to subscriptions, not to confirmations; for readers who confirmed their address, Watch Confirmed Users is the better fit.
AcyMailing4Watch Unsubscribed Users

Watch Unsubscribed Users

Scheduled trigger

In Make“Triggers when an AcyMailing user unsubscribes.”

This one surfaces the people who leave: each time an AcyMailing user unsubscribes, the trigger passes them on so the rest of your tools can respect that choice. It is the building block for keeping a CRM in line with your mailing list.

How it fires
scheduled. Make looks for unsubscribes on the scenario's schedule, so the news reaches the next module at the following run.
When to use it
when a CRM or a spreadsheet should flag who no longer wants your emails.
Watch out
the trigger only reports the departure; updating or stopping messages in other tools is the job of the modules you add after it.
Modules

What can Make do in AcyMailing?

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

AcyMailing1

Add a User or Update a User

Action

In Make“Creates a user or updates it if they already exist.”

One module handles both cases: it creates the AcyMailing user when the address is new and updates the record when it already exists. You skip a separate lookup before every write, and duplicates stay out.

When to use it
when leads arrive from a form, a shop or a spreadsheet and should land in AcyMailing whether or not they are already known.
AcyMailing2

Delete a user

Action

In Make“Deletes a user from your AcyMailing database.”

This action removes a user from your AcyMailing database altogether, rather than simply taking them off a list. It is the module for a real clean-up, when a record should no longer exist.

When to use it
when someone asks for their data to be erased, or when a test contact slipped into your real lists.
Watch out
to keep the record and only stop the emails, Unsubscribe a User is the gentler choice.
AcyMailing3

Make an API Call

Action

In Make“Performs an arbitrary API call to your website.”

When no other module does what you need, this one sends a request of your own to the AcyMailing API, reusing the connection you already created. Any endpoint of the API is within reach from the scenario.

When to use it
for an AcyMailing feature that the other five actions do not cover.
Watch out
you write the request yourself, which makes it the most technical module on this page.
AcyMailing4

Send an Email to a User

Action

In Make“Sends an email to a single AcyMailing user.”

This action sends an email to one AcyMailing user at a time, which suits a personal message better than a campaign to a whole list. Each bundle that reaches it produces one email.

When to use it
right after a confirmation, to greet the new reader, or when a status changes in another tool.
Watch out
each email is one operation, so a trigger that brings many users multiplies the count on your plan.
AcyMailing5

Subscribe a User

Action

In Make“Subscribes a user to the given list(s).”

Use it to put a user on one list or several lists in a single step, which is how a person moves into the right audience without anyone touching AcyMailing by hand.

When to use it
when a purchase, a webinar signup or a confirmed address should place someone in a dedicated list.
Watch out
paired with Watch Subscribed Users in the same scenario, it feeds the trigger its own subscriptions; keep the two apart.
AcyMailing6

Unsubscribe a User

Action

In Make“Unubscribes a user from the given list(s).”

This action takes a user off one list or several, the mirror image of Subscribe a User. Unlike Delete a user, it works on list memberships and leaves the rest alone.

When to use it
when a customer cancels a subscription in your billing tool and should stop receiving the matching newsletter.
Watch out
pick the exact lists concerned, or the person may drop out of lists they still want.
Need help

Need help automating AcyMailing with Make?

A person reads every message.

FAQ

AcyMailing and Make: common questions

01Is the AcyMailing Make integration free?
Yes, on the Make side. AcyMailing is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum interval of 15 minutes between scheduled runs, 5 minutes of execution at most and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution, with usage counted in credits each month. On the AcyMailing side, the documentation requires an Essential account or higher, so check that plan as well.
02What do you need to connect AcyMailing to Make?
Three things: an active AcyMailing Essential account or higher, the REST API activated in AcyMailing, and the API key displayed under Licenses in your account dashboard. In Make, add any AcyMailing module, click Create a connection, give it a name if you like and paste the key. The connection is then shared by every AcyMailing module in your scenarios, so this setup happens once per account. If you manage several AcyMailing sites, create one connection for each and name them clearly.
03Do AcyMailing triggers in Make fire in real time?
No. All 4 AcyMailing triggers are scheduled: Make checks AcyMailing on the scenario's schedule instead of receiving a webhook call. A new scenario checks every 15 minutes by default, which is also the shortest interval on the Free plan, while paid plans go down to 1 minute. A confirmation, a new subscription or an unsubscribe therefore reaches your scenario at the next check. A paid plan shortens that wait, but with these modules it never becomes instant.
04What if an AcyMailing module is missing in Make?
Use Make an API Call. With that module, any endpoint of the AcyMailing API can be called from your scenario, through the same connection as the other modules. It covers what the 6 ready-made actions leave out, at the cost of writing the request yourself. The AcyMailing documentation in Make gives no specific limit for these modules, and it notes that its content is AI-generated from the official AcyMailing documentation, so verify important details and contact AcyMailing directly about their own documentation.
05Should you use Make or n8n for AcyMailing?
It depends on your criteria rather than on AcyMailing alone. On Make, you get 10 ready-made AcyMailing modules, a visual editor and a Free plan to test your first scenario. n8n often has a node for the same app, so check whether AcyMailing is covered there before deciding. No ranking is given here on price or performance between the two: the n8n vs Make comparison on this site lays out the criteria side by side, and you can match them to how your team works.
Same platform

Other docs you might need on this stack.

Browse all integrations