A loyalty program is a relationship, not a discount.
Enrol, reward a first redemption and re-engage dormant members with consent. This demo shows the four branches — enrolment, first redemption, dormant and reward notification.
What triggers this workflow
First purchase, dormancy threshold, or reward threshold fires the workflow.
Source: Order event + cadence
Workflow steps
- Twenty CRM + n8nDetect eventFirst purchase / dormancy / reward — different branches.
- Listmonk + Twenty CRMEnrol / messageEnrol customer with a unique member ID; first-redemption bonus ready.
- Listmonk + TwilioRe-engageDormant branch sends a low-pressure re-engagement (no pushy discounts).
- Listmonk + TwilioNotifyReward branch notifies the customer with redemption details.
Tools used
Human handoff
The program is opt-in and consent-driven
Every message respects the customer's marketing consent. STOP keywords and unsubscribe links remove the contact from the program without losing the membership.
- Customer asks to be removed from marketing
- Member requests a points audit
- Member reports a billing or balance error
Try it in your browser
Edit the sample inputs, choose a branch, and see what the workflow produces. The sandbox runs offline — no accounts touched, no messages sent.
Try it in your browser
Edit the inputs, pick a branch, and see what the workflow produces. Runs entirely in your browser — no messages are sent, no accounts are touched.
1. Member already enrolled
Hannah is enrolled in Maple Avenue Rewards (member M-78514). Branch: first-redemption.
2. Branch by engagement
Hi Hannah, your Maple Avenue Rewards bonus (200 pts) is loaded — tap to redeem at your next fill: mapleave.example/r/abc. — Maple Avenue Pharmacy
Sample data only. Numbers, names and messages are placeholders for illustration. Wire the live workflow separately using the setup notes below.
n8n workflow template
n8n template — LGM 07 Customer Event Recipe (SIMULATED, inactive). Ships with active: false — no live integrations are wired. See the setup section below for the wiring checklist, and download the JSON to inspect or import it.
Setup for production
Wiring it for production
Live deployment needs the order source, consent flags and a clear program policy.
- Connect the order source so first-purchase detection works.
- Define the dormancy window (default 90 days) and the reward threshold.
- Add a STOP / unsubscribe handler so customers can opt out of marketing while staying members.
- Document the program policy in plain English and link it from the enrolment email.
Production prerequisites
- Order source with reliable first-purchase detection
- Consent flag maintained in Twenty CRM
- Reward threshold and dormancy window signed off
Nothing here runs by default. Configuration has to be in place before any live send, booking or contact write.
Questions
Can a customer opt out of marketing and still be a member?
Yes. STOP / unsubscribe removes the customer from marketing messages but leaves the membership intact — the points balance and the member ID stay active.
What about spam concerns?
The dormant branch runs on a quarterly cadence with low-pressure copy. If the customer opts out, the cadence stops without further prompts.
More demos you can run in your browser
Want this loyalty enrolment & re-engagement workflow running on your stack?
Pick the demo you're curious about or describe your own. We'll come back with what a real deployment looks like for your business — the workflow, the prerequisites, the people involved.