Resources · Make integration

Loops Make integrationAutomate Loops with Make.

Can your signup form, CRM or billing tool keep Loops up to date on its own? The Loops Make integration gives you 12 modules: one instant trigger and 11 actions on contacts, events and transactional emails. This guide connects your account, builds a first scenario and explains each module.

Try the Loops integration on MakeSee the 12 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Loops Make integration do for you?

The Loops Make integration links your Loops account to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules that each do one job. On the Loops side, a scenario can create and update contacts, send events that start your loops, fire transactional emails and react when Loops reports an event.

An audience that fills itself. A SaaS team can pass every new signup from its app or its form tool to Update a Contact by Email. Loops receives the contact with its properties, and nobody exports a CSV again. If the property you need does not exist yet, Add a Custom Property creates it from the same scenario.

Product behavior that starts the right email. When a user finishes onboarding or upgrades in your product, Send an Event by User ID tells Loops, and the loop tied to that event takes over. The copywriting stays in Loops; Make only carries the signal.

Account emails sent from any tool. Send a Transactional Email lets an e-commerce shop or a booking tool send a receipt, a reset link or a confirmation through a template designed in Loops. For inspiration on the booking side, the Acuity Scheduling Make integration shows what that app can hand over.

The list stops at 12 modules: there is no search that returns several contacts, and only one trigger. For any other endpoint, Make an API Call reuses your connection. Loops also has an n8n node; the n8n vs Make comparison lays out how the two tools differ, and the Make review covers Make on its own.

Connect

How do you connect Loops to Make?

  1. 01

    Generate an API key in Loops

    In Loops, open Settings, then API, and click Generate. A window shows the key: copy it right away. This key is what lets Make act on your account, so keep it somewhere private.

  2. 02

    Add a Loops module and create the connection

    In your scenario, add any Loops module and click Create a connection. A connection is your Loops account linked to Make once and reused by every Loops module. The Connection name field is optional; a clear name helps if you run several workspaces.

  3. 03

    Paste the key and save

    Paste the API key copied from Loops and confirm. Make checks it and the connection appears in the module. From there, the fields of each Loops module can be filled with data coming from earlier modules.

First scenario

Build your first Loops scenario

GoalWhen a new user signs up in another app, Make updates the contact in Loops and sends a welcome email.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the app where signups land (a form, a database, your product) as the first module.

  2. 02

    Add Update a Contact by Email

    Click the + on the right, search Loops and choose Update a Contact by Email. Link your account with Create a connection, then map the email and name from the first module.

  3. 03

    Add Send a Transactional Email

    Add one more Loops module, Send a Transactional Email. Point it to your welcome template and map the same email address, so the message reaches the person who just signed up.

  4. 04

    Test with Run once

    Click Run once and create a test signup. Each module shows the bundles it received, a bundle being one item passed along, here one contact. Check that the contact exists in Loops and the email arrived.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, or keep it instant if that app offers a webhook. Then switch the scenario on so it keeps running without you.

Triggers

What starts a Loops scenario

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

Loops1Watch Events

Watch Events

Instant trigger

In Make“Triggers with every new event selected in your Loops account.”

Watch Events turns activity in your Loops account into the starting point of a scenario, so other tools hear about it without anyone copying data. You choose which events it listens to when you set it up, and each event arrives as a bundle the next modules can use.

How it fires
it is an instant trigger, meaning Loops calls Make through a webhook as soon as the event happens. Make does not wait for a schedule.
When to use it
pass a Loops event to your CRM, a team chat or a spreadsheet where sales or support can act on it.
Watch out
create the webhook before the connection, and select only the events you need, since each run uses operations, the unit Make counts on your plan.
Modules

What each Loops module does

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

Loops1

Add a Contact

Action

In Make“Adds a contact to your Loops account.”

This one creates a brand new person in your Loops audience, ready to receive your loops and campaigns. It suits sources where every record is truly new.

When to use it
a lead magnet or waitlist form where each submission should become a fresh contact.
Watch out
if the address may already exist, prefer Update a Contact by Email, which also creates the contact when none is found.
Loops2

Add a Custom Property

Action

In Make“Adds a new custom property for contacts.”

Your contacts get a new field in Loops, such as a plan name or a signup source, that you can later use to segment or personalize emails.

When to use it
before you start sending a new piece of data from another tool, so Loops has a place to store it.
Watch out
it creates the property, not a value on a contact; to fill the field, add an update module afterwards.
Loops3

Delete a Contact by Email

Action

In Make“Deletes a Contact by using the Email.”

Removing someone from your Loops audience takes one step with this module: you give it the email address and the contact is gone from your list.

When to use it
a deletion request received through a form or your support desk that must be honored in Loops as well.
Watch out
a delete cannot be undone from Make, so test it with Run once on a dummy address first.
Loops4

Delete a Contact by User ID

Action

In Make“Deletes a User by using the User ID.”

Same result as the email version, except Loops finds the person through the user ID your product assigned, which stays stable even when an email changes.

When to use it
an account closed in your app, where the scenario only knows the internal user ID.
Watch out
the ID must match the one stored on the contact in Loops, otherwise nothing is deleted, and a deletion is permanent.
Loops5

Get a Contact by Email

Action

In Make“Gets a Contact using the Email.”

Pull what Loops knows about a person into your scenario: you pass an email, and the contact's data becomes available to map into the next modules.

When to use it
check whether a buyer is already in your audience before deciding which email or event to send.
Watch out
despite its internal key, it looks up one address at a time; it does not return a list of contacts matching a filter.
Loops6

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Here is your way past the 11 ready-made actions: any endpoint of the Loops API can be called from the scenario, with the connection you already set up.

When to use it
a Loops feature that none of the listed modules covers.
Watch out
you write the request yourself, so keep the Loops API documentation open and check the response in Run once before switching the scenario on.
Loops7

Send an Event by Email

Action

In Make“Sends an Event by using the Email.”

Tell Loops that something happened to a person, identified by email, and let the loop linked to that event send the right sequence.

When to use it
a payment received in your billing tool that should start an onboarding loop for that customer.
Watch out
the event name must match the one your loop listens to in Loops, or the email flow will not start.
Loops8

Send an Event by User ID

Action

In Make“Sends an Event by using the User ID.”

Product teams get the same event signal, keyed on the user ID from your app rather than an email, which fits data coming straight from a product database.

When to use it
a feature used for the first time or a trial about to end, recorded in your product with the user's internal ID.
Watch out
the contact in Loops must carry that same user ID for the event to land on the right person.
Loops9

Send a Transactional Email

Action

In Make“Sends a transactional email.”

One person, one message, sent now: a receipt, a password reset or a booking confirmation built from a template you designed in Loops.

When to use it
any tool without good email of its own, such as a shop or a form, that needs to send a clean account message.
Watch out
this is for messages tied to an action the person took, not for marketing; campaigns and loops live in Loops itself.
Loops10

Update a Contact by Email

Action

In Make“Updates a contact in Loops or creates a new one if there is no contact for the given email.”

Keeping a contact current is its job, and it creates that contact when the email is not in Loops yet, which makes it the safest choice for syncing.

When to use it
a CRM or signup flow where you cannot tell whether the person already exists in your audience.
Watch out
map only the fields you want to change, so an empty value from the source does not overwrite good data.
Loops11

Update a Contact by User ID

Action

In Make“Updates a Contact in Loops for a given User ID.”

When your source knows people by their product ID, this module updates the matching Loops contact without needing the email at all.

When to use it
a user changes plan or email address in your app, and Loops should follow.
Watch out
unlike the email version, the documentation does not say it creates a missing contact, so test with Run once on a known user first.
Need help

Need help automating Loops with Make?

A person reads every message.

FAQ

Loops and Make: common questions

01Is the Loops Make integration free?
Yes, on the Make side. Loops is a standard app, available from the Make Free plan. That plan allows 2 active scenarios, runs no more often than every 15 minutes on a schedule, stops a run after 5 minutes, handles files up to 5 MB and includes 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 count usage in credits per month. The Loops subscription is separate; check the Loops pricing page for that part.
02What do you need to connect Loops to Make?
An active Loops account and an API key. In Loops, go to Settings, then API, click Generate and copy the key shown in the window. In Make, add a Loops module, click Create a connection, give it a name if you like and paste the key. For the Watch Events trigger, click Create a webhook first and create the connection from there. One connection then serves every Loops module in all your scenarios, so you only do this setup once per account.
03Does the Loops trigger in Make fire instantly?
Yes. Watch Events is an instant trigger: Loops calls Make through a webhook as soon as a selected event happens, so the scenario starts without waiting for a schedule. It is the only trigger in the Loops app. If your scenario should start from something that happens elsewhere, such as a new signup or a payment, put that app's module first and use the Loops actions after it. A scheduled first module runs every 15 minutes by default, or down to 1 minute on paid plans.
04What if a Loops module you need is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the Loops API with the connection you already have, so you are not stuck with the 11 listed actions. You write the request following the Loops API documentation and read the result in Run once. Keep in mind that the Make documentation for this app is marked as AI-generated from the Loops docs, so verify important details with Loops directly before relying on them in a live scenario.
05Should you use Make or n8n for Loops?
It depends on the tool your team already works in. Loops has a Make app with 12 modules, including an instant trigger, and it also has an n8n node. On the Make side, you get a visual editor, a connection set up once, and Make an API Call for anything the modules do not cover. If your other automations already live in one of the two tools, keeping Loops there usually means less to maintain. Compare what each tool offers for your own flows before choosing.
Same platform

Other docs you might need on this stack.

Browse all integrations