HighLevel Loyalty Integration: Wallet Cards for Agencies and Their Local Clients
A HighLevel loyalty integration lets a workflow in a client’s sub-account add stamps or points to a wallet card when a booking, payment or form event happens. MSTRMND connects through webhooks and the API on the Business plan. This page covers the set-up, and the limits.
Via API and webhooks, Business plan
Connect HighLevel to a wallet card
- Write the reward rule
- Store credentials as custom values
- Build one workflow per trigger
- Test with a real card
Save the working workflow as a template for the next client.
What does a HighLevel loyalty integration do?
HighLevel runs the follow-up for many local businesses: forms, bookings, pipelines, reminders and reviews. A wallet card adds the one thing those tools do not hold, a reason to come back that sits in the customer’s phone. The link between them is a workflow that tells MSTRMND when something earned a reward.
MSTRMND does not publish a HighLevel app, so the connection is built from HighLevel’s own workflow steps and the MSTRMND API and webhooks, which the Business plan includes. That is more work than a one-click app, and it is also more flexible, because a workflow can use any trigger HighLevel offers. New to wallet cards? Start with our guide to digital loyalty cards.
How a workflow reaches the card
A workflow starts with a trigger in the sub-account, such as an appointment marked as showed, an invoice paid or an opportunity moved to a stage. A webhook step then sends the customer’s phone or email, and the action you want, to the MSTRMND API.
- Find or create the customer and issue a wallet card on first contact.
- Add a stamp, a point or a purchase amount when the trigger fires.
- Subtract when an appointment is cancelled or an invoice is refunded.
- Send a push notification from the same workflow, for example when a customer reaches a reward.
Because the steps live inside HighLevel, the people who already manage the client’s automations can read and change them.
Four HighLevel triggers and the card action each one drives
Each row is one workflow in a client’s sub-account.
| Trigger | Webhook sends | Card action | Best for |
|---|---|---|---|
| Appointment showed | Phone and visit | Add a stamp | Salons, barbers, clinics |
| Invoice paid | Phone and amount | Add points or an amount | Services billed by invoice |
| Appointment cancelled | Phone and visit | Subtract the stamp | Keeping counts honest |
| Days since last visit | Phone | Send a push notification | Win-back nudges |
Why agencies set it up per sub-account
An agency usually manages many businesses from one account, and each business keeps its own sub-account. The loyalty set-up follows the same shape: one card design and one reward rule per business, one workflow per rule.
The practical consequence is that the first build takes the longest. Once one salon’s workflow works, the next barbershop is mostly a copy with a new card and new credentials. Save the working workflow as a template in HighLevel, and the second client takes a fraction of the time.
Rules that suit this set-up
A stamp for every attended appointment
Trigger on the appointment status “showed”, not “booked”. A card that rewards bookings will reward no-shows, and the owner will notice.
Points for paid invoices
Trigger on invoice paid and send the amount, so a bigger spend earns more points. A refund workflow does the reverse.
A win-back nudge
A workflow can wait a set number of days after the last visit and send a push notification to the card. The customer sees it on the lock screen without opening a message app.
A referral reward
When a form from a referral link is submitted, add a bonus to the referrer’s card. The card type for this is built in.
API access by plan
The workflow needs the API, so it needs the Business plan.
Source: MSTRMND plan limits, checked 11 October 2026.
What you need before you start
- The Business plan, which includes API and webhooks.
- A HighLevel account with the sub-account and a plan that allows webhook steps in workflows. Check its current plans.
- The API credentials from your MSTRMND account, kept as custom values in the sub-account rather than typed into each step.
- A matching key for customers: phone or email, used the same way everywhere.
- A written reward rule for each client.
Where it stops
There is no native HighLevel app listed for MSTRMND, so someone has to build and maintain the workflows. If a trigger fires twice, a customer can be rewarded twice, so a lookup or a flag on the contact is worth adding. Webhook steps can also fail silently unless you add a notification on failure. None of this is unusual for HighLevel, and all of it is easier to plan on day one.
A first-week plan for a HighLevel loyalty integration
Prove one workflow on one client before you copy it.
- Day one: write the reward rule in plain words, including what happens on a cancellation.
- Day two: add the MSTRMND credentials as custom values in the sub-account, so no step has a pasted key.
- Day three: build the sign-up workflow, with a lookup before the create step.
- Day four: build the attended-appointment workflow and its cancellation twin.
- Day five: test with your own card and one friendly customer, then switch the workflows on.
Keep a one-page note for the client that says what each workflow does and who to call if a card looks wrong. Handing over a build with no note is how agencies end up fixing the same thing twice.
Questions to ask before you sign off a build
Before you tell a client the card is live, run through the awkward cases.
- What happens when an appointment is rebooked, rather than cancelled?
- What if two staff mark the same visit as showed?
- Does a customer with two phone numbers become two cards?
- Who gets the failure alert, and do they read it?
If you cannot answer one of these, write the answer down for the client before launch, not after the first complaint.
Frequently asked questions
Is there a HighLevel app for MSTRMND?
No app is published. The connection is built from HighLevel workflow webhook steps and the MSTRMND API, both available on the Business plan. That makes the first build slower than a one-click install, and it lets you use any trigger HighLevel offers.
Can an agency reuse the build for each client?
Mostly. Save the working workflow as a template in HighLevel, then change the card, the credentials and the reward rule for each new business. The structure stays the same, so later clients take far less time than the first one.
What stops a customer being rewarded twice?
Add a lookup or a flag to the workflow. Before the add step, check whether this appointment or invoice has already been rewarded, or write a tag on the contact when it has. Without that check, a trigger that fires twice can add two stamps for one visit.
What does it cost?
MSTRMND’s side is the Business plan, £115 a month billed annually, which includes API and webhooks. HighLevel is a separate subscription, so check its current plans for workflow and webhook access. An agency pays for each separately, and usually passes the HighLevel cost through to the client.
Key takeaways
- A HighLevel loyalty integration uses workflow webhooks and the MSTRMND API on the Business plan.
- No HighLevel app is published, so the workflows are built and maintained by someone.
- Trigger on attended appointments and paid invoices, not on bookings.
- Save a working workflow as a template to speed up each later client.
- Guard against double rewards with a lookup or a tag.