Lead Enrichment and Routing

A signup sits in your database. It doesn't tell you which ones are worth a call.

Unmeshed enriches every signup with company and email data, scores it, and pings your team the moment a high-value lead comes in. Low-value signups get stored quietly. Nothing waits on someone checking a spreadsheet.

15-minute setupRuns on your existing stackFree tier available

Trusted by teams at leading organisations

American ExpressJPMorgan ChaseAtlassianUWMCoupangGE HealthCareDTDLT LogoClariAmerican ExpressJPMorgan ChaseAtlassianUWMCoupangGE HealthCareDTDLT LogoClari

What Changes

The lead still shows up. The question is whether anyone notices in time.

Before
Signups land in a database with no context
Someone manually checks each one against a company lookup tool
High-value leads sit unnoticed until someone happens to scroll through the list
Enrichment data lives in a spreadsheet, disconnected from the actual record
After
Every signup is enriched with company and email data automatically
A lead score decides what happens next, no manual lookup
High-value leads hit Slack the moment they sign up
Enrichment data writes back to the same record, for every signup, not just the ones someone got to

Capture

Validate and Save First

The workflow checks the email format and name before anything else, then writes the signup straight to your database. If an enrichment API is slow or down later, you still have the lead.

  • RULE

    Validate email format and required fields, before any external call

  • RULE

    Insert the signup immediately, enrichment happens after

  • RULE

    Extract the domain for the lookups that follow

Capture Path

Validate Signup

# validate_input

Insert Record

# db.insert

Extract Domain

# extract_domain

Parallel Enrichment Path

Domain Ready

fan out, non-blocking

Company Lookup

# company_lookup

Email Verification

# email_verify

Merge Signals

Enrichment

Company and Email Signals

Two lookups run after the insert, one for company context, one for email quality. Both are optional calls, so an outage on either side doesn't stop a signup from being captured.

  • RULE

    Look up the domain for company name and employee count

  • RULE

    Detect free or disposable email addresses

  • RULE

    Both calls are non-blocking, so an API outage doesn't drop the lead

Classification

One Rule Decides the Tier

A script combines both lookups into a single decision. Business email at a company over ten employees becomes high value. Free or disposable addresses become low value. No manual judgment call, same rule every time.

  • RULE

    Merge enrichment results into one lead tier

  • RULE

    Business domain plus company size above threshold, high value

  • RULE

    Free or disposable address, low value

Classification Path

Score Lead

# score_lead

High Value

business domain, 10+ employees

Low Value

free or disposable address

Routing Path

Slack Alert

high value, full context

Exit Quietly

low value, no notification

Update record

every signup, high or low

Routing

Notify, Then Record Everything

High-value leads post straight to Slack with the context your team needs to follow up. Every signup, high or low value, gets its enrichment data written back to the same record.

  • RULE

    High-value leads post to Slack with name, email, company, and a follow-up note

  • RULE

    Low-value leads exit quietly, no notification

  • RULE

    Every signup gets its enrichment fields updated, whether or not Slack fired

What This Template Actually Does

Business email at a company over ten employees. That's the entire rule. No manual lookup, no spreadsheet, no missed lead.

15 min

Typical setup time

2

Lookups: company + email verification, both non-blocking

100%

Of signups get enrichment data written back, high or low value

Connects to Your Stack

Built on the tools this template uses, with room to route notifications wherever your team lives.

Postgres / SupabaseHunter.ioKickboxSlackMS TeamsOutlookGmailGoogle Sheets+100 more

Inside the Workflow

Four pieces, one workflow.

Non-blocking enrichment

API calls that can fail without losing the lead. The signup is saved before any external call runs.

One rule, every time

The same lead-scoring logic runs on every signup. Nothing depends on someone remembering to check.

Selective notification

Only high-value leads interrupt your team. Low-value signups still get recorded, just quietly.

Full enrichment record

Company, email quality, and lead tier written back to every signup, not just the ones flagged.

Why This Holds Up

Built for reliability, not a compliance checklist.

Fails safe

If an enrichment API times out, the signup is already saved. Nothing is lost waiting on a third-party call.

Your data, your database

Enrichment writes back to the same record in your own Postgres or Supabase instance, not a separate vendor silo.

No black-box scoring

The lead-scoring rule is plain logic you can read and edit, not a hidden model.

Try it before you commit

Free tier available, no credit card required to see it running.

Frequently asked questions

Still have questions? Talk to us.

Know which signups are worth a call, automatically.

Connect your database, Hunter.io, and Slack, and this runs on every signup starting today.

Free tier, no credit card required