Lead Routing and Enrichment
Enrich new Typeform submissions with Clearbit firmographics, score them, and route each lead to the right Salesforce owner within minutes.
The problem
Leads that sit unassigned go cold, and reps waste time researching companies by hand. Manual routing rules live in spreadsheets that drift out of date, and duplicate leads clutter the CRM. By the time the right rep gets the lead, the prospect has moved on.
How it runs on Neblex
A webhook from Typeform starts the flow the moment a form is submitted, or you can use a Neblex hosted form as the intake itself. The flow calls Clearbit to enrich the submission with firmographic data such as company size, industry, and location. Transforms normalize the values so downstream scoring works on clean data.
Dedup matching rules check Salesforce for an existing lead or contact before anything is created. Conditional branching scores the lead, and a built-in Data Table holds the territory and routing rules so RevOps can update assignments without editing the flow. The lead is created or updated in Salesforce with the right owner already set.
Per-step retries cover transient API errors, and if enrichment fails the flow branches to a fallback path instead of dropping the lead. Event-sourced run history shows exactly what happened to every submission.
Step by step
Capture the submission
A Typeform webhook fires on submit, or a Neblex hosted form collects the lead directly.
Enrich the lead
Clearbit adds firmographics, and transforms normalize company names, sizes, and industries.
Check for duplicates
Matching rules search Salesforce so an existing account gets an update, not a second record.
Score and route
Conditional branching applies the scoring model, and a Data Table lookup resolves territory and ownership.
Create the lead
The flow writes the enriched, scored lead to Salesforce with the owner assigned.
Platform capabilities used
- Webhook triggers
- Hosted forms
- Dedup via matching rules
- Conditional branching
- Data Tables for routing rules
- Per-step retries
Common questions
What happens when enrichment finds no match?
Conditional branching handles the miss: the lead still routes on the data you have, and the flow can flag it for manual review in the task inbox. Nothing is silently dropped, and the run history records the path each lead took.
How do we change routing rules without touching the flow?
Territory and assignment rules live in a built-in Data Table. RevOps edits the table, and the next run applies the new rules.
Can we start from a form Neblex hosts?
Yes. Neblex includes hosted forms that start or feed flows directly, so you can run intake without a third-party form tool. Typeform stays fully supported as a trigger if you prefer it.
Related use cases
Campaign-to-Pipeline Attribution
Sync Google Ads spend and HubSpot campaign engagement into BigQuery on a schedule so marketing and sales report from the same pipeline numbers.
Sales & RevOpsQuote-to-Cash Sync
Move closed-won opportunities from Salesforce through Neblex CPQ to NetSuite billing automatically, with no rekeying between systems.
AgenticSales Research Agent
An agent researches each new lead with a real browser, scores fit against your ICP, and drafts a personalized outreach sequence for rep review.
Want this running on your stack?
Neblex Integration Fabric is in beta: full platform, free while in beta. Bring this workflow and we will map it to your systems.