Understanding this example
The sample begins with a website inquiry, shows a possible day-two reminder and ends when a booking stops the sequence. The useful part is the send decision: the workflow should recheck permission and the current conversation before every message.
A timed delay alone is not a follow-up strategy. The visitor may reply, book or opt out while the reminder is waiting. Keep those events on the same durable lead record so the next send can use current information rather than the state that existed when the inquiry arrived.
Read the complete sample sequence
Use Next step above to explore the preview, or read every stage below. Selecting a stage changes the explanation shown; it does not perform that action.
Day 0 · Inquiry
Acknowledgment: A sample lead receives an acknowledgment and a relevant discovery-call link.
Day 2 · Check in
Follow-up: A gentle reminder is sent only if follow-ups were requested and no reply or booking exists.
A booking stops the sequence
Stop condition: The sample lead books a meeting. Further follow-ups are canceled automatically.
What to look for
- The acknowledgment relates to an inquiry the visitor made.
- The reminder is conditional on the current preference, reply and booking state.
- A confirmed booking stops further inquiry reminders.
What happens when the request changes?
Test scenario: A visitor replies just before the reminder becomes due.
The sending workflow should read the latest record and skip the reminder when a reply has already stopped follow-ups. If a provider has already accepted a send, the team must handle that in-flight limitation rather than promising it can always be recalled.
What this demonstration does and does not do
No email is sent by this preview. The displayed days and outcomes are an example sequence, not a delivery log or a promised response schedule.
Prepare for a connected version
A production workflow needs agreed access, ownership and recovery behavior. Bring these details to discovery:
- A domain sending identity, an approved purpose and message content.
- Reply, booking and opt-out events linked to the same lead.
- Delivery identifiers, failure alerts and a process for uncertain send outcomes.
Continue with Plan an n8n lead workflow that stops when it should for a deeper planning checklist.
Published by FindSolution. These examples explain a design choice; they are not client case studies or evidence of a live integration. Read our editorial approach.