Start with the buying process, not the nodes
Write down where a prospect comes from, what makes that prospect relevant, who may be contacted, what the first useful action is, and where the status must remain visible. This prevents a collection of disconnected automations from becoming an unmanageable sales system.
Separate sourcing from qualification
A sourcing workflow should gather and normalize records. Qualification should apply your documented fit and intent rules. Keeping these stages separate makes it easier to replace a data source without changing the sales logic.
For example, compare the Google Maps Lead Generator with the AI Lead Qualification workflow. One produces structured business records; the other decides how an incoming lead should be prioritized.
Define consent, suppression, and ownership
Document who can be contacted, which records must be excluded, how opt-outs are stored, and which system is the source of truth. Automation does not remove the need to follow applicable outreach and privacy rules.
Make every state visible
Your CRM or structured sheet should show sourced, verified, qualified, contacted, replied, booked, and suppressed states. Idempotent keys and explicit timestamps help avoid duplicate outreach when a workflow is retried.
Connect the system gradually
Test sourcing first, then qualification, then CRM writes, and only then outreach. The n8n Lead Generation Workflow shows how those stages can connect, but your fields and approval rules still need to be mapped.