Pabbly Connect Loyalty Automation: Workflows That Update a Wallet Card
Pabbly Connect loyalty automation uses workflows to turn events in your other tools into stamps, points or cashback on a MSTRMND wallet card. It runs through webhooks and the API on the Business plan. This page covers the recipes, the setup and the limits.
Via API and webhooks, Business plan
Build your first workflow
- Choose the trigger
- Look up the customer
- Call the card API
- Build the refund path
Test with a real card.
What does Pabbly Connect loyalty automation do?
It connects an event in one of your tools to an action on a customer’s loyalty card. Pabbly Connect organises this as a workflow: a trigger, then one or more actions. For MSTRMND, the actions are calls to the API, which the Business plan includes along with webhooks.
Owners who already use Pabbly Connect for other jobs, such as moving form entries into a spreadsheet or a CRM, can add the card to the same place. The tool is familiar, the logins are in one account and the loyalty rule sits beside the rest of the business’s automation. New to wallet cards? Start with our guide to digital loyalty cards.
How a workflow talks to the card
A workflow reaches MSTRMND by calling the API, using a webhook or an API step. The card actions it can use are the same as any other route:
- Create a customer and issue a card, then send the card link by message.
- Add or subtract a stamp, point, visit, purchase or transaction amount.
- Send a push or an SMS to a customer.
- Look up a customer to avoid creating a duplicate.
The workflow’s own steps format the data, filter out records you do not want to reward and handle delays between steps.
Three Pabbly Connect workflows and the card actions they use
Each workflow pairs a trigger in another tool with a call to the MSTRMND API.
| Workflow | Trigger | Card action | Reverse it with |
|---|---|---|---|
| Sign-up to card | New form or shop sign-up | Look up, create customer, issue card, send message | Edit or delete the card |
| Payment to reward | Payment received | Add purchase, stamp or visit | Subtract the same |
| Birthday message | Scheduled check | Send push | Not applicable |
Workflows worth building first
Sign-up to wallet card
A form entry, a landing page or a shop sign-up becomes a customer and a card. The workflow sends the card link, so the customer can add it to their wallet at once. The key detail is checking for an existing customer first, so one person does not get two cards.
Payment to reward
A payment notification from your payment tool or booking system adds a purchase, a stamp or a visit. Add a second workflow for refunds that uses the matching subtract action.
Birthday or milestone message
A scheduled workflow looks for customers with a birthday this week and sends a push message with a small treat. It costs little and customers tend to remember being thought of.
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 Pabbly Connect account. Check its current plans and limits, 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 Pabbly Connect stops
Like any workflow tool, it works best on single events with a clear rule. Complex branching and very large batches are harder to maintain than in a tool built for them, or in a developer’s code. It is also a separate subscription with its own limits, and it is only as reliable as the data it receives. Test every workflow with a real card, including the refund path, before you launch.
A first-week plan for Pabbly Connect loyalty automation
Start small and prove one workflow before you build a second.
- Day one: write the reward rule in plain words, including what happens on a refund.
- Day two: collect your MSTRMND API credentials and decide how you will match customers, by email or phone.
- Day three: build the sign-up workflow, with a lookup step before the create step.
- Day four: build the payment workflow and its refund twin.
- Day five: test with your own card and one friendly customer, then switch the workflows on.
Resist the urge to build the birthday message in week one. A programme that rewards correctly and is simple is worth more than one that does ten things unevenly.
Test before you launch
A workflow is only as good as the data it receives, so test the awkward cases, not only the happy path.
- A customer with no email address or a phone number in an unusual format.
- The same customer arriving twice in a minute.
- A refund that arrives after the original reward.
- A payment for zero or a very small amount.
- A failed call to the card API, and whether you are told.
Pabbly Connect loyalty automation works well when these are settled in advance. Decide each rule once, write it down and build it in.
Frequently asked questions
Does MSTRMND have a Pabbly Connect app?
The published connection is through API and webhooks on the Business plan, which a Pabbly Connect workflow can call with a webhook or API step. If you want something more specific, ask on a call. Plan on the API route, because that is what is documented, and it covers the common rules.
What does it cost?
MSTRMND’s side is the Business plan, £115 a month billed annually, which includes API and webhooks. Pabbly Connect is a separate subscription with its own plans and limits, so check them against the volume you expect. The two together replace a build that would otherwise need a developer.
Can I stop duplicate cards?
Yes. Add a lookup step before the create step, so the workflow finds an existing customer by email or phone first and only creates one if none exists. This is the most common source of mess in a new setup, and it takes one extra step to prevent.
Can a workflow reverse a reward?
Yes. Each add action has a matching subtract, so a workflow triggered by a refund can take a stamp, points or cashback back. Build the refund workflow at the same time as the forward one, and test both before you tell customers about the programme.
Key takeaways
- Pabbly Connect loyalty automation drives the wallet card through the API and webhooks on the Business plan.
- Look up the customer before you create one, so nobody gets two cards.
- Every add action has a matching subtract, so build the refund workflow too.
- Workflows suit single events with a clear rule, not large or complex batches.
- Pabbly Connect is a separate subscription. Check its current plans.