Resources · Make integration

Systeme IO Make integrationAutomate Systeme IO with Make.

Can Make keep your Systeme IO contacts, tags and courses in order without code? Yes. The Systeme IO Make integration offers 25 modules, 18 actions and 7 searches. This page shows how to link your account, build a first scenario and pick the right module.

Try the Systeme IO integration on Make See the 25 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Systeme IO Make integration let you automate?

The Systeme IO Make integration links your Systeme IO account to Make, a no-code tool where you build a scenario: an automation made of modules. A module is one brick of that chain, here an action or a search on Systeme IO. Together they create and update contacts, tag them, enroll them in a course or open a community to them.

A new lead, tagged and enrolled. A form in another app collects a sign-up. Create a Contact adds the person to Systeme IO, Add a Tag to a Contact labels them by source, and Create an Enrollment opens the course they asked for.

Community access that follows the sale. When a payment lands in your billing tool, Create a Membership lets the buyer into the right community. When a refund comes in, Delete a Membership takes that access back.

A tidy tag list. List Tags pulls every tag of the account, then Update a Tag or Delete a Tag fixes the labels your team stopped using.

One thing to know before you start: Systeme IO has no trigger module in Make, so the app itself never starts a scenario. Another app or Make's own schedule does. For anything the listed modules miss, Make an API Call reuses the same connection. Many apps also have an n8n node; if you are weighing both tools, read n8n vs Make, and check Make pricing for plan details.

Connect

How do you connect Systeme IO to Make?

01
Create an API key in Systeme IO
In Systeme IO, click your profile icon in the upper right corner, then Settings, then Public API keys in the left sidebar. Click Create, name the key, click Save and copy the Token value.
02
Add a Systeme IO module in Make
In your scenario, add any Systeme IO module and click Create a connection. A connection is your Systeme IO account linked to Make once, then reused by every Systeme IO module. The Connection name field is optional.
03
Paste the token and save
Paste the token into the API Token field and click Save. If Systeme IO asks you to authenticate and confirm access, accept. The connection now shows in the module, and Make can list what it reads from your account.

First scenario

Your first scenario: a new lead becomes a tagged contact

GoalWhen a lead signs up in another app, Make creates the contact in Systeme IO and adds a tag to it.

01
Create the scenario
On the Scenarios page, create a new scenario and click the +. Put first the trigger of the app where leads arrive, your form tool for instance, since Systeme IO has none.
02
Add Create a Contact
Click the + on the right of that first module, search Systeme IO and pick Create a Contact. Link your account with Create a connection, then map the lead's data from the form into the contact.
03
Tag the new contact
Add Add a Tag to a Contact next. Map the contact that the previous module returned, then choose the tag from the list Make shows, so every lead carries the name of its source.
04
Test with Run once
Click Run once, send one test sign-up through the form and read the bundles. A bundle is one item passing from a module to the next, here one person. Then open Systeme IO and check the contact and its tag.
05
Schedule and switch it on
Set the schedule on the first module: a new scenario runs every 15 minutes by default, the shortest interval on the Free plan. Switch the scenario on. Each module run counts as one operation on your plan.

Modules

What each Systeme IO module does

Systeme IO gives you 25 modules in 6 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Community

4 modules

Systeme IO1

List Communities

In Make“Lists the collection of community resources.”

Pulls every community of your Systeme IO account into the scenario, one bundle per community, so the next modules know which spaces exist.

When to use it

before Create a Membership, when the community depends on the product a buyer picked and you want Make to match it by name instead of a fixed choice.

Watch out

a search returns zero, one or several bundles, and each module after it runs once per bundle, which multiplies operations.

Systeme IO2

Create a Membership

Action

In Make“Creates a membership resource.”

Gives a contact access to one of your Systeme IO communities straight from the scenario, so a new member gets in without anyone adding them by hand.

When to use it

right after a payment or a signed order in another app, to open the community that goes with the offer.

Watch out

check during Run once that the right community was chosen, because every buyer after that will land in it.

Systeme IO3

List Memberships

In Make“Retrieves the collection of membership resources.”

Shows who belongs to your communities by bringing membership records back as bundles, ready to copy into a sheet or another tool.

When to use it

to export members for a report, or to find the exact membership you want to remove with Delete a Membership.

Watch out

a busy community can return many bundles; look at the count in Run once before you map them into further modules.

Systeme IO4

Delete a Membership

Action

In Make“Deletes the membership resource.”

Removes a contact's access to a community in one step, which keeps paid spaces for the people who still pay.

When to use it

when a refund or a cancelled subscription is recorded in your billing app.

Watch out

a wrong mapping cuts a paying member off, so test it on your own contact before you point it at real customers.

Contact Fields

4 modules

Systeme IO5

List Contact Fields

In Make“List the contact fields resources.”

Returns the contact fields set up in your Systeme IO account, the slots where you keep data about each person.

When to use it

before sending data from another app into contacts, to see which fields exist, or before a cleanup of fields nobody fills.

Watch out

it lists the fields themselves, not what a given contact holds in them; for one person's data, use Read a Contact.

Systeme IO6

Create a Contact Field

Action

In Make“Creates a contact field.”

Adds a new contact field to your account from the scenario, so contacts gain a place for a piece of data you did not track until now.

When to use it

when a new form in another app asks a question that has no matching field in Systeme IO yet.

Watch out

look it up with List Contact Fields first, so a scenario that runs again does not try to add the same field twice.

Systeme IO7

Delete a Contact Field

Action

In Make“Deletes a contact field ressource.”

Retires a contact field you no longer use, which keeps the field list short and easier for your team to read.

When to use it

during a cleanup, once List Contact Fields has shown you the fields that stay empty.

Watch out

data stored in that field may go with it, so export anything you still need before the scenario runs.

Systeme IO8

Update a Contact Field

Action

In Make“Modifies a contactfield resource”

Edits a contact field that already exists, so you fix it in place instead of deleting it and building a new one.

When to use it

when a field needs correcting and other scenarios or forms already rely on it.

Watch out

pick the field from the list Make shows, or map it from List Contact Fields, so the change lands on the right one.

Contact

7 modules

Systeme IO9

List Contacts

In Make“Lists the contacts resources.”

Brings your Systeme IO contacts into the scenario, one bundle per person, ready to go to a sheet, a CRM or a mailing tool.

When to use it

to copy your audience elsewhere, or to check whether someone already exists before you create or update them.

Watch out

every module after it runs once per contact returned, and each of those runs is an operation on your plan.

Systeme IO10

Create a Contact

Action

In Make“Creates a contact.”

Adds a person to Systeme IO when they show up in another app, with the data you map from the module before it.

When to use it

a lead fills a form, a buyer pays in a shop, or a webinar sign-up arrives in another tool.

Watch out

when the person may already be in your list, search them with List Contacts first and use Update a Contact instead.

Systeme IO11

Read a Contact

Action

In Make“Retrieves a Contact resource.”

Fetches the full record of one contact, so the following modules can use everything Systeme IO holds on that person.

When to use it

after another module handed you a contact and you need its details before a decision, a message or an update.

Watch out

it reads a single contact, not a list; to go through many people, List Contacts is the right module.

Systeme IO12

Delete a Contact

Action

In Make“Deletes a contact resource.”

Erases a contact from Systeme IO, useful when someone asks for their data to be removed or when test entries clutter your list.

When to use it

when a deletion request is logged in your support or form tool.

Watch out

treat it as permanent and try it with Run once on a test contact before it touches real people.

Systeme IO13

Update a Contact

Action

In Make“Modifies a contact resource.”

Keeps a Systeme IO contact in line with another app by rewriting the data you map, without creating a second record for the same person.

When to use it

a customer changes their details in your shop or CRM, and Systeme IO should follow.

Watch out

map only what changed, then open the contact in Systeme IO after Run once to confirm nothing else moved.

Systeme IO14

Add a Tag to a Contact

Action

In Make“Assigns a tag to a contact.”

Labels a contact with one of your Systeme IO tags, the usual way to sort people by source, product or interest.

When to use it

right after Create a Contact to mark where a lead came from, or when a buyer completes a purchase in another app.

Watch out

pick an existing tag from the list Make shows, or add it first with Create a Tag.

Systeme IO15

Delete a Tag in a Contact

Action

In Make“Deletes the tag assigned to resource.”

Takes a tag off one contact while the tag itself stays in your account for everyone else who carries it.

When to use it

a prospect becomes a customer and the prospect tag should go, or someone opts out of a topic.

Watch out

do not confuse it with Delete a Tag, which targets the tag itself rather than one person.

School

4 modules

Systeme IO16

List School Courses

In Make“Retrieves the list of schools.”

Lists the courses of your Systeme IO school, so the scenario can choose which one to open for a student.

When to use it

before Create an Enrollment, when the course depends on what was bought and you match it by name.

Watch out

each course comes back as its own bundle, and every module placed after it repeats once per course.

Systeme IO17

Create an Enrollment

Action

In Make“Creates an Enrollment to a course.”

Opens a course to a contact the moment the scenario runs, so a buyer reaches the training without anyone touching the school settings.

When to use it

after a sale in your checkout tool or a signed quote, to deliver the course that was sold.

Watch out

run it once on your own contact first to confirm the right course opens.

Systeme IO18

List Enrollments

In Make“Lists enrollment resources.”

Returns the enrollments of your school, which tells you which contacts can reach which course.

When to use it

to report on students in a sheet, or to find an enrollment before closing it with Delete an Enrollment.

Watch out

each enrollment returned is one bundle, and the modules after it spend one operation on every one of them.

Systeme IO19

Delete an Enrollment

Action

In Make“Deletes the enrollment resource.”

Withdraws a contact's access to a course, the step that closes the training once payment stops.

When to use it

a subscription is cancelled or a refund is issued in your billing app.

Watch out

a mistake here locks a real student out of their course, so test with your own contact and check the mapping twice.

Tag

5 modules

Systeme IO21

Create a Tag

Action

In Make“Creates a tag ressource.”

Creates a new tag in Systeme IO from the scenario, so a new product or campaign gets its label without a detour through the settings.

When to use it

a new product appears in your shop and its buyers need their own tag.

Watch out

check List Tags first so the same name is not created twice when the scenario runs again.

Systeme IO22

Read a Tag

Action

In Make“Retrieves a Tag resource.”

Retrieves one tag and its details, which lets the scenario confirm it exists before relying on it.

When to use it

when another module hands you a tag and you need its name for a message, a sheet or a report.

Watch out

it works on one tag at a time; for the whole list, List Tags does the job in a single module.

Systeme IO23

Update a Tag

Action

In Make“Modifies a Tag ressource”

Edits an existing tag without deleting it, the gentle way to fix a label your team set up badly.

When to use it

after a List Tags audit showed names that do not follow the same logic.

Watch out

other scenarios may rely on that tag, so look at them before you change it.

Systeme IO24

Delete a Tag

Action

In Make“Deletes a tag resource.”

Removes a tag from your Systeme IO account, the clean way to retire a label left over from an old campaign.

When to use it

once an audit with List Tags has shown labels nobody uses anymore.

Watch out

unlike Delete a Tag in a Contact, it acts on the tag itself, not on one person, so test it on a throwaway tag.

Other

1 module

Systeme IO25

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Calls any endpoint of the Systeme IO API from your scenario, with the same connection as the other modules, to cover what they do not.

When to use it

when you need a Systeme IO action that has no dedicated module in this list.

Watch out

here you work with the API directly, so read the Systeme IO API reference for that endpoint before you build.

Need help

Need help automating Systeme IO with Make?

A person reads every message.

FAQ

Systeme IO and Make: common questions

01Is the Systeme IO Make integration free?

Yes. Systeme IO is a standard app in Make, so it works from the Free plan. That plan allows 2 active scenarios, scheduled runs no closer than every 15 minutes, runs of 5 minutes at most, 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, remove the cap on active scenarios and allow runs of up to 40 minutes. Usage is counted in operations per month. Your Systeme IO subscription is a separate matter.

02What do you need to connect Systeme IO to Make?

A Systeme IO account and an API token. In Systeme IO, open your profile icon, then Settings and Public API keys, click Create, name the key, save it and copy the Token value. In Make, add a Systeme IO module, click Create a connection, paste the token into the API Token field and click Save. If Systeme IO asks you to authenticate and confirm access, accept. The connection is then reused by every Systeme IO module you add.

03Does the Systeme IO Make integration react in real time?

Not by itself. Systeme IO has no trigger module in Make, so nothing inside Systeme IO starts a scenario. You still have two ways to get going. Put the trigger of another app first, such as your form or checkout tool, and the scenario reacts to that app. Or run the scenario on Make's schedule, set on the first module: every 15 minutes by default, down to 1 minute on a paid plan, with a module such as List Contacts to pull the data.

04What if the Systeme IO module you need is missing in Make?

Use Make an API Call. This module calls any endpoint of the Systeme IO API with the connection you already set up, so it covers what the listed modules do not. The Make documentation for Systeme IO gives no numeric limit for the app, so there is no published cap to plan around. If the task falls outside what Systeme IO itself offers, add the module of another app to the same scenario for that part.

05Make or n8n for Systeme IO?

It depends on where your team already builds. On Make, Systeme IO comes with 25 modules for contacts, tags, contact fields, courses and communities, plus Make an API Call for the rest. Many apps also have an n8n node, so check whether one exists for Systeme IO before you decide. Then weigh practical criteria: where your other automations already live, who will maintain them, and how each tool counts usage, which is operations on Make.

Create an API key in Systeme IO

Add a Systeme IO module in Make

Paste the token and save

Create the scenario

Add Create a Contact

Tag the new contact

Test with Run once

Schedule and switch it on

Need help automating Systeme IO with Make?