Problem
Follow-up becomes fragile when the workflow cannot remember what already happened.
A purchase can change status at different times. Without shared state, automations repeat actions or lose the next step.
Selected project · Hotmart Recovery Engine
A purchase changed state. The system knows what happens next.
A verified 22-node n8n workflow that evaluates eligible purchases every five minutes, prevents repeated sends, advances a three-stage recovery journey, and preserves an observable history.
Workflow22 n8n nodes
ScheduleEvery five minutes
RecoveryThree follow-up stages
SafetyDuplicate-send prevention
Solution
Receive the event, consult the journey, then act once.
The workflow reads the existing history before choosing a path, records the outcome, and exposes the updated state in the dashboard.
Portfolio demo
See the recovery workflow in 52 seconds.
The original demonstration shows the problem, workflow behavior, dashboard, and safety boundaries using fictional data.
Portfolio-safe demonstration — no real customer, purchase, or conversion data is shown.
Architecture
Receive. Decide. Persist. Observe.
The workflow keeps one clear responsibility at each boundary and leaves a durable record behind.
- 01Receive the status change
A webhook identifies the purchase and its new state.
- 02Read the current journey
The system checks what has already happened before choosing another action.
- 03Choose the next step
State-aware rules select the appropriate follow-up path.
- 04Persist the outcome
The action and next stage are stored as a durable execution history.
- 05Expose operations
A portfolio-safe dashboard makes journeys and executions visible.
Key engineering challenges
The automation has to remember before it acts.
Avoid duplicate follow-up
Existing execution history is checked before a new action can be considered.
Persist journey state
Each purchase keeps a known stage between independent workflow executions.
Handle changing status
The next step depends on the latest purchase state, not a fixed timer alone.
Keep execution observable
Operators can see what ran, where a journey stopped, and what comes next.
Test the workflow paths
Portfolio-safe scenarios exercise the automation without exposing customer data.
Avoid invented outcomes
The public project demonstrates behavior without claiming unsupported conversion or revenue results.
n8nSupabasePostgreSQLWebhooksState machineQA automation
Honest demonstration
The system behavior is visible without inventing business results.
The public demo uses fictional purchases to show journey state, workflow execution, and operational visibility.
No unsupported revenue or conversion claims are presented, and no real customer information appears.
Explore the project