Loopy Loyalty
Loyalty & ReferralRun digital stamp-card loyalty programmes with Loopy Loyalty, enrolling customers into Apple and Google Wallet passes. Agents award stamps off verified transactions and push the updated card to the phone.
What This Integration Enables
Loopy Loyalty is the paper punch card moved onto the phone, and that is a narrower and more useful thing than a loyalty platform. There is no app to install and no account to create. A customer opens a hosted URL, the pass drops into Apple Wallet or Google Wallet, and from then on their stamp count is a live object on their lock screen rather than a piece of card they will lose. That makes it a fit for businesses with a counter: coffee, barbers, car washes, sandwich shops, anywhere the loyalty mechanic is a visit count and the friction budget is about four seconds.
The interesting operational problem is that the counter is the worst place to run software. FlowRunner agents solve that by stamping from the transaction rather than from the till. Add Stamps By Unique ID takes an email or phone number, so a cleared payment in your checkout can stamp the right card without anyone at the counter looking up an internal ID. Around that core, agents enrol customers and return the installable pass URL, redeem rewards when someone claims their free item, resync a pass that looks stale on a customer's phone, and push lock-screen messages to one card or to a filtered slice of a whole campaign. The one thing an agent should never do on its own is the last of those.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Stamping from the payment, not the counter
A customer pays. A Stripe payment succeeds, and the agent calls Add Stamps By Unique ID with the buyer's email, matched against the unique email field configured on the campaign. Loopy adds the stamp, and if that stamp crosses the campaign's reward threshold the reward is issued automatically and the pass on the customer's phone updates itself. Nobody at the counter typed anything. If the customer has never enrolled, the agent calls Enrol Customer first and sends the returned hosted pass URL so they can install the card before they leave.
Reward claimed in store, logged everywhere else
On Card Event fires for Reward Received and the agent emails the customer through Gmail to tell them their free item is waiting, which is the message people actually respond to. When they come in and claim it, the agent calls Redeem Rewards with the reward index and, where the till reports it, the scan latitude and longitude so the redemption is attributed to a location from List Locations. The store gets a per-site view of where rewards are being claimed without asking staff to record anything.
Weekly stamp-balance export
A scheduled flow calls List Cards for each campaign, sorted by current stamps, and writes the balances into Google Sheets so the owner can see how many customers sit one stamp short of a reward. That number is the whole business case for a win-back push, and it is the number that decides whether Scenario 1's automation is paying for itself. When a customer reports that their pass looks out of date after a manual correction, the agent calls Resync Card and the phone catches up.
Human-in-Loop Highlight
Send Message To Campaign Cards is the operation that earns a gate here, and it is not about money. It pushes a lock-screen notification to every installed pass in a campaign, optionally filtered by stamp or reward count. That message lands on the phone of every customer who ever enrolled, at whatever hour the flow happens to run, and there is no unsend. A typo, a stale offer, or an audience filter that was meant to say more than five stamps and actually said more than zero, and the whole customer base gets an interruption you cannot take back. So the agent assembles the send and stops, which is the digital andon cord applied to a retail program: the flow halts itself at the step it cannot take back. It posts to the owner: "Win-back push ready for the Loyalty Card campaign. Filter is more than five stamps, no stamp in sixty days, which matches 312 installed passes. Message reads: Your free coffee is still waiting, and it expires Sunday. Send, edit, or cancel?" The owner answers on their phone between customers. The agent sends what was approved, to the audience that was approved. Send Message To Card, which reaches exactly one person, runs without a gate, because the blast radius is the point.
Agent Capabilities
14 actionsCards
6- List Cards List the stamp cards issued for a campaign with paging, free-text search across customer detail values, and sorting. Used to browse enrolled customers or resolve the Card ID that the stamping, redemption and messaging actions need.
- Get Card Retrieve a single stamp card by Card ID with the customer details captured at enrolment, pass status, and stamp and reward totals, optionally including the full transaction event history and earned rewards. Used to inspect one customer's progress.
- Add Stamps Add stamps to a card, or deduct them with a negative number, optionally recording the latitude and longitude of the scan. Rewards are issued automatically once the campaign's threshold is reached. This is the core reward action at the point of sale.
- Redeem Rewards Redeem one or more earned rewards on a card, identifying the reward by its index in the campaign where the first is 1, optionally recording the scan location. Used when a customer claims their free item.
- Delete Card Permanently delete a stamp card, removing the customer's pass and their stamp history. This cannot be undone. Used to honour a customer erasure request or clear test enrolments.
- Resync Card Force a card to re-synchronise with the customer's wallet, pushing the latest stamp count and design to the installed pass. Used when a pass looks out of date after a manual change.
Customers
3- Enrol Customer Enrol a customer into a campaign and issue their digital stamp card, returning a hosted pass URL they open to install it into Apple Wallet or Google Wallet plus the customer ID needed to stamp it later. Customer detail keys must match the campaign's configured field names.
- Get Card By Unique ID Look up a customer's card by email, phone or text instead of the internal Card ID, where the campaign has that unique field configured. Used when your system only knows the customer by email.
- Add Stamps By Unique ID Add stamps to a card identified by email, phone or text rather than the internal Card ID, so a checkout or CRM can stamp directly. A negative number deducts. The campaign must have the matching unique field configured.
Campaigns
3- List Campaigns List every stamp card campaign on the account with its name, short code, reward configuration and status. Used to resolve the campaign ID the enrolment, card and messaging actions require.
- Get Campaign Retrieve one campaign's full configuration, including rewards and stamp thresholds, the data fields collected at enrolment, locations, beacons, expiry rules, card design and terms. Used to inspect how a program is set up before enrolling anyone.
- List Locations List the physical locations configured on the account with name, address, coordinates and the lock-screen message shown when a customer is nearby. Used to review which venues trigger location-based pass notifications.
Messaging
2- Send Message To Card Push a lock-screen message to a single customer's installed pass. Used for personal follow-ups such as a birthday offer or a reminder that a reward is waiting. The customer must have the pass installed.
- Send Message To Campaign Cards Push a lock-screen message to every installed pass in a campaign, optionally narrowed by a stamp or reward filter. Used for campaign-wide announcements and win-back offers, and the operation that should always carry an approval gate.
Triggers
1 triggersEvent Triggers
1- On Card Event Fires when a chosen loyalty event happens on any card in a campaign, such as a customer enrolling, earning a stamp, or redeeming a reward. Loopy Loyalty registers a webhook subscription on the campaign and the flow runs each time a matching event is delivered. Used to drive the follow-up that a stamp card cannot do on its own, from a reward-ready email to a lapsed-customer record in your CRM.
Frequently Asked Questions
What can FlowRunner do with Loopy Loyalty?
FlowRunner agents can run List Cards, Get Card, and Add Stamps in Loopy Loyalty, plus 11 more actions.
Does connecting Loopy Loyalty to FlowRunner require OAuth?
Loopy Loyalty uses a custom authentication method to connect to FlowRunner.
Can Loopy Loyalty trigger a FlowRunner workflow automatically?
Yes. Loopy Loyalty supports 1 trigger that can start a FlowRunner workflow automatically.
Start building with Loopy Loyalty
$100 in credits. No card required. Connect in minutes.