Understanding this example
Taylor at the fictional Northstar Studio submits an inquiry about customer support. The sample moves that context into a lead record and then prepares a team notification. The key design choice is to preserve the inquiry before relying on an email notification.
A business record and an automation run serve different purposes. The record describes the current lead and owner; a run describes an attempt to process an event. Keeping these separate makes it possible to recover a failed notification without losing the lead or creating another copy.
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.
Capture the inquiry
Website form: Sample lead: Taylor at Northstar Studio. Interested in customer support automation.
Create the record
CRM: A sample lead record is created with the selected service and requirement.
Notify the team
Team inbox: A sample notification provides context and a clear owner for the next step.
What to look for
- The inquiry includes a service and a specific requirement.
- The record retains that context for the next person.
- The notification gives ownership as well as announcing that an inquiry exists.
What happens when the request changes?
Test scenario: The same submission arrives twice while the team inbox is unavailable.
The receiving system should recognize the repeated submission, keep one lead and track the notification failure separately. A retry should recover the missing notification rather than create a second inquiry.
What this demonstration does and does not do
Taylor and Northstar Studio are fictional. This preview writes no CRM records, stores no visitor information and sends no notification.
Prepare for a connected version
A production workflow needs agreed access, ownership and recovery behavior. Bring these details to discovery:
- The destination CRM, field mapping and ownership rules.
- Stable submission identifiers and duplicate-handling behavior.
- A failure queue and a way for the team to recover missed notifications.
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.