← All Projects
Project 01 · Workflow EngineeringProduction Workflow

Inbound Qualification & Routing Engine

A production GTM system that captures, enriches, qualifies, routes, syncs, alerts, and reports on inbound leads automatically.

Capture → Enrich → Score → Route → Respond
Inbound Form / Webhook→Normalize Lead→Apollo Enrichment→ICP Scoring→Territory + Rep Assignment→CRM Update→Instant Sales Notification→Lead Response
n8nApolloCRMGmailGoogle SheetsJavaScriptREST APIs

Business Case

High-intent inbound leads can lose momentum when enrichment, qualification, routing, CRM updates, rep notifications, and reporting are handled across disconnected tools or manual processes.

The core business outcome: reduce the time between inbound conversion and sales action from minutes or hours to seconds.

The goal of this project was to design a single GTM system that could take a raw inbound lead and automatically turn it into enriched, qualified, routed, sales-ready, and reportable GTM data.

Problem

An inbound lead can require multiple operational steps before a sales rep can act on it: data normalization, company enrichment, ICP qualification, territory assignment, CRM synchronization, company resolution, rep notification, and reporting.

When these steps are disconnected, GTM teams can introduce slower handoffs, inconsistent qualification, routing errors, duplicate CRM records, and fragmented reporting.

Solution

I built an automated inbound GTM engine in n8n that orchestrates the lead lifecycle from capture through reporting.

The system normalizes inbound data, enriches company information through Apollo, calculates an ICP Fit Score, assigns the appropriate sales territory, triggers high-priority rep alerts, creates or updates CRM records, resolves companies by domain, and automatically feeds a management reporting layer.

Solution Architecture

Inbound Lead→Normalize→Apollo Enrichment→ICP Qualification→Territory Routing→Priority Check→CRM Sync→Reporting
Speed to Lead
Lead Submitted
10:32:04 AM
Lead Qualified
10:32:09 AM
+5s
Rep Assigned
10:32:10 AM
+1s
Sales Notified
10:32:12 AM
+2s
Total Routing Time
8 seconds

Calculated from workflow execution timestamps. Reduce the time between inbound conversion and sales action from minutes or hours to seconds.

Demo run · illustrative data

n8n serves as the orchestration layer connecting enrichment, qualification, routing, CRM operations, sales notifications, and reporting.

How I Built It

01

Capture & Normalize

Inbound webhook data is converted into a consistent lead structure for downstream processing.

02

Enrich

Apollo enriches company information including employee count, industry, domain, and company location.

03

Score & Qualify

Custom JavaScript calculates a 0 to 100 ICP Fit Score using company size, seniority, department, geography, and lead intent.

04

Route

Lead geography determines sales territory and assigned rep across Canada East, Canada West, US East, US Central, and US West.

05

Activate Sales

High-priority leads trigger an immediate rep notification while the workflow synchronizes lead and company data with CRM.

06

Report

Every processed lead is written into the reporting layer to provide management visibility into qualification, territory, ICP quality, and acquisition source.

System Outcomes

One workflow. Four operational outputs.

The inbound engine connects automation, CRM operations, sales activation, and management reporting in a single GTM system.

End-to-End Workflow

The production n8n workflow orchestrates lead capture, enrichment, qualification, routing, alerts, CRM synchronization, company resolution, and reporting.

Webhook→Normalize→Apollo→ICP Scoring→Territory Routing→Priority Check→CRM→Company Resolution→Reporting

n8n serves as the orchestration layer across the GTM stack. Click to enlarge.

Why This System Matters

Faster Operational Handoff

Lead processing moves through a predefined automated workflow rather than relying on separate manual GTM steps.

Consistent Qualification

Every inbound lead is evaluated against the same scoring framework, creating a standardized qualification process.

Structured CRM Data

Enrichment, qualification, routing, and company-resolution logic produce cleaner and more actionable CRM records.

Management Visibility

Reporting is generated as part of the workflow, giving GTM leadership visibility into lead quality, source, and territory.

Technical Decisions

Decision 01

Domain-Based Company Resolution

Companies are searched by domain before creation so the workflow can choose between update and create paths.

Decision 02

Submitted Geography Priority

Lead-submitted geography takes precedence where appropriate so company HQ data does not incorrectly determine territory.

Decision 03

Conditional Priority Alerts

Only high-priority leads trigger immediate sales notifications, preventing unnecessary rep alerts.

Decision 04

Reporting Built Into the Workflow

Reporting is captured as part of the automation rather than being treated as a separate manual process.

Tech Stack

n8n
Workflow orchestration
Apollo
Company enrichment
CRM
Contact and company sync
Gmail
Priority notifications
Google Sheets
Reporting data layer
JavaScript
Scoring and routing logic
REST APIs
System integrations
Webhooks
Inbound capture

Skills Demonstrated

GTM Systems ArchitectureWorkflow AutomationAPI IntegrationCRM AutomationLead EnrichmentICP ScoringLead QualificationTerritory RoutingRevenue OperationsData NormalizationConditional LogicJavaScriptReporting AutomationCRM Data ManagementSpeed-to-Lead Optimization
Project 01

Inbound Qualification & Routing Engine

Designed and built as an end-to-end GTM engineering project demonstrating workflow orchestration, enrichment, custom qualification logic, territory routing, CRM automation, real-time sales alerts, and management reporting.

n8n · Apollo · CRM · JavaScript · REST APIs · Gmail · Google Sheets