From incoming enquiry
to a clear next step.
01 / The brief
An inbound request needs more than a place in the CRM. It needs context, a destination and a visible next step.
I built an n8n workflow to validate and qualify incoming leads, route requests by intent and urgency, update HubSpot and bring the right context into Slack.
02 / Follow the flow
Explore the four stages, from initial validation to the team handoff.
The workflow receives the enquiry, normalizes its fields and checks that essential contact information is available before continuing.
An incomplete request has a review path instead of an automatic CRM write.
AI qualifies the enquiry by intent, urgency and priority. Routing rules turn that context into a destination for the appropriate team.
AI classification and routing rules work together in the handoff.
HubSpot receives the contact information and qualification context so the team can pick up the request with a useful record.
Duplicate checks support review; they do not automatically merge contacts.
Slack alerts bring the enquiry context to the team. A follow-up check flags records that still need an owner, with error alerts for issues that need attention.
The follow-up checks assignment, not whether a customer has received a reply.
This is a simplified overview. Client details and internal configuration are omitted.
03 / The safeguards
The handoff also needs a plan for incomplete data, possible duplicates and exceptions.
Requests with missing contact details move to review rather than creating incomplete CRM records.
Contact lookups and possible-duplicate flags help the team review existing records.
Logging, error alerts and assignment checks make follow-up part of the workflow.
Workflow documentation supports testing, maintenance and future changes.
Built by Artur Gurunyan / ArtoBuilds