Understanding this example
The fictional Northstar Studio wants customer support automation. Qualification adds relevant requirements and timing before a discovery task is assigned. The purpose is to prepare a useful conversation, rather than collect every possible detail about a visitor.
Decide which questions affect the next action. Asking about the current support tool may establish integration fit; requesting confidential customer records at this stage does not. Keep optional information optional, and make the receiving person responsible for reviewing the requirement.
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 requirement
Sample inquiry: Fictional lead: Northstar Studio is interested in customer support automation.
Qualify the context
Qualification: Sample requirements and timing help identify the service fit and next owner.
Route to discovery
Team handoff: The sample lead receives a discovery task with their requirement attached.
What to look for
- The captured requirement names a business problem.
- Qualification adds context that can change routing or scope.
- The next owner receives a discovery task with the requirement attached.
What happens when the request changes?
Test scenario: The visitor is unsure which service they need and leaves an optional field blank.
The flow should allow a general discovery request instead of inventing missing details or rejecting a useful inquiry. Required fields should reflect what the team actually needs to respond.
What this demonstration does and does not do
This example collects no real leads and writes no CRM data. It does not search for prospects or send outreach.
Prepare for a connected version
A production workflow needs agreed access, ownership and recovery behavior. Bring these details to discovery:
- The few required fields and the reason each is needed.
- Routing rules, an owner and a response process.
- Consent preferences, duplicate checks and retention responsibilities.
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.