The first week shapes whether they stay.
Onboarding sequences that fire on day 3 — not day 1 — respect the customer's pace. This demo shows the engaged, stalled and off branches.
What triggers this workflow
First successful purchase / subscription event triggers the onboarding sequence.
Source: Order or subscription event
Workflow steps
- Listmonk + n8nWelcomeWelcome email with the basics — links, contacts, what to expect.
- Twenty CRM + n8nDay 3 triggerDay-3 behaviour check — engaged / stalled / off.
- n8nBranchEngaged → tip; stalled → personal check-in; off → feedback ask.
- Chatwoot + Twenty CRMDay 14If still no engagement, surface a cancellation offer to the team.
Tools used
Human handoff
Day 7 and Day 14 are always a person
The automated branches handle days 1–3. Anything past day 7 is handled by a CX team member with the customer history attached.
- Customer still stalled at day 7
- Customer asks for help with onboarding
- Customer reports a problem with the first order
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. Welcome sequence begins
Subject: Welcome to Salt & Sand, Hannah! Hi Hannah, Welcome aboard — your monthly cafe subscription kicks off this week. Here's a quick rundown: • How your subscription works (link) • How to update your preferences (link) • Who to contact if anything's off (link) Take your time — none of this needs to happen today. — Salt & Sand, Noosa
2. Branch by day-3 behaviour
Hi Hannah, glad you're getting the hang of the monthly cafe subscription. Quick tip: you can swap your usual order anytime in the app — it's under 'preferences'. — Salt & Sand
Sample data only. Numbers, names and messages are placeholders for illustration. Wire the live workflow separately using the setup notes below.
Setup for production
Wiring it for production
Live deployment needs the activation event and consent flags.
- Wire the activation event in Twenty CRM.
- Set the day-3 trigger in the n8n workflow.
- Document the cancellation-offer wording for the day-14 branch.
- Configure CX team alerts for stalled and off customers.
Production prerequisites
- Activation event source reliable
- Consent flag maintained in Twenty CRM
- CX team named as the day-7+ hand-off owner
Nothing here runs by default. Configuration has to be in place before any live send, booking or contact write.
Questions
When does the workflow stop being useful?
After the day-14 hand-off the sequence ends. From there, a CX team member owns the relationship — not the workflow.
Does the welcome email go out without consent?
No. Welcome messages only go to customers who have explicitly opted in to receive them. Consent flags live in Twenty CRM.
More demos you can run in your browser
Want this customer onboarding 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.