Resources · Make integration

Boomerangme Make integrationAutomate Boomerangme with Make.

Can Make update your Boomerangme cards on its own? Yes: the Boomerangme Make integration gives you 43 modules, from 22 triggers to card and customer actions. This guide shows how to link your account, build a first scenario and pick the right module.

Try the Boomerangme integration on MakeSee the 43 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Boomerangme Make integration let you automate?

The Boomerangme Make integration lets Make read events from your Boomerangme account and act on its cards and customers. You build a scenario, the automation itself, out of modules: each module is one brick, either a trigger that starts the run, an action that changes something, or a search that finds records.

Credit a card when a sale happens somewhere else. Your sales tool records the purchase, Search for Cards finds the matching card, and Add a Point to a Card or Add a Stamp to a Card credits it. Nobody retypes the purchase at the counter.

Welcome every new customer. Watch Customer Created Event picks up the new record, Issue a Card gives that person a card, and Send a Push can follow with a message. For a referral program, Watch Customer Created Referral Event plays the same role.

Keep an eye on payments. Watch Payment Failed Event and Watch Recurrent Payment Failed Event can feed a task in your team tool, so a failed charge gets a human follow-up instead of sitting unnoticed.

What Make does not give you here is a detailed guide: the Make doc for Boomerangme is marked as limited, with no field list and no module descriptions. Plan a test run before trusting any module. The Make review helps you judge the tool itself, the n8n vs Make comparison covers the other option, and Make troubleshooting helps when a run fails.

Connect

How do you connect your Boomerangme account to Make?

  1. 01

    Add a Boomerangme module

    Open your scenario, click the +, type Boomerangme and pick any module. Its settings panel opens with a Create a connection button. A connection is your Boomerangme account linked to Make once, then reused by every Boomerangme module.

  2. 02

    Name it and authorize Make

    Give the connection a name if you like, for example the name of your shop. Then either authorize Make on the Boomerangme page that opens, or paste the key Boomerangme gives you, depending on what the connection window asks for.

  3. 03

    Save and check the fields

    Click Save. Back in the module, Make can now list what it reads from your account. If the lists fill in, the link works and you can move on to the next module.

First scenario

Your first scenario: a point for every sale

GoalWhen a sale is recorded in another app, Make finds the customer's Boomerangme card and adds a point to it.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Add the trigger of the app where your sales land, for instance your online store or your billing tool.

  2. 02

    Find the card

    Click the + on the right, add Boomerangme's Search for Cards and create your connection. Map the customer data from the first module into the search so Make looks up the right person.

  3. 03

    Add the point

    Add Add a Point to a Card after the search and map the card it returned. Each card found becomes one bundle, one item passed from module to module, so each one gets its point.

  4. 04

    Test with Run once

    Record a test sale, then click Run once. Open the bubble above each module to read the bundles it received and confirm the point landed on the expected card.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, and switch the scenario on. Each module run counts as an operation, the unit Make counts on your plan.

Triggers

Which Boomerangme events can start a scenario?

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

Boomerangme1Watch Card Installed Event

Watch Card Installed Event

triggerIn the docs only

This trigger starts your scenario when a card is installed; going by the name, that gives you the moment a customer actually takes your card with them.

How it fires
scheduled, Make checks the app on the scenario's schedule, every 15 minutes by default, so the event reaches you at the next check.
When to use it
send a thank-you push or tag the customer in your CRM once the card is in their hands.
Watch out
the Make doc does not say what an installation contains, so run the scenario once and read the bundle before mapping anything.
Boomerangme2Watch Company Removed Event

Watch Company Removed Event

triggerIn the docs only

You get a run each time a company is removed from Boomerangme, handy if you manage several businesses or brands from one place.

How it fires
scheduled; Make asks Boomerangme for new removals each time the scenario runs, on the clock set on the first module.
When to use it
archive that company's rows in a spreadsheet or close its folder in your project tool.
Watch out
the doc does not list which company details still come through after the deletion.
Boomerangme3Watch Created Company Event

Watch Created Company Event

triggerIn the docs only

With this trigger, a newly created company in Boomerangme becomes the starting point of your scenario, so the rest of your setup can follow without a manual step.

How it fires
scheduled, which means Make polls the app at the interval of the scenario rather than being called by Boomerangme.
When to use it
open a matching record in your CRM or notify the person who onboards new locations.
Watch out
test it with a real company first, because the doc gives no example of what Make receives.
Boomerangme4Watch Customer Created Event

Watch Customer Created Event

triggerIn the docs only

Every new customer added in Boomerangme can kick off a scenario here, which is the cleanest entry point for any welcome sequence.

How it fires
scheduled. The scenario's clock decides when Make looks for new customers, every 15 minutes unless you change it.
When to use it
copy the customer into your email tool, then issue a card or send a welcome push.
Watch out
customers you create from Make with Create a Customer will also land here, so do not chain the two in a way that recreates the same person.
Boomerangme5Watch Customer Created Referral Event

Watch Customer Created Referral Event

triggerIn the docs only

This one reacts to customers who arrive through a referral, so you can reward the right people without checking the list by hand.

How it fires
scheduled; Make checks Boomerangme for new referral sign-ups whenever the scenario's schedule comes around.
When to use it
add a reward or a bonus stamp once a referred customer shows up, and log it in a sheet.
Watch out
the doc does not say whether the referrer appears in the bundle; run it once and check before you build the reward step.
Boomerangme6Watch Expired Card Event

Watch Expired Card Event

triggerIn the docs only

When a card reaches its expiry, this trigger hands it to your scenario, which turns a silent loss into a chance to win the customer back.

How it fires
scheduled, Make reads the app at the rhythm set on the first module rather than at the exact second the card expires.
When to use it
email the customer an offer or flag them for a call from your team.
Watch out
an expired card may not accept new stamps or points, so test any follow-up action on it before going live.
Boomerangme7Watch Feedback Created Event

Watch Feedback Created Event

triggerIn the docs only

Fresh feedback from your customers lands in your scenario through this trigger, so a comment never stays unread in the app.

How it fires
scheduled; the scenario's schedule tells Make when to fetch new feedback from Boomerangme.
When to use it
post each new piece of feedback in your team chat, or send low scores to the manager of the shop.
Watch out
the Make doc does not describe the feedback fields, so map only what you see in a real bundle after Run once.
Boomerangme8Watch Issued Card Event

Watch Issued Card Event

triggerIn the docs only

Each card issued in Boomerangme can start a scenario here, whether your staff issued it or another scenario did it for you.

How it fires
scheduled, Make polls Boomerangme at the scenario's interval, every 15 minutes by default on a new scenario.
When to use it
keep a register of issued cards in a spreadsheet, or tell your accounting tool a new member joined.
Watch out
if a scenario issues cards with Issue a Card, those cards also come back through this trigger, so avoid feeding them into another Issue a Card.
Boomerangme9Watch Manager Created Event

Watch Manager Created Event

triggerIn the docs only

This trigger tells your scenario that a new manager account exists in Boomerangme, useful when access to several tools has to follow.

How it fires
scheduled; Make checks for new managers on the schedule of the first module, not the moment the account is created.
When to use it
open the same person's access in your team tools, or post a note to the owner.
Watch out
the doc gives no detail on the manager data sent, so confirm the email or name is there with a first test.
Boomerangme10Watch Manager Removed Event

Watch Manager Removed Event

triggerIn the docs only

Removing a manager in Boomerangme can start a scenario with this trigger, which keeps your other tools in step when someone leaves.

How it fires
scheduled, which means the removal shows up at the next check Make runs on the scenario's clock.
When to use it
close that person's access elsewhere or record the departure in your HR sheet.
Watch out
removal steps in other tools are hard to reverse, so run the scenario once with a test manager before switching it on.
Boomerangme11Watch Payment Failed Event

Watch Payment Failed Event

triggerIn the docs only

A failed payment on your Boomerangme account reaches your scenario through this trigger, so nobody has to spot it in the dashboard.

How it fires
scheduled; Make asks Boomerangme for failed payments at the interval set on the first module.
When to use it
create a task for the person who handles billing, or alert your finance channel.
Watch out
the doc does not say which payments count here, so compare with Watch Recurrent Payment Failed Event on a real case before building both.
Boomerangme12Watch Payment Refunded Event

Watch Payment Refunded Event

triggerIn the docs only

Refunds recorded in Boomerangme can open a scenario with this trigger, which keeps your books aligned with what really happened.

How it fires
scheduled, Make reads new refunds on the scenario's schedule, every 15 minutes unless you pick another interval.
When to use it
add a refund line to your accounting sheet or warn the person who reconciles payments.
Watch out
check the first bundle to see which amount and reference arrive, since the Make doc does not list them.
Boomerangme13Watch Payment Successful Event

Watch Payment Successful Event

triggerIn the docs only

Every successful payment becomes a run of your scenario, giving you a clean feed of what went through.

How it fires
scheduled; the clock on the first module sets how often Make asks Boomerangme for new payments.
When to use it
send the payment to your invoicing tool, or post a short note in a sales channel.
Watch out
each payment found costs at least one operation per module, so a busy account uses more of your plan than a quiet one.
Boomerangme14Watch Recurrent Payment Failed Event

Watch Recurrent Payment Failed Event

triggerIn the docs only

This trigger isolates failures on recurring payments, so a subscription problem gets its own follow-up path.

How it fires
scheduled, Make checks the app at the scenario's interval and picks up the failures found since the last check.
When to use it
send a reminder email to update a payment method, or open a support ticket.
Watch out
if you also use Watch Payment Failed Event, test both on the same case: the doc does not say whether one failure shows up in both.
Boomerangme15Watch Removed Card Event

Watch Removed Card Event

triggerIn the docs only

A card removed from Boomerangme can start your scenario here, the signal that a customer has probably left your program.

How it fires
scheduled; Make fetches removals on the schedule of the scenario, not at the exact moment they happen.
When to use it
update the customer's status in your CRM or stop the emails aimed at card holders.
Watch out
actions on a removed card will likely fail, so send the follow-up to your other tools, not back to Boomerangme.
Boomerangme16Watch Scanned Card Event

Watch Scanned Card Event

triggerIn the docs only

Each scan of a card at your counter can feed a scenario, which is the closest thing to a visit log this app gives Make.

How it fires
scheduled, so scans arrive in groups at each check Make runs, every 15 minutes by default.
When to use it
count visits per shop in a spreadsheet, or send a push once a customer comes back.
Watch out
do not answer a scan with an action that adds a visit if the scan already counts one in Boomerangme, or the customer gets it twice.
Boomerangme17Watch Tariff Payment Created Event

Watch Tariff Payment Created Event

triggerIn the docs only

This trigger watches payments tied to a tariff in Boomerangme; going by the name, that is your plan with the app rather than a customer purchase.

How it fires
scheduled; Make checks for new tariff payments on the clock of the first module.
When to use it
save the receipt details to your accounting folder or notify the person paying the bills.
Watch out
the doc does not define a tariff payment, so run it once and read the bundle before relying on this reading of the name.
Boomerangme18Watch Updated Card Balance

Watch Updated Card Balance

triggerIn the docs only

When the balance on a card changes, this trigger passes the card to your scenario, so you can react to progress instead of single actions.

How it fires
scheduled, Make reads updated balances at the scenario's interval rather than at each change.
When to use it
message a customer who is close to a reward, or keep a live balance column in a sheet.
Watch out
the add and subtract modules in your own scenarios also move balances, so avoid sending them back into a module that changes the balance again.
Boomerangme19Watch User Template Activated Event

Watch User Template Activated Event

triggerIn the docs only

Activating a template in Boomerangme can start a scenario here, a sign that a card design or program is about to go live.

How it fires
scheduled; Make asks for newly activated templates each time the scenario's schedule runs.
When to use it
tell your marketing team a program is live, or log the launch in your planning tool.
Watch out
the doc does not explain what a user template holds, so confirm on one real activation what the bundle carries.
Boomerangme20Watch User Template Created Event

Watch User Template Created Event

triggerIn the docs only

A new template created in your Boomerangme account shows up in your scenario through this trigger, well before it is activated.

How it fires
scheduled, Make polls the app on the scenario's clock, every 15 minutes if you keep the default.
When to use it
ask for a review of the new template in your team chat before anyone switches it on.
Watch out
the doc does not say whether unfinished templates count too; check the first bundle and add a filter if you only want finished ones.
Boomerangme21Watch User Template Removed Event

Watch User Template Removed Event

triggerIn the docs only

This trigger runs your scenario when a template disappears from Boomerangme, which helps you keep other tools from promoting a program that is gone.

How it fires
scheduled; the removal reaches Make at the next check set by the first module.
When to use it
pause the related email campaign or mark the program as closed in your planning sheet.
Watch out
once removed, the template may carry few details, so store what you need when it is created or updated.
Boomerangme22Watch User Template Updated Event

Watch User Template Updated Event

triggerIn the docs only

Any change to one of your templates can start a scenario with this trigger, which keeps a trace of who changed what and when.

How it fires
scheduled, Make looks for updated templates on the scenario's schedule, so several edits may arrive together.
When to use it
log each update in a sheet, or warn the team that prints in-store material from the template.
Watch out
the doc does not say which fields changed are sent, so compare two bundles after two small edits.
Modules

What can Make do in Boomerangme?

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

Boomerangme1

Add a Point to a Card

ActionIn the docs only

Credits a point to a customer's card, so a purchase recorded in another tool shows up in their loyalty balance.

When to use it
after a sale in your store or billing app, once Search for Cards has found the card.
Watch out
map the card from a search rather than typing it, or every run credits the same card.
Boomerangme2

Add a Reward to a Card

ActionIn the docs only

Puts a reward on a card directly, useful when the customer earns it outside the usual stamp or point path.

When to use it
a referral that pays off, a feedback you want to thank, a birthday flagged in your CRM.
Watch out
this gives the reward; the customer claiming it is a separate step, handled by Receive a Reward from a Card.
Boomerangme3

Add a Score to a Card

ActionIn the docs only

Raises the score on a card, for programs that count a score rather than stamps or points.

When to use it
your card template runs on a score and an event elsewhere, such as a completed order, should move it up.
Watch out
pick the module that matches your card type; a score module on a stamp card is likely to fail, so test it with Run once.
Boomerangme4

Add a Stamp to a Card

ActionIn the docs only

Adds one stamp to a card, the digital version of the stamp you give at the counter on a coffee card.

When to use it
an online order or booking should count toward the same stamp card as an in-store visit.
Watch out
if your staff also stamp by scanning, make sure the same purchase does not go through both paths.
Boomerangme5

Add a Visit to a Card

ActionIn the docs only

Records a visit on a card, for programs that reward how often a customer comes rather than what they spend.

When to use it
a booking tool marks an appointment as done and you want it counted as a visit.
Watch out
Watch Scanned Card Event may already reflect a visit, so do not chain the two on the same customer.
Boomerangme6

Add an Amount to a Card

ActionIn the docs only

Adds an amount to a card's balance, which suits cashback or prepaid programs where money, not stamps, is counted.

When to use it
map the total of an order from your shop so the customer's balance grows with what they spend.
Watch out
check on a test card how the amount is read before mapping real totals; the doc gives no format.
Boomerangme7

Create a Customer

ActionIn the docs only

Adds a new customer record to Boomerangme from any other source, so nobody types the same details twice.

When to use it
someone signs up through a form or places a first order and should join your loyalty program.
Watch out
run Search for Customers first; creating blindly leaves you with duplicate people and split balances.
Boomerangme8

Edit a Customer

ActionIn the docs only

Changes the details of an existing customer, keeping Boomerangme in line with your CRM or shop account.

When to use it
a customer updates their email or phone somewhere else and the loyalty record should follow.
Watch out
it needs the customer found first, usually by Search for Customers; an empty mapped field may overwrite what was there.
Boomerangme9

Issue a Card

ActionIn the docs only

Creates a loyalty card for a customer, the step that actually lets them start collecting.

When to use it
right after Create a Customer, or when a new sign-up comes in from your website form.
Watch out
issuing twice for the same person may give them two cards, so check with Search for Cards when in doubt.
Boomerangme10

Make an API Call

ActionIn the docs only

Calls any endpoint of the Boomerangme API with the connection you already set up, for whatever the listed modules leave out.

When to use it
you need an operation none of the 43 modules covers and Boomerangme's API offers it.
Watch out
you write the request yourself, so keep the Boomerangme API reference open; Make does not document it here.
Boomerangme11

Receive a Reward from a Card

ActionIn the docs only

Marks a reward on a card as received, closing the loop once the customer has actually been given their gift or discount.

When to use it
your checkout confirms the free item was handed over and Boomerangme should stop showing it as pending.
Watch out
do not confuse it with Subtract a Reward from a Card, which removes a reward rather than marking it as used.
Boomerangme12

Redeem a Coupon on a Card

ActionIn the docs only

Uses up a coupon held on a card, so the same offer cannot be claimed a second time.

When to use it
your online shop applies the coupon at checkout and Boomerangme needs to know it has been spent.
Watch out
a redemption is hard to reverse, so test the flow on a test card with Run once before live orders reach it.
Boomerangme13

Search for Cards

SearchIn the docs only

Finds cards in Boomerangme and hands them to the next module, the step that turns a customer's details into the card you want to change.

When to use it
before any add or subtract module, when you only know who the customer is.
Watch out
a search can return zero, one or several cards, and each one becomes its own bundle, so the next module runs once per card.
Boomerangme14

Search for Customers

SearchIn the docs only

Looks up customers in Boomerangme, so your scenario can check whether someone already exists before doing anything else.

When to use it
ahead of Create a Customer to avoid duplicates, or ahead of Edit a Customer to find the record.
Watch out
no match returns no bundle and stops that path, so plan for it if you want to create the customer in that case.
Boomerangme15

Send a Push

ActionIn the docs only

Sends a push message through Boomerangme, reaching customers where their card lives instead of in a crowded inbox.

When to use it
announce a reward that just became available, or thank someone after a visit.
Watch out
placed after a trigger that picks up many events at once, it sends one push per bundle, so filter first.
Boomerangme16

Subtract a Point from a Card

ActionIn the docs only

Takes a point back off a card, the fix when a purchase that earned it gets cancelled.

When to use it
your shop records a refund or a cancelled order and the point it gave should disappear.
Watch out
it only corrects what Add a Point to a Card did; find the same card with Search for Cards first.
Boomerangme17

Subtract a Reward from a Card

ActionIn the docs only

Removes a reward from a card, for a reward that was given by mistake or no longer applies.

When to use it
a referral turns out invalid or an order that unlocked the reward is refunded.
Watch out
to record that the customer used the reward, Receive a Reward from a Card is the right module, not this one.
Boomerangme18

Subtract a Score from a Card

ActionIn the docs only

Lowers the score on a card, the counterpart of Add a Score to a Card for score-based programs.

When to use it
a returned order or a cancelled booking should take back the score it earned.
Watch out
run it on a test card first to see how the app handles a score that would drop below zero.
Boomerangme19

Subtract a Stamp from a Card

ActionIn the docs only

Removes a stamp from a card, so a mistaken or cancelled purchase does not bring the customer closer to a free item.

When to use it
a staff member flags a wrong stamp in a form, or an online order is refunded.
Watch out
map the card from a search or a trigger bundle; a hard-typed card would lose stamps on every run.
Boomerangme20

Subtract a Visit from a Card

ActionIn the docs only

Cancels a visit recorded on a card, which keeps visit-based rewards honest.

When to use it
an appointment counted as done gets marked as a no-show in your booking tool.
Watch out
if Watch Updated Card Balance starts another scenario, make sure that one does not add the visit back.
Boomerangme21

Subtract an Amount from a Card

ActionIn the docs only

Takes an amount off a card's balance, for a customer who spends cashback or prepaid credit.

When to use it
your checkout applies the balance to an order and Boomerangme must show what is left.
Watch out
test with a small amount on a test card, because the doc does not say what happens when the balance is too low.
Need help

Need help automating Boomerangme with Make?

A person reads every message.

FAQ

Boomerangme and Make: common questions

01Is the Boomerangme Make integration free?
Yes, Boomerangme is a standard app in Make, so you can use it from the Free plan. That plan keeps you to 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes per run, 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 and lift the limit on active scenarios. Your Boomerangme subscription is separate and not covered here.
02What do you need to connect Boomerangme to Make?
A Boomerangme account and a Make account are enough to start. The Make doc lists no special prerequisite for this app. You add any Boomerangme module, click Create a connection, then either authorize Make on the Boomerangme page or paste the key the app gives you, and click Save. The same connection then serves all 43 modules, including Make an API Call, so you only do it once per account.
03Do Boomerangme triggers in Make fire in real time?
No. All 22 Boomerangme triggers are scheduled: Make checks the app on the scenario's schedule, every 15 minutes by default, and 1 minute at best on a paid plan. Make lists no instant trigger for this app, and the types come from the module names since the doc is limited. If a delay of a few minutes is a problem, move the logic to the app that records the event first and call Boomerangme actions from there.
04What if a Boomerangme module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Boomerangme API with the connection you already have, so an operation missing from the 19 actions and 2 searches is still within reach. You write the request yourself, with the Boomerangme API reference open, because Make marks its own documentation for this app as limited. Test the call with Run once and read the response bundle before mapping it further.
05Should you use Make or n8n for Boomerangme?
It depends on what your team already runs and on what each tool offers for this app. On the Make side, Boomerangme brings 43 modules, 22 of them triggers, all scheduled. This guide does not cover whether n8n has a Boomerangme node, so check that first if you lean toward n8n. The comparison page linked in the introduction sets out the criteria for the two tools without taking sides, so you can decide on your own terms.
Same platform

Other docs you might need on this stack.

Browse all integrations