Grow workflow
Lead Qualification Workflow: HubSpot and Salesforce Scoring
Inbound leads decay fast: the ones worth talking to book elsewhere while your team works through a flat queue of everything that filled out the form. This workflow puts a deterministic pipeline between the form and your calendar: every lead gets captured, enriched with what can be known from its email and company, scored by explicit rules, and routed. Hot leads get a booking link immediately; the rest get nurture or a polite pass, and your CRM stays accurate without anyone typing.
Typical timeline
2-4 weeks depending on how many capture points and CRM quirks are involved
Stack
n8n for the pipeline · Postgres for lead state · HubSpot or Salesforce for the score fields and routing · Cal.com for routing hot leads to a call · Resend for follow-up email · Slack for hot-lead alerts
What we need to start
- Your current capture points: forms, inbound email, or both
- A working definition of a good lead: who you actually close, in plain language we can turn into rules
- Admin access to HubSpot, Salesforce or the CRM you use, and a booking link (Cal.com or whatever you already use)
How it works
- 01
Capture everything into one pipe
Form submissions and inbound email land in a single n8n intake with a shared schema, so scoring logic runs once instead of per channel. Deduplication happens here: the same person filling the form twice is one lead, not two CRM records.
Tools: n8n, Webhooks, Postgres - 02
Enrich from real signals
We start with what the lead already gave you: the email domain. A company domain versus a free mailbox provider, a resolvable website, and a role-based address like info@ are all cheap, honest quality signals. Third-party enrichment APIs can layer on top, but the base tier works from data you already have.
- 03
Deterministic scoring
Scoring is explicit rules, not a model guessing: points for a business domain, for company signals matching your ICP, for message content that describes a real project. Deterministic means you can read the score breakdown for any lead and know exactly why it landed where it did, and tuning is editing rules rather than retraining anything.
Tools: n8n, Postgres - 04
Route by score
Hot leads trigger a Slack alert and an immediate email with a booking link while intent is fresh. Mid-tier leads get a short nurture sequence; low scores get logged and left alone. The routing thresholds are yours to move as you watch what each tier actually converts into.
Tools: Slack, Cal.com, Resend - 05
Write the score into HubSpot
In HubSpot, the score and its breakdown live in contact properties the pipeline writes, and HubSpot workflows act on them: set the lifecycle stage, rotate the lead to an owner, create a follow-up task. If you already use HubSpot's own score properties, we feed them the same rules instead of running a second score next to them, so reps see one number.
Tools: HubSpot, n8n - 06
Or write it into Salesforce
In Salesforce, the score and breakdown are custom fields on the Lead, written by the pipeline through the API. Lead assignment rules or a record-triggered Flow route on the score, and a high score creates a task for the owner. Conversion to Contact and Opportunity stays a rep decision.
Tools: Salesforce, n8n - 07
Review loop
Because every score and breakdown sits in the CRM, the pipeline is inspectable rather than a black box. We schedule a review after the first few weeks of real traffic to compare scores against what sales actually experienced and adjust the rules.
Tools: n8n
You get
- The live capture-enrich-score-route pipeline in n8n
- A documented scoring rubric your team can read and edit
- Score and score-breakdown fields in HubSpot or Salesforce, with routing on top
- Slack hot-lead alerts and the booking-link email flow
When to choose another approach
- ·You get a handful of leads a month; read them yourself, the context in your head beats any rubric at that volume
- ·You cannot describe what a good lead looks like yet; the rules would encode guesses, close a dozen deals first
- ·Your sales process changes weekly; stabilize who you sell to before automating who you talk to
Open resources
Frequently asked
Why deterministic scoring instead of AI scoring?
Because you can debug it. When a rule-based score looks wrong, you read the breakdown and edit a rule; when a model score looks wrong, you shrug. AI earns a place for specific judgments, like reading intent in the message body, but the backbone stays rules you own.
What can you really tell from an email address?
More than you would expect: whether the domain belongs to a company or a free mailbox provider, whether that domain resolves to a real website, and whether the address is personal or a role account. None of it is certain on its own, but combined these signals separate serious inquiries from noise reliably enough to route on.
Will good leads get filtered out by mistake?
Some misses are inevitable, which is why nothing is deleted: low scores are logged with their breakdown, not discarded, and a human can skim that tier in minutes. The review loop exists to catch systematic misses and fix the rule that caused them.
Should we use HubSpot or Salesforce native lead scoring instead?
Use it if it already works for you. The native tools are good at scoring on fields and activity inside the CRM. This workflow adds what they do not see: enrichment from outside the CRM, deduplication before the record is created, and a breakdown your team can read. Where native scoring exists, we feed it rather than compete with it.
Does this work with our existing CRM?
Almost certainly. n8n has native nodes for the major CRMs and can hit any REST API for the rest. The sync writes leads, scores, and breakdowns into fields your team already looks at, rather than adding another tool to check.
FROM A PATTERN TO YOUR SYSTEM
Want this working in your business?
Bring your tools, data, and operating requirements. ManasFlow can help you scope the implementation around the way your business works.