Resources · Make integration

Loopify Make integrationAutomate Loopify with Make.

Can your Loopify contacts stay in sync without copy and paste? The Loopify Make integration offers 5 modules: 1 scheduled trigger and 4 actions. This page shows how to link your account, build a first scenario and pick the right module.

Try the Loopify integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Loopify Make integration do?

The Loopify Make integration links your Loopify account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a single brick such as a trigger or an action. Loopify brings 5 of them, so contacts coming from other tools can land in Loopify, and Loopify activity can start work elsewhere.

Feed Loopify from your other tools. A signup captured by a form app or a shop can go straight into Loopify with Create/Update a Contact. Going by its name, the module updates the contact when it already exists instead of creating a duplicate; check that on your first test.

Place a contact into a Loopify entry. Add Contact to New Entry and Add to API Entry both work with Loopify entries. The documentation gives no description for either, so run each one on a test contact and compare what changes in Loopify before you pick one.

React to your flows. Watch Connect in Flow is the only trigger. Make checks it on the scenario's schedule, so the next step starts at the following check, not the second something happens.

Anything the four actions miss can go through Make an API Call, with the same connection. The documentation for this app is marked as AI-generated by Make, so treat every label as something to verify in the editor. The same app often exists in n8n too; the n8n vs Make comparison lays out the differences, and the Make training covers the editor from zero. If a run fails, Make troubleshooting lists the usual fixes.

Connect

How do you connect Loopify to Make?

  1. 01

    Get your Loopify API key

    Sign in to Loopify and open the area where API access is managed. Retrieve or generate the key there, which the documentation also calls a Bearer Token. You need an active Loopify account for this step.

  2. 02

    Open the connection window

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

  3. 03

    Paste the key and save

    Give the connection a clear label in Connection name if you manage several Loopify accounts, then paste the key you copied. Make checks it and the module can now read your Loopify data.

First scenario

How do you build your first scenario with Loopify?

GoalWhen a new signup arrives in another app, Make creates or updates that person as a Loopify contact.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big + to place the first module. This first module is the app where your signups arrive, such as a form tool.

  2. 02

    Set up the source app

    Pick that app's module that watches new entries and link its account. Each item it returns is a bundle, meaning one record passed to the next module, here one person.

  3. 03

    Add the Loopify action

    Click the + on the right, search Loopify, choose Create/Update a Contact and create your connection. Then map the person's details from the first module into the Loopify fields Make lists.

  4. 04

    Test with Run once

    Click Run once and submit one test signup. Open the bubble above each module to read the bundles it received, then check in Loopify that the contact looks right.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A new scenario runs every 15 minutes by default, and the Free plan cannot go below that. Switch the scenario on and it keeps running without you.

Triggers

Which Loopify trigger starts a scenario?

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

Loopify1Watch Connect in Flow

Watch Connect in Flow

triggerIn the docs only

This trigger gives you a scenario that starts from activity in your Loopify flows, so your other tools learn about it without anyone checking Loopify by hand. The documentation offers no description, and the name is the only clue: it points to a connect step inside a flow.

How it fires
scheduled, Make checks the app on the scenario's schedule, every 15 minutes by default.
When to use it
when something happening in a Loopify flow should create a task, a message or a row in another app.
Watch out
run it once before building the rest, then read the bundle it returns to learn which data it really carries.
Modules

What can the Loopify modules do?

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

Loopify1

Add Contact to New Entry

ActionIn the docs only

With this action, a person reaches a Loopify entry without you placing them manually, which saves a round trip into the app. Its name says it creates a new entry for the contact; the documentation adds nothing more.

When to use it
after a purchase or a signup, when that person should start a fresh journey in Loopify.
Watch out
test on a dummy contact first and look in Loopify at where it ended up.
Loopify2

Add to API Entry

ActionIn the docs only

You get a way to push a contact into an entry point set up for API use in Loopify, so outside tools can start Loopify work. The documentation leaves it undescribed, so its exact behaviour is something to confirm yourself.

When to use it
when your Loopify setup already has an API entry and Add Contact to New Entry does not reach it.
Watch out
compare both modules on a test contact before choosing, because their names are close.
Loopify3

Create/Update a Contact

ActionIn the docs only

This one keeps your Loopify contact list current from any other app, without duplicate cleanup afterwards if it behaves as its name promises: create the person when new, update them when known.

When to use it
as the last step whenever a form, a shop or a CRM hands over a person to store in Loopify.
Watch out
the documentation does not say how Loopify matches an existing contact, so check after Run once that no copy appeared.
Loopify4

Make an API Call

ActionIn the docs only

Here you reach any part of the Loopify API that the other modules skip, reusing the connection you already created, so there is no second key to handle. It is the fallback when no listed module matches your need.

When to use it
when you need something the four named actions and the trigger do not cover.
Watch out
you write the request yourself, so keep the Loopify API reference open while you set it up.
Need help

Need help automating Loopify with Make?

A person reads every message.

FAQ

Loopify and Make: common questions

01Is the Loopify Make integration free?
Yes, on the Make side. Loopify is a standard app, so it is available from the Free plan, like more than 3000 other standard apps. The Free plan allows 2 active scenarios, runs them at most every 15 minutes, stops a run after 5 minutes and caps transfer at 512 MB. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and count usage in credits each month. Loopify itself needs its own active account.
02What do you need to connect Loopify to Make?
An active Loopify account and its API key, which the documentation also calls a Bearer Token. Find it in the part of Loopify where API access is managed, retrieve or generate it, then paste it in Make after clicking Create a connection on any Loopify module. The connection name is optional. Once saved, every Loopify module in every scenario reuses that same connection, so you only paste the key one time.
03Does the Loopify trigger in Make fire in real time?
No. Watch Connect in Flow is a scheduled trigger: Make checks Loopify on the scenario's schedule, every 15 minutes by default and never more often than that on the Free plan. On a paid plan you can go down to 1 minute. Anything that happens in Loopify between two checks is picked up at the next one. The documentation lists no instant trigger for Loopify; when you add the module, the clock badge on it confirms the scheduled type.
04What if the Loopify module you need is missing in Make?
Use Make an API Call. It sends any request the Loopify API accepts, with the same connection as the other modules, so it covers what the four actions and the trigger leave out. Keep in mind that Make marks the Loopify documentation as AI-generated and asks users to verify important details with Loopify directly. When a label or a behaviour looks off, test on dummy data first and contact Loopify if it still does not match.
05Should you use Make or n8n for Loopify?
It depends on the tool your team already uses. In Make, Loopify gives 5 modules (1 scheduled trigger and 4 actions) plus Make an API Call for the rest, all driven from a visual editor with no code. The same app often exists as an n8n node as well, so check that list for your case. The practical criterion is where your other automations already run, because one tool means one place to follow every run.
Same platform

Other docs you might need on this stack.

Browse all integrations