FlowRunner
PricingContact
Theme
Start Free

Boomerangme

Loyalty & Referral

Issue and manage digital wallet loyalty cards with Boomerangme, covering customers, Apple and Google Wallet passes, stamps, and points. Agents enrol members and push balance updates straight to the phone.

1 trigger 20 actions API key available
On New Customer fires when someone signs up through a wallet pass link
Agent reads the card template with Get Template to resolve its custom field, reward tier and membership tier IDs
Agent issues the card with Create Card and captures the Apple, Google and PWA install links
The customer receives their install link, with no file to download and no app to install
Agent confirms the card exists with the expected starting balance using Get Card
Where the signup matches an existing customer by phone or email, a manager decides whether to issue a second card or point the person at the one they already hold

What This Integration Enables

The thing to understand about Boomerangme is where the card ends up. It is not a row in a loyalty database that a customer can look up if they think to. It is a pass in Apple Wallet or Google Wallet, on the lock screen, that updates itself. When an agent calls Add Stamps, the customer's phone shows a new stamp within seconds, whether or not they are still in the shop. That immediacy is the whole value of the product, and it is also the reason this connector needs a different kind of care from a CRM connector.

FlowRunner agents handle the mechanical half completely: create the customer record, issue the card from the right template, return the install links, record stamps, points, visits and spend as the transactions happen, and assign a membership tier when somebody subscribes. Nothing about that needs a human, and doing it by hand at a counter is where loyalty programs quietly fall apart. The half that does need a human is the half that takes value away, because a balance the customer has already seen on their phone is a promise you have already made. That is where human-in-the-loop belongs on this connector, and it is a small enough number of cases that a person can genuinely look at each one.

Without FlowRunner

Stamps live on paper A lost card is a lost customer relationship, and the balance goes with it
Balance updates need a person Someone at the counter has to remember to stamp, and to stamp the right number
Spend and rewards tracked separately The point of sale knows what was spent, the loyalty program finds out later or not at all

With FlowRunner

The card lives on the phone The pass sits in Apple Wallet or Google Wallet and updates without the customer doing anything
Balance moves with the transaction Stamps, points, visits and spend are recorded by the system that saw the purchase happen
Reversals are a decision A refund does not silently strip visible progress from a customer's pass

Use Case Scenarios

Signup to installed pass, without a counter conversation

Someone fills in a signup form. The agent calls Create Customer with their details and the store's own identifier in the external user ID field, so the two systems can be reconciled later. It then calls Create Card against the right template and receives hosted install links for Apple Wallet, Google Wallet and PWA. The install link goes out by Gmail or SMS, the customer taps once, and the pass is on their phone. No file download, no app, no staff time.

Spend recorded by the system that saw it

An order completes in Shopify. The agent looks up the customer by email with List Customers, finds their card with List Cards, and calls Add Transaction Amount so cashback and tier progression are calculated from the real basket value rather than an estimate. On stamp programs the same flow calls Add Stamps with the purchase amount and a comment for the transaction history. When the balance crosses a reward threshold the pass updates on its own, and the customer sees the reward unlock without anyone telling them.

Balance reporting for the people who set the offers

A weekly flow calls List Cards across the account and writes stamp and point balances into Google Sheets so the marketing owner can see distribution rather than averages: how many cards sit one stamp short, how many have not moved in ninety days, which template is actually converting. One detail matters when building this: list responses return per-card lifetime totals such as visits and rewards empty, so the flow fetches individual cards with Get Card for the cohort it wants those figures for, rather than reporting zeros as facts.

Human-in-Loop Highlight

The gate on this connector is the refund clawback, and it sits on Subtract Stamps and Subtract Points. Here is why it cannot be automatic. When the original purchase was recorded, the customer's pass updated on their phone. They saw the stamp. They may have been told at the counter that one more visit earns the free coffee. When the refund comes through days later and a rule quietly subtracts that stamp, the next thing that happens is a conversation your counter staff have to have without any context.

So the agent prepares the reversal and stops. It resolves the card with Get Card, reads the balance and the reward tiers, works out the exact adjustment the refund implies, and asks the store manager: "Refund of 34.50 on order 8812 for Jane Roe. Her card currently shows 9 of 10 stamps toward Free Coffee. Reversing this refund removes 2 stamps and takes her back to 7. Claw back, or absorb it?" The manager knows things the agent does not: that the refund was the shop's fault, that Jane comes in twice a week, that two stamps are worth less than the goodwill. They answer in one tap and the agent applies exactly that, with a comment written into the card's transaction history so the next person to look can see why. Delete Card carries a harder version of the same rule, because it removes the pass from the customer's wallet along with its balance and cannot be undone.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via preferred channel
Human decides
Agent resumes with decision

Agent Capabilities

20 actions

Cards

4
  • List Cards List the wallet loyalty cards issued from your templates, optionally narrowed to a single template or to one customer by ID, email or phone. Results are paginated. Note that per-card lifetime totals such as visits and rewards come back empty in list responses, so fetch a single card when those figures matter.
  • Get Card Retrieve one card by ID, including its balance, membership tier, available reward tiers, custom field values and the customer it belongs to. Also returns the install, share and QR links plus platform-specific Apple, Google and PWA install links.
  • Create Card Issue a new card to an existing customer from one of your templates. Returns hosted install links the customer opens to add the pass to Apple Wallet, Google Wallet or as a PWA, so there is no file to download. Custom field values must reference the field IDs configured on the template.
  • Delete Card Permanently delete a card, removing the pass from the customer's wallet along with its balance. This cannot be undone. Used to honor an erasure request or to clear test cards.

Card Balance

8
  • Add Stamps Add stamps to a stamp card, advancing the customer toward their next reward. Optionally records the purchase amount that earned them and a comment for the transaction history. This is the point-of-sale action on stamp programs.
  • Subtract Stamps Remove stamps from a stamp card, reversing an accrual recorded in error or clawing back after a refund. Because the customer has already seen the stamps on their pass, this belongs behind a human decision rather than an automatic rule.
  • Add Points Credit loyalty points to a card, typically on a cashback or points-based program. Optionally records the purchase amount that generated them and a comment.
  • Subtract Points Debit points from a card, when a customer spends them or when an earlier accrual is reversed. Same reasoning as stamps: it removes value the customer can already see.
  • Add Visit Record one or more visits against a card, for programs that reward attendance rather than spend. Optionally records the purchase amount and a comment. Used when a customer checks in at a venue.
  • Add Transaction Amount Record a spend amount against a card so cashback and tier progression are calculated from real transaction value. Used on cashback and membership programs driven by customer spend.
  • Receive Reward Award a specific reward tier to a card, marking it as earned and available to redeem. The reward is identified by its reward tier ID from the card's template. Used to grant a reward outside the normal stamp or points threshold, which is usually a goodwill decision and worth confirming.
  • Set Membership Tier Assign a membership tier to a card for a fixed period, such as a monthly or yearly subscription level, and optionally enable automatic renewal. Used on membership programs when a customer upgrades or renews.

Customers

5
  • List Customers List the customers on the account, optionally filtered by exact phone number or email address. Results are paginated and include contact details and segment membership. Used to find the customer ID needed to issue a card, and to detect a duplicate signup before a second card is created.
  • Get Customer Retrieve one customer by ID, returning name, contact details, date of birth, your own external user ID and their segments.
  • Create Customer Create a customer record, which is the prerequisite for issuing a card. Store your own system's identifier in the external user ID field so the two can be reconciled later. Returns the created customer with its generated ID.
  • Update Customer Update an existing customer's details. Only supplied fields change, so a single value such as an email address can be corrected without resending the whole profile.
  • Delete Customer Permanently delete a customer record. This cannot be undone and removes the profile any of their cards are linked to. Used to honor a data erasure request.

Templates and Locations

3
  • List Templates List your card templates, which define each program's type, custom fields, reward tiers, membership tiers and card design. Used to find the template ID required when issuing a card.
  • Get Template Retrieve one template by ID, including its custom field definitions, reward tiers, membership tiers, appearance settings and tracking links. This is where the reward tier and membership tier IDs the balance actions need come from.
  • List Locations List the store locations on the account, each with its address, coordinates, the lock-screen message shown when a customer is nearby, and the templates it applies to. Used to review which venues trigger location-based pass notifications.

Triggers

1 triggers

Event Triggers

1
  • On New Customer Fires when a new customer is created in your Boomerangme account, for example after someone installs a wallet pass from a signup link. Boomerangme exposes no webhook management API, so this trigger polls the customer list on a configurable interval and reports customers it has not seen before. Used to start the enrollment flow the moment a person signs up, rather than on the next batch import.

Frequently Asked Questions

What can FlowRunner do with Boomerangme?

FlowRunner agents can run List Cards, Get Card, and Create Card in Boomerangme, plus 17 more actions.

Does connecting Boomerangme to FlowRunner require OAuth?

No. Boomerangme connects to FlowRunner with an API key, no OAuth flow required.

Can Boomerangme trigger a FlowRunner workflow automatically?

Yes. Boomerangme supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with Boomerangme

$100 in credits. No card required. Connect in minutes.