Enrich form leads with waterfall enrichment
This play is built for teams that cannot afford missing data. When a lead submits a form, this n8n workflow initiates a sophisticated waterfall enrichment process. It starts with Lusha to get high-accuracy verified emails and direct dials. If Lusha doesn’t have a specific data point (i.e. a mobile number or a secondary email), the workflow automatically triggers a second request to a fallback provider via an HTTP node.
The data from both sources is merged into a single “golden record”, which is then pushed to HubSpot. This ensures that by the time your SDR gets the Slack alert, they have the most complete profile possible, regardless of which database the information came from.
Why this works
No single data provider has 100% coverage of every person on earth. Relying on just one source means your SDRs might hit a dead end with no phone number to call.
This play operationalizes coverage by:
- Maximizing ROI: Using your primary provider (Lusha) first and only spending credits on secondary providers when necessary.
- Redundancy: Ensuring that even hard to find prospects are enriched via a fallback logic.
- Merged intelligence: Combining the strengths of multiple databases into one HubSpot record.
- Instant response: Returning a complete JSON payload to your calling system so you can use the enriched data for real-time form routing.
What you get
- Webhook-triggered multi-source enrichment
- Waterfall logic that prioritizes Lusha for primary data
- Automated fallback to secondary APIs via HTTP
- Unified “golden record” upserted to HubSpot
- Complete SDR alerts in Slack with no missing contact fields
How to set it up
Install the Lusha community node
Ensure your n8n instance has the Lusha node ready to act as your primary “Tier 1” data source.
Connect your core apps
Link your credentials in n8n for:
- Lusha: Your primary enrichment engine.
- HubSpot: To store the merged “golden record.”
- Slack: To alert your sales team of the enriched lead.
Configure the waterfall logic
Set up the conditional node to check for missing values (i.e. if phone is null or if email is null). If a gap is detected, the workflow will proceed to the HTTP Request node.
Set up the fallback provider
Configure the HTTP Request node with the API endpoint, headers, and authentication keys for your secondary data provider. Map the input email from the original form submission to their search parameter.
Merge and map
Use a Merge node to combine the outputs. Ensure the mapping logic gives priority to Lusha data, only using the fallback data to fill in the blanks. Map this final object to your HubSpot contact properties.
Update your form action
Copy the n8n webhook URL and set it as the destination for your web form. The workflow will now process every lead in real time, returning the enriched JSON response to the browser or server.
What to do next
- Coverage reporting: Use n8n to log how often the fallback provider is triggered vs. Lusha to calculate the “Coverage Lift” of your waterfall.
- Dynamic routing: Use the merged “Industry” or “Seniority” fields to route the lead to a specific SDR team in Slack based on the best data available.
- Verification loop: Add a step to verify the fallback email via an email validation service before pushing it to HubSpot to maintain high deliverability.
The goal: Ensure that your SDRs always have a path forward, leveraging Lusha’s premium accuracy first and filling in the gaps with a smart fallback system.
No FAQ items available at this time.
Ready to build this?
Get started with Lusha and set up this play in minutes.
