Resources · Make integration

Loopy Loyalty Make integrationAutomate Loopy Loyalty with Make.

Your loyalty program can talk to the rest of your tools. The Loopy Loyalty Make integration gives you 16 modules: 5 triggers, 9 actions and 2 searches. This page shows shop owners and ops teams how to link the account and build a first working scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Loopy Loyalty Make integration do?

The Loopy Loyalty Make integration links your loyalty program to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules that runs on a schedule. Each module is one brick of that chain, so Loopy Loyalty events such as a new enrollment or a redeemed reward can feed your other apps.

Greet new members. Watch Enrollments spots each customer who joins, and Send Push Message to a Customer sends them a welcome note on their phone. It is the scenario built step by step further down.

Reward activity from another app. When a purchase lands in your checkout or booking tool, Search Customer finds the matching member and Add Stamps credits the visit. The search can return zero, one or several customers, so plan for each case.

Keep your team in the loop. Watch Redeemed Rewards and Watch Forfeited Rewards can post each event into a sheet or a chat tool, so the counter staff knows who used a reward and who lost one.

One limit to know first: Make states that its documentation for Loopy Loyalty is limited, because little public information exists about the app. Module names are clear, but the exact fields only show up once your connection is in place. When a listed module falls short, Make an API Call reaches other endpoints with the same account. If you are still choosing a tool, the n8n vs Make comparison lays out the differences, the Make pricing page covers plans, and Make training helps you get fluent in the editor.

Connect

How do you connect Loopy Loyalty to Make?

  1. 01

    Add a Loopy Loyalty module

    In a new scenario, click the +, search for Loopy Loyalty and pick any of its modules. Then click Create a connection. A connection is your Loopy Loyalty account linked to Make once and reused by all 16 modules.

  2. 02

    Name the connection

    Make offers a name field for the connection. It is optional, but a clear label such as the shop or brand name helps when you run several Loopy Loyalty accounts from the same Make organization.

  3. 03

    Authorize and save

    Follow what Make asks next: either approve access on the Loopy Loyalty page that opens, or paste the key your account provides. Click Save, and the module can now list what it reads from your program.

First scenario

Build your first scenario with Loopy Loyalty

GoalWhen a customer joins your program in Loopy Loyalty, Make sends that customer a welcome push message.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big +. Search for Loopy Loyalty and choose Watch Enrollments as the first module.

  2. 02

    Link your account

    Click Create a connection and authorize Make as shown in the section above. Once linked, fill the fields the trigger displays; Make lists what it can read from your account.

  3. 03

    Add the push message

    Click the + on the right of the trigger and pick Send Push Message to a Customer. Map the customer coming from the first module and type your welcome text.

  4. 04

    Test with Run once

    Enroll a test customer, then click Run once. Open the bubble above each module to read the bundles it received, that is each item passed along, and check the push reached the phone.

  5. 05

    Schedule and switch on

    Click the clock on the first module to set how often Make checks for new members. A new scenario runs every 15 minutes by default. Then switch the scenario on.

Triggers

Loopy Loyalty triggers in Make

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

Loopy Loyalty1Watch Earned Rewards

Watch Earned Rewards

triggerIn the docs only

This trigger starts your scenario each time Make finds a reward that a customer has just earned, so you can react while the customer still cares. Make lists it without a description, so its behavior here is read from its name.

How it fires
scheduled: Make checks the app on the scenario's schedule, shown by the clock badge on the module.
When to use it
a customer fills a card and you want a follow-up email or a note in your CRM right after.
Watch out
on the Free plan the shortest gap between two checks is 15 minutes, so the follow-up is not immediate.
Loopy Loyalty2Watch Enrollments

Watch Enrollments

triggerIn the docs only

Every new member who joins your loyalty program becomes a bundle Make can pass to the next module, which makes onboarding hands-free. It is the most natural first trigger for this app.

How it fires
scheduled: Make checks the app on the scenario's schedule rather than being called by Loopy Loyalty.
When to use it
you want each new member added to a mailing list, a CRM or a welcome push without typing anything.
Watch out
the fields each enrollment carries are not documented, so run the scenario once and read the bundle before mapping.
Loopy Loyalty3Watch Forfeited Rewards

Watch Forfeited Rewards

triggerIn the docs only

You learn about rewards that customers let slip away, which is a signal worth catching before the customer drifts off. Going by its name, it reports rewards that were lost rather than used; Make gives no further detail.

How it fires
scheduled: Make checks the app on the scenario's schedule, not the moment the reward is lost.
When to use it
a win-back flow, where a lost reward opens a task for your team or a friendly message.
Watch out
test with a real forfeited reward first, since the bundle content is only visible after a run.
Loopy Loyalty4Watch Redeemed Rewards

Watch Redeemed Rewards

triggerIn the docs only

Each reward a customer claims at the counter can land in your reporting or your stock tool, with no manual tally. The trigger watches redemptions, as opposed to rewards that were only earned or lost.

How it fires
scheduled: Make checks the app on the scenario's schedule so a redemption shows up at the next check, not at the counter.
When to use it
a free coffee or product leaves the shelf and you log it in a sheet to track what the program costs.
Watch out
each redemption is one bundle, and every module after it counts one operation per bundle on your plan.
Loopy Loyalty5Watch Stamped

Watch Stamped

triggerIn the docs only

Stamps are the daily heartbeat of the program, and this trigger lets Make hear each one. Every time a card gets stamped, the event can travel to another tool of your choice.

How it fires
scheduled: Make checks the app on the scenario's schedule, so stamps arrive grouped by check.
When to use it
you want visit history in your CRM, or a thank-you push after a given stamp.
Watch out
this trigger can produce many bundles on a busy day, and each module after it spends operations on every one, so keep the chain short.
Modules

What the Loopy Loyalty modules do in Make

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

Loopy Loyalty1

Add Stamps

ActionIn the docs only

Credits stamps to a member's card from another app, so a sale recorded elsewhere counts toward the reward without anyone tapping a phone.

When to use it
an order is paid in your online shop and the buyer is already a member.
Watch out
put Search Customer before it to be sure you stamp the right person.
Loopy Loyalty2

Add Stamps with a Unique ID

ActionIn the docs only

Same result as Add Stamps, a card that moves closer to its reward, but the member is targeted through a unique identifier instead. Pick it when the other app already stores that identifier.

When to use it
your booking or checkout tool keeps a customer reference you can map directly.
Watch out
Make does not document which ID is expected, so check the field after connecting.
Loopy Loyalty3

Delete a Customer

ActionIn the docs only

Removes a customer from your program, which keeps your member list clean when someone asks to leave. Nothing in Make brings a deleted record back.

When to use it
a deletion request arrives through a form and you want it handled in every tool at once.
Watch out
test it on a dummy member first, and add a filter so only confirmed requests reach this module.
Loopy Loyalty4

Enroll a Customer

ActionIn the docs only

Signs a person up for your loyalty program from the outside, so members join without scanning anything at the counter. It is the action twin of Watch Enrollments.

When to use it
a customer ticks a loyalty box at online checkout or on a newsletter form.
Watch out
search first to avoid enrolling the same customer twice when they come back.
Loopy Loyalty5

Make an API Call

ActionIn the docs only

Opens any endpoint of the Loopy Loyalty API from your scenario, using the connection you already set up. It covers what the 15 other modules leave out.

When to use it
you need data or an action that none of the named modules offers.
Watch out
you write the request yourself, so keep the app's own API reference open, since Make's page on this app is limited.
Loopy Loyalty6

Redeem a Reward

ActionIn the docs only

Marks a reward as used from outside the Loopy Loyalty app, so a gift handed over in another system also closes it on the card.

When to use it
the reward is applied as a discount in your online shop and you want the card to reflect it.
Watch out
treat it as final and add a filter so it only runs on confirmed orders.
Loopy Loyalty7

Redeem a Reward with a Unique ID

ActionIn the docs only

Closes a reward the same way as Redeem a Reward, but finds the member through a unique identifier rather than the default lookup. Handy when your records already carry that identifier.

When to use it
the order in your shop stores the customer reference and you want to skip a search step.
Watch out
the identifier expected is not documented; read it off a Run once result.
Loopy Loyalty8

Search Customer

SearchIn the docs only

Finds members in your program so the next modules act on the right person. A search returns zero, one or several customers, each as its own bundle.

When to use it
before stamping, redeeming or messaging someone identified by data from another app.
Watch out
plan for an empty result, and decide whether that case calls for an enrollment instead.
Loopy Loyalty9

Search Customer by Unique ID

SearchIn the docs only

Looks a member up through a unique identifier, which gives a tighter match than a general search when you already hold the reference.

When to use it
a synced CRM stores the Loopy Loyalty reference next to each contact.
Watch out
like any search, it can come back empty; plan the next step for that case, and confirm the expected ID after connecting.
Loopy Loyalty10

Send Push Message to a Customer

ActionIn the docs only

Delivers a push notification to one member's phone, the fastest way to say thanks or nudge a return visit after an event in your stack.

When to use it
right after Watch Enrollments or Watch Earned Rewards, to speak to that exact person.
Watch out
map the customer from the previous module; an empty value leaves the message with no recipient.
Loopy Loyalty11

Send a Push Message

ActionIn the docs only

Pushes a message without naming a single member in its title, which suggests a wider audience than the per-customer version. Make gives no description, so open the module after connecting to see who it targets.

When to use it
a promotion goes live in your shop and the whole program should hear about it.
Watch out
test on a small audience before switching the scenario on.
Need help

Need help automating Loopy Loyalty with Make?

A person reads every message.

FAQ

Loopy Loyalty and Make: common questions

01Is the Loopy Loyalty Make integration free?
Yes, on the Make side. Loopy Loyalty is a standard app, so it works from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans, Core, Pro, Teams and Enterprise, lower the interval to 1 minute and remove the cap on active scenarios. Every module run counts as an operation, the unit Make bills on your plan. Your Loopy Loyalty subscription is a separate matter.
02What do you need to connect Loopy Loyalty to Make?
A Loopy Loyalty account and a Make account are enough to start. Make's documentation lists no other prerequisite for this app. Add any Loopy Loyalty module, click Create a connection, give it a name if you like, then either authorize Make on the page that opens or paste the key your account provides, and click Save. The same connection then serves all 16 modules, so you only do this once per account. Since Make's documentation for this app is limited, check the available fields right after saving.
03Do Loopy Loyalty triggers fire instantly in Make?
No. Make does not document their type, but going by their names, all 5 Loopy Loyalty triggers are scheduled, which means Make checks the app on the scenario's schedule rather than being called the moment something happens. A new scenario checks every 15 minutes by default. On the Free plan, 15 minutes is also the shortest interval; paid plans go down to 1 minute. In practice, a new member or a used reward reaches your other tools with a delay tied to the schedule you set on the first module.
04What if a Loopy Loyalty module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Loopy Loyalty API from inside the scenario, with the connection you already created, so you are not limited to the 15 named modules. You write the request yourself, which calls for the app's own API reference because Make's documentation on Loopy Loyalty is limited. For everything else, the 16 modules cover the core of a loyalty program: enrollments, stamps, rewards, customer searches and push messages. Test any new request with Run once before switching the scenario on.
05Should you use Make or n8n for Loopy Loyalty?
It depends on your criteria. On Make, Loopy Loyalty comes with 16 ready modules, 5 scheduled triggers and Make an API Call for the rest, and it runs from the Free plan. The same app often has an n8n node too, so check whether it covers the modules you need before choosing. Beyond that, pick the tool your team already knows, and compare how each one handles your other apps. A side-by-side comparison of both tools is linked in the section above.