Quick answer
Boomerangme documents card-specific workflow triggers: points-count events for cashback, reward and gift cards, and reward-count events for stamp cards. A merchant should test the exact card and event before enabling a live chain.
Read the compatibility note as a design constraint
The workflow-builder page says not all triggers work with every card type. It identifies points-count and reward-count examples and describes a reward-card bonus-balance filter. This is current documentation checked October 23, 2026, not evidence of a new release date.
Start with the customer event, then select a supported trigger. Do not design a campaign copy first and assume the software can detect it later. A “third visit” journey requires a reliable visit or reward event on the selected card, not merely a customer opening a message.
Give branches an exit and frequency rule
An automation can send repeated messages if the same condition remains true or a record re-enters the chain. Define the one-time condition, cooldown, stop event and exclusion. Birthday and feedback journeys also need correct dates, consent and a sensible delay.
For SMS or email actions, the documentation notes that mailing services must be connected. That is a dependency, not a guarantee of delivery. Test sender configuration, consent, unsubscribe behavior and failed-address handling in the connected service.
Use test customers and readable names
Name workflows by card, trigger, audience and purpose. Keep them in draft while testing. Use one staff customer that should qualify and one that should not; record each trigger time, branch and message.
If a workflow adds value to a card, reconcile the resulting transaction and restrict who can edit the chain. Turn off old experiments so later staff do not confuse draft logic with production.
A practical pilot
Build the smallest useful chain: one supported trigger, one filter, one message and one exit. Test duplicate events, missing contact permission, existing customer, wrong card type and manual balance correction before switching to working mode.
Use a staff test account first. Save the transaction or booking reference, the rule applied, the resulting customer balance and the person who made any correction. Review edge cases before inviting the public. A loyalty card is the customer-facing record of an offer; it does not replace the booking, payment, inventory or accounting system that proves what happened.
Boomerangme documents digital stamp cards and reward cards. You can explore Boomerangme to compare those mechanics with this workflow. This independent journal does not imply a native integration with the businesses or systems cited here. Verify the current settings in your own account and keep the primary operational record in the system that owns it.
What to record and review
For “Boomerangme Workflow Builder: Check Card Triggers Before Automation,” keep a compact decision log beside the operating system that proves the transaction. Record the customer-facing rule version, qualifying reference, date, location or channel, value added or removed, staff user and exception reason. Do not copy sensitive operational notes into a public-facing wallet pass. Review a small sample weekly during the pilot: one ordinary earning event, one redemption, one correction and one case that did not qualify. Compare the saved record with what the customer can see. This is especially important for the trends workflow described here, because a card balance alone cannot explain a booking state, refund, product exclusion or staff override. If the same exception appears twice, improve the written rule or checkout process instead of relying on memory.
Quick questions
Do all workflow triggers work with every card type?
No. The current documentation lists card-specific trigger compatibility, so verify the chosen card and event.
Does connecting an email action guarantee delivery?
No. The mailing service, address quality, consent and recipient settings still affect delivery.
Should I start with a long branching chain?
Start with one tested trigger and outcome. Add branches only after the event and stop conditions are reliable.
Sources & further reading
- How to create automationPrimary documentation for workflow triggers, card types and filters; checked October 23, 2026.
- Push automationPrimary documentation for visit, feedback and birthday automations; checked October 23, 2026.
- Boomerangme reward card documentationPrimary product documentation checked October 23, 2026.
Sources reviewed .
Numerical examples are illustrative unless a cited source states otherwise.