Resources · Make integration

Mautic Make integrationAutomate Mautic with Make.

Can your Mautic contacts keep themselves up to date? The Mautic Make integration gives you 26 modules: 1 instant trigger, 21 actions and 4 searches. This page is for marketers who run Mautic and want leads, segments and stages handled without copy and paste.

Try the Mautic integration on MakeSee the 26 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Mautic Make integration let you automate?

The Mautic Make integration links your Mautic account to Make, a visual tool where you build a scenario (the automation itself) out of modules (one brick each: a trigger, an action or a search). Mautic becomes one link in a chain: contacts come in from other apps, move between segments and stages, and send events back out.

Every new lead lands in the right segment. A form tool or a spreadsheet starts the scenario, Create/Update a Contact writes the person into Mautic, and Add Contact to a Segment drops them into the list your campaign already targets. The same e-mail twice updates the existing contact instead of creating a duplicate.

Your pipeline follows the sales team. When a deal moves in your CRM, Add Contact to a Stage or Remove Contact from a Stage keeps the Mautic stage in line, so scoring and campaigns see the same picture as sales.

Mautic talks to the rest of your tools. Watch Events is an instant trigger: Mautic calls Make the moment the event you picked happens, and the next modules can post it to a chat channel or a shared table.

What the app does not cover: there is a single trigger, and nothing reads e-mails, campaigns or forms directly. For anything else the Mautic API offers, Make an API Call uses the same connection. The same app also has an n8n node, described on the Mautic n8n integration page, and the n8n vs Make comparison helps you pick a tool. If Make itself is new to you, start with the Make training.

Connect

How do you connect Mautic to Make?

  1. 01

    Create an API application in Mautic

    Your Mautic account needs API access turned on. In Mautic, open Settings in the sidebar, then API Settings, and click Add New. Paste https://www.integromat.com/oauth/cb/mautic as the callback URI.

  2. 02

    Copy the two credentials

    Mautic now shows a Client ID and a Client secret. Copy both somewhere safe: you paste them into Make in the next step.

  3. 03

    Create the connection in Make

    Add any Mautic module to a scenario and click Create a connection. Name it in Connection name if you like, paste the two credentials, and follow the on-screen steps. The connection (your Mautic account linked to Make) is reused by every Mautic module.

First scenario

Your first scenario: new leads into a Mautic segment

GoalWhen a new lead arrives in another app, Make creates or updates the contact in Mautic and adds it to a segment.

  1. 01

    Start from the lead source

    On the Scenarios page, create a new scenario and click the +. Pick the trigger of the app where leads show up first, such as your form tool or a sheet, and connect it.

  2. 02

    Add Create/Update a Contact

    Click the + to the right, search Mautic and choose Create/Update a Contact. Link your account with Create a connection, then map the e-mail and name coming from the first module.

  3. 03

    Drop the contact into a segment

    Add Add Contact to a Segment after it. Map the contact returned by the previous module, then choose the segment: once the connection exists, Make lists what it can read from Mautic.

  4. 04

    Test with Run once

    Submit one test lead, then click Run once. Open the bubbles above each module to read the bundles (the items passed along) and check the contact in Mautic.

  5. 05

    Schedule and switch it on

    Open the clock on the first module. A new scenario runs every 15 minutes by default if that trigger is scheduled. Save, then flip the switch to turn the scenario on.

Triggers

What can start a scenario from Mautic?

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

Mautic1Watch Events

Watch Events

Instant trigger

In Make“Triggers when a new event given by the selection parameter is occured.”

This trigger starts your scenario when the Mautic event you select in the module happens, and hands its data to the next modules. It is the only way Mautic itself kicks off a scenario, so it is where any Mautic-first automation begins.

How it fires
instant, Mautic calls Make through a webhook as soon as the event happens.
When to use it
you want a Slack message, a CRM update or a row in a table right after something happens on the Mautic side.
Watch out
the module asks for Create a webhook before Create a connection. Pick the event carefully in the module, since it decides what the whole scenario reacts to.
Modules

What can Make do in Mautic?

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

Mautic1

Add Contact to a Segment

Action

In Make“Adds a contact to a specific segment.”

Puts an existing contact into one of your segments, so the campaigns and e-mails that target that list reach them too.

When to use it
right after a lead is created or qualified, to send them into the nurture sequence that fits their interest.
Watch out
the contact must already exist, so place Create/Update a Contact or Search Contacts before it.
Mautic2

Add Contact to a Stage

Action

In Make“Adds a contact to a specific stage.”

Moves a contact into a stage of your Mautic lifecycle, the place where you track how far each person has gone from lead to customer.

When to use it
a deal is won in your CRM or an invoice is paid, and Mautic should reflect that new status for scoring and follow-up.
Watch out
the stage has to exist first; List Stages helps you find it.
Mautic3

Create a Segment

Action

In Make“Creates a new segment.”

Builds a brand new segment in Mautic from a scenario, ready to receive contacts from the modules that follow.

When to use it
each new webinar, event or product launch in your planning tool should get its own list in Mautic without anyone clicking through the settings.
Watch out
run it once per new list, not per contact, or you will end up with piles of look-alike segments.
Mautic4

Create a Stage

Action

In Make“Creates a new stage.”

Adds a new stage to your Mautic lifecycle so contacts can later be placed in it with Add Contact to a Stage.

When to use it
your sales process gains a step, for instance a demo or a trial, and you keep the list of stages in another tool that should drive Mautic.
Watch out
stages are a shared structure; check List Stages first so the scenario does not add a second copy.
Mautic5

Create/Update a Company

Action

In Make“Creates a new company. If the company with the same company's name already exists, it is updated.”

Writes a company record in Mautic, and if a company with the same name is already there, it updates that one instead of adding a twin.

When to use it
a new account is signed in your CRM or billing tool, and marketing needs the firm in Mautic to group its people.
Watch out
matching is on the company name, so "Acme" and "Acme Inc" become two records.
Mautic6

Create/Update a Contact

Action

In Make“Creates a new contact. If the contact with the same e-mail already exists, it is updated.”

The workhorse of most Mautic scenarios: it creates a contact, or updates the existing one when the same e-mail address is already in Mautic.

When to use it
any lead source, from a form to an event sign-up list, feeding people into Mautic without creating duplicates.
Watch out
the e-mail is the matching key, so a lead with a missing or mistyped address lands as a separate contact.
Mautic7

Delete a Company

Action

In Make“Deletes a company.”

Removes a company record from Mautic, which keeps your company list clean when an account closes or turns out to be a duplicate.

When to use it
an account is marked as closed or merged in your CRM, and Mautic should stop showing it.
Watch out
treat the deletion as final. Test the scenario on a dummy company before pointing it at real data.
Mautic8

Delete a Contact

Action

In Make“Deletes a contact.”

Erases a contact from Mautic, the step you need when a person asks to be forgotten or when a test lead slipped into production.

When to use it
a data deletion request is logged in your helpdesk or a ticket form, and Mautic must follow suit.
Watch out
treat the deletion as final; find the contact with Search Contacts and check the ID before deleting.
Mautic9

Delete a Segment

Action

In Make“Deletes a segment.”

Removes a whole segment from your Mautic account when a list has served its purpose.

When to use it
an event or a promotion is over and the dedicated list created for it has no reason to stay in your account.
Watch out
check what still relies on that list, and confirm with Get a Segment which list you are about to remove.
Mautic10

Delete a Stage

Action

In Make“Deletes a stage.”

Takes a stage out of your Mautic lifecycle when your funnel drops a step.

When to use it
the sales team retires a step of its process in the tool that holds your reference list, and Mautic should mirror the change.
Watch out
look at who sits in that stage first, and move them with Add Contact to a Stage if they need a new home.
Mautic11

Get a Company

Action

In Make“Gets an individual company by ID.”

Fetches one company by its Mautic ID and returns its details to the next modules, so you can copy them into another tool.

When to use it
an event or a previous module gave you a company ID, and you need the full record to enrich a CRM entry or a report.
Watch out
it needs the ID, not the name; if you only know the name, go through List Companies.
Mautic12

Get a Contact

Action

In Make“Gets an individual contact by ID.”

Reads a single contact by ID and brings back its data, handy when the previous step only gave you a number.

When to use it
an earlier module handed you a contact ID, and the next step needs the person's name and e-mail to post a message or fill a sheet.
Watch out
an ID only; when all you have is an e-mail address, Search Contacts is the better pick.
Mautic13

Get a Segment

Action

In Make“Gets an individual segment by ID.”

Returns the details of one segment from its ID, a quick check before you act on the list.

When to use it
before a delete or an update, to confirm the scenario is holding the right segment and to pass its name to a notification.
Watch out
without the ID, start with List Segments and filter to the one you need.
Mautic14

Get a Stage

Action

In Make“Gets an individual stage by ID.”

Looks up one stage by its ID and gives its details to the rest of the scenario.

When to use it
a report or a message should show the stage name in plain words rather than a bare number coming from an earlier module.
Watch out
like the other Get modules it works on the ID only; List Stages is the way in when you start from nothing.
Mautic15

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Your escape hatch: it calls any endpoint of the Mautic API with the connection you already set up, so anything the listed modules miss stays reachable.

When to use it
the job you have in mind matches none of the other Mautic modules, for instance anything beyond contacts, companies, segments and stages.
Watch out
you write the request yourself, so keep the Mautic API reference open while filling it in.
Mautic16

Remove Contact from a Segment

Action

In Make“Removes contact from a specific segment.”

Pulls a contact out of a segment, so the campaigns aimed at that list stop counting them in.

When to use it
a trial user becomes a paying customer, and the onboarding list for prospects no longer fits them.
Watch out
the contact keeps every other segment; if a switch is intended, pair this with Add Contact to a Segment.
Mautic17

Remove Contact from a Stage

Action

In Make“Removes contact from a specific stage.”

Takes a contact off their current stage without deleting anything else about them.

When to use it
a deal is lost or reopened in your CRM, and the contact should no longer sit in the stage that says otherwise.
Watch out
removing is not moving; to land them somewhere new, follow up with Add Contact to a Stage in the same scenario.
Mautic18

Update a Company

Action

In Make“Updates an existing company.”

Changes the details of a company that already exists in Mautic, with values coming from another tool.

When to use it
your CRM holds the reference data, and a change made there should reach Mautic too.
Watch out
unlike Create/Update a Company, it never creates anything, so it expects a company that is already there.
Mautic19

Update a Contact

Action

In Make“Updates an existing contact.”

Edits a contact Mautic already knows, with details that changed in another tool.

When to use it
you have the contact ID from Search Contacts or Watch Events and want to change only that person, never create one.
Watch out
if the source may bring brand new people too, Create/Update a Contact handles both cases in one module.
Mautic20

Update a Segment

Action

In Make“Updates an existing segment.”

Renames or edits a segment that already exists, so your lists keep names people can recognize.

When to use it
an event is renamed in your planning tool, and its Mautic list should carry the new title.
Watch out
the scenario needs the segment ID; Get a Segment or List Segments gives it to you first.
Mautic21

Update a Stage

Action

In Make“Updates an existing stage.”

Edits a stage that already exists in your lifecycle, so its wording keeps up with how your team talks about the funnel.

When to use it
your team rewords a step of the funnel in its shared reference, and Mautic should use the same wording.
Watch out
Create a Stage adds a new step, this one changes an old one; picking the wrong module leaves a duplicate.
Mautic22

List Companies

Search

In Make“Returns a list of all companies available to the user.”

Returns every company your Mautic user can see, each one as a separate bundle for the next module.

When to use it
you want to copy your company base into a sheet or check which accounts exist before creating new ones.
Watch out
each company counts as an operation in the modules that follow, so add a filter after it on a large base.
Mautic23

List Segments

Search

In Make“Returns a list of all segments.”

Brings back all your Mautic segments, one bundle per list.

When to use it
to find the ID of a segment by its name, or to keep an overview of your lists in a shared table.
Watch out
it returns every segment, not just one; place a filter right after it to keep only the list you are after.
Mautic24

List Stages

Search

In Make“Returns a list of all contact stages.”

Returns all the contact stages defined in Mautic, which gives you their IDs and names in one pass.

When to use it
before Add Contact to a Stage, to match the stage name used by your CRM with the right Mautic ID.
Watch out
each stage arrives as its own bundle, so the next module runs once per stage unless you filter.
Mautic25

Search Contacts

Search

In Make“Retrieves a list of contacts by a search.”

Runs a search across your Mautic contacts and returns the matches, zero, one or many.

When to use it
you have an e-mail address from another app and need the Mautic contact ID before updating, segmenting or deleting that person.
Watch out
the search can come back with several contacts or none, so add a filter to keep only the one you mean.
Need help

Need help automating Mautic with Make?

A person reads every message.

FAQ

Mautic and Make: common questions

01Is the Mautic Make integration free?
Yes, on the Make side. Mautic is a standard app, available from the Free plan. That plan allows 2 active scenarios, runs scheduled scenarios at most every 15 minutes, caps each run at 5 minutes and files at 5 MB. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Each module run on one bundle is an operation, which is what Make counts on your plan. Your Mautic subscription is a separate matter, handled on the Mautic side.
02What does it take to connect Mautic to Make?
An active Mautic account with API access enabled. In Mautic, go to Settings, then API Settings, click Add New and paste the callback URI https://www.integromat.com/oauth/cb/mautic. Copy the Client ID and the Client secret shown on screen. In Make, add a Mautic module, click Create a connection, give it a name if you want, and paste both values. If the module is Watch Events, Make asks you to create a webhook first.
03Does the Mautic trigger in Make react in real time?
Yes. Watch Events is an instant trigger: Mautic sends the event to Make through a webhook as soon as it happens, so the scenario does not wait for a schedule. It is the only Mautic trigger, though. For scenarios that start somewhere else, such as a new form entry, the first module belongs to that other app, and if it is scheduled, it runs every 15 minutes by default on a new scenario.
04What if a Mautic module is missing in Make?
Use Make an API Call. It sends any request the Mautic API accepts, with the same connection as every other Mautic module, so what the other Mautic modules do not cover stays within reach. You write the request yourself, so it takes a look at the Mautic API documentation. The Make doc for this app lists no specific limit, and marks its own content as AI-generated, so check important details against Mautic's documentation.
05Make or n8n for a Mautic integration?
It depends mostly on the tool your team already works in. Mautic has an app in Make, with the 26 modules described on this page, and a node in n8n, covered on a separate page of this site. Both connect to the same Mautic account. If your other automations already live in Make, keeping Mautic there means one place to read runs and fix errors. If they run in n8n, the n8n page is the better starting point.
Same platform

Other docs you might need on this stack.

Browse all integrations