Zapier Loyalty Automation: Five Zaps That Run a Wallet Loyalty Card
Zapier loyalty automation connects the apps you already use to a MSTRMND wallet card, with no code for simple rules. It runs through webhooks and the API on the Business plan. Here are five recipes, what each needs and where it stops.
Via API and webhooks, Business plan
Build your first Zap
- Pick a trigger in another app
- Match the customer
- Call the card API
- Build the reverse
Start with one rule and test it.
What does Zapier loyalty automation do?
It lets an event in one app cause an action on a customer’s loyalty card. Zapier calls each automation a Zap: a trigger, such as a paid invoice or a booked appointment, followed by one or more actions. For MSTRMND, the actions are calls to the API, which the Business plan includes along with webhooks.
That makes Zapier loyalty automation the quickest route from “I use a tool MSTRMND does not natively connect to” to “my customers’ cards update by themselves”. It is not the only route, and it is not free of effort. It is the one that needs the least code. New to wallet cards? Start with our guide to digital loyalty cards.
How a Zap talks to the card
A Zap reaches MSTRMND by calling the API, using a webhook or HTTP step in Zapier. The API offers the actions most loyalty rules need:
- Customers and cards: create a customer, issue a card, find a card.
- Earning: add a stamp, a point, a visit, a purchase or a transaction amount.
- Redeeming and reversing: subtract the same, or receive a reward.
- Messaging: send a push notification or an SMS to a customer.
Zapier’s own steps handle the rest: filtering, formatting and waiting. A Zap can, for example, wait a day after a visit and then send a message.
Five Zaps and what each needs
Each Zap pairs a trigger in another app with a call to the MSTRMND API.
| Zap | Trigger | Card action | Reverse it with |
|---|---|---|---|
| Sign-up to card | New form entry | Create customer, issue card, send SMS | Delete or edit the card |
| Paid invoice to cashback | Invoice paid | Add transaction amount | Subtract transaction amount |
| Booking to visit | Appointment completed | Add visit | Subtract visit |
| Order to points | Order completed | Add point | Subtract point |
| Lapsed customer to message | Scheduled check | Send push | Not applicable |
Five Zaps worth building first
1. New form submission to a new card
A customer fills in a form on your website or a sign-up sheet. The Zap creates the customer, issues the card and sends the card link by SMS. The customer is on your list before they have left the page.
2. Paid invoice to cashback
An accounting or invoicing tool marks an invoice paid. The Zap adds the amount to the customer’s card as cashback. A credit note triggers a second Zap that subtracts it.
3. Booking completed to a visit
A booking tool marks an appointment as done. The Zap adds a visit, so a salon or clinic does not need the receptionist to scan anything.
4. Ticket or order to points
A shop or ticketing tool completes an order. The Zap adds points equal to the order value. A refund Zap reverses them.
5. Lapsed customer to a message
A scheduled Zap checks for customers who have not visited in a set period and sends a push message with an offer. It is the simplest win-back automation you can build.
Customer list limits by plan
Any automation that creates cards fills the list faster. Check the ceiling before you build.
Bars show the order of the limits, not a scale. Source: MSTRMND plan limits, checked 11 October 2026.
What you need before you start
- The Business plan, which includes API and webhooks.
- A Zapier account on a plan that includes the steps you need. Check Zapier’s current plans, because they change.
- The API credentials from your MSTRMND account.
- A matching key for customers: email or phone.
- A written reward rule, including refunds.
Where Zapier stops
Zapier runs one Zap at a time on a single event. It is poor at complex branching and at working through a large batch in one go. If your rule needs a lot of conditions, or you are processing hundreds of records overnight, a tool built for that, such as Make, or a developer’s code, will be easier to maintain. Zapier is also a separate subscription with its own usage limits.
Test it before customers see it
A Zap that works once is not the same as a Zap that works every day. Before you tell customers about the programme, run this short test of your Zapier loyalty automation.
- A real card. Issue a test card to your own phone, trigger the Zap and watch the balance change in the wallet.
- A refund. Trigger the reverse Zap and confirm the balance goes back to where it was.
- A duplicate. Send the same customer twice and check that you end up with one card, not two.
- A failure. Switch off a field the Zap needs and check that you hear about it, instead of finding out from a customer.
- A busy hour. Send several events close together and confirm each one lands once.
Write down what you tested and what happened. If something changes later, such as a form field or a payment tool, that note saves an afternoon of guessing.
Frequently asked questions
Does MSTRMND have an official Zapier app?
The Business plan includes API and webhooks, and Zapier can call an API with its webhook or HTTP step, so a Zap can drive a card without a dedicated app. Check your account on a call for anything more specific. The published connection is through the API, so plan for that.
Do I need to write code?
Not for simple rules. Zapier’s steps let you map fields and call the API without code. You will need the API credentials from your MSTRMND account and a clear rule. For matching logic, large batches or several reward types, a developer or Make may be easier to maintain.
What does it cost?
MSTRMND’s side is the Business plan: £115 a month billed annually, which includes API and webhooks. Zapier is a separate subscription with its own limits, so check its current plans before you build. Together they replace a build that would otherwise need a developer’s time.
Can a Zap reverse a reward?
Yes. Each add action has a matching subtract, so a Zap triggered by a refund or credit note can take a stamp, points or cashback back. Build the reverse Zap at the same time as the forward one, and test both with a real card before you tell customers about the programme.
Key takeaways
- Zapier loyalty automation drives the wallet card through the API and webhooks on the Business plan.
- Five Zaps cover most rules: sign-up, invoice, booking, order and lapsed customer.
- Every add action has a matching subtract, so build the reverse Zap too.
- Zapier is best for simple rules on single events, not for large batches.
- Zapier is a separate subscription. Check its current plans.