Lead Scoring Automation

A contact crosses your engagement threshold. Sales shouldn't find out a week later.

Unmeshed automates lead scoring and routing end-to-end. When a contact's engagement score crosses your threshold, it checks they're not already qualified elsewhere, creates the Salesforce lead with the right rating, and notifies your sales team, all without a form fill triggering it.

Map My Workflow
10-minute setupBuilt-in dedup checkFree tier available

Trusted by teams at leading organisations

American ExpressJPMorgan ChaseAtlassianUWMCoupangGE HealthCareDTDLT LogoClariAmerican ExpressJPMorgan ChaseAtlassianUWMCoupangGE HealthCareDTDLT LogoClari

What Changes

The behavior already happened. The question is whether sales ever sees it.

Before
Engagement scoring lives in one system, Salesforce lives in another, nobody's watching the gap
Contacts who never filled out a form can cross every buying signal and still have no lead record
Duplicate leads pile up when two systems both try to qualify the same contact
A dropped API call means a lead silently never gets created
After
The moment a score crosses threshold, lead scoring automation creates the lead automatically, no form required
A tag check runs first, so contacts already qualified through another path don't get duplicated
Rating is calculated from the actual score, Hot or Warm, not guessed
A retry policy on the Salesforce call means a transient failure doesn't mean a lost lead

Intake

Load the Contact Fast

The workflow pulls contact details straight from the trigger payload; no separate lookup needed. Everything downstream, the score check, the tag check, the lead payload, works off this one input.

  • RULE

    Pull contact ID, name, email, company, score, and tags from the trigger

  • RULE

    No extra lookup call before the first gate

  • RULE

    This input feeds every step that follows

Intake Path

Engagement Trigger

# trigger.payload

Contact From Payload

contact IDnameemailcompanyscoretags

Score gate

same input

Tag gate

same input

Lead payload

same input

Gating Path

Score Gate

# score >= threshold

Exit

below threshold

Tag Gate

# has_qualified_tag

Exit

already qualified

Proceed to Create

both gates passed

Gating

Two Checks Before Anything Gets Created

Score is checked first because it's the fastest filter, an in-memory comparison, no external call. Only contacts above threshold reach the second gate, which checks whether they're already qualified through another path.

  • RULE

    Exit immediately if the score is below threshold

  • RULE

    Check for an existing qualified tag before creating anything

  • RULE

    Both gates run before any Salesforce call, so nothing is wasted on a contact that won't qualify

Lead Creation

Rating Calculated Then Posted

A script maps the engagement score to a Salesforce rating, Hot for 90 and above, Warm for 75 to 89, and assembles the full lead payload. The Salesforce call carries a retry policy, since transient API failures are common enough to cost you real leads over time.

  • RULE

    Map score to rating, Hot or Warm, no manual judgment

  • RULE

    Assemble the full lead object before the API call

  • RULE

    Retry policy on the Salesforce post; a transient failure doesn't mean a lost lead

Creation Path

Map Score to Rating

# calculate_rating

Hot

score 90+

Warm

score 75 to 89

Assemble Lead Payload

# build_lead

Create Salesforce Lead

# salesforce.create_leadretry policy

Notification Path

Salesforce Confirms

# create_lead.response

Read Lead ID

# lead.id

Post to Sales Channel

# slack.post_messageoptional

a failure here leaves the lead in place

Notification

Sales Gets the Lead ID Immediately

Once Salesforce confirms the lead, the new Lead ID gets pulled from the response and posted to your sales channel. This step is optional, so a Slack hiccup never undoes a lead that already got created.

  • RULE

    Read the new Lead ID from the Salesforce response

  • RULE

    Post to the sales channel with the lead details

  • RULE

    Slack is optional; a notification failure doesn't roll back the lead

What This Template Actually Does

Score checked first because it's the fastest filter. Only contacts who clear both gates ever reach Salesforce.

10 min

Typical setup time

2 gates

Score threshold and dedup tag check

3x retry

On the Salesforce call, so a transient failure doesn't cost a lead

Connects to Your Stack

Runs on the tools you're probably already using.

SalesforceSlackMS TeamsGmailOutlookGoogle SheetsAirtableMailchimpSendGridTwilioPostgres / Supabase+100 more

Inside the Workflow

Four pieces, one workflow.

Fast first gating

The cheapest check runs first, so nothing is wasted on a contact that won't qualify.

Built-in dedup

A tag check catches contacts already qualified through another path before a duplicate lead gets created.

Automatic rating

Hot or Warm is calculated from the score every time, no manual judgment call.

Resilient delivery

A retry policy on the Salesforce call, and an optional Slack step that can't undo a lead that already exists.

Why It Holds Up in Production

Built to survive a flaky API and a duplicate signal.

Ordered gates

Score checked before tags, tags checked before creation, nothing wasted on a contact that exits early.

Retry on the write

Transient Salesforce failures don't silently drop a lead.

Token handling flagged

The setup notes call out that access tokens expire and need a refresh step in production, not left as a surprise.

Full run history

Every gate a contact passed or failed is logged and readable after the fact.

Frequently asked questions

Still have questions? Talk to us.

Let behavior create the lead, not a missed form.

Connect Salesforce and Slack, and this runs on every contact that crosses your engagement threshold.

Map My Workflow

Free tier, no credit card required