Score fit, intent and timing in separate columns, add them in a formula column to a 0 to 100 total, convert the total to a tier (A, B, C), then write score, tier, reasons and a timestamp into custom HubSpot contact properties with Clay's "Look up object" and "Update object" or "Create object" actions. Routing lives in HubSpot workflows triggered on the tier property, not in Clay. Keep Clay's score out of HubSpot's own HubSpot Score property.
Below: the scoring model, the formula column, field mappings into HubSpot. Clay's action list and formula behavior were read on Clay University in November 2026.
Want this built and maintained for you? See our certified Clay build service.
Most "Clay lead scoring" content stops at the idea: enrich, score, done. The hard part is the plumbing: which columns feed the score, how the formula handles blanks, what the HubSpot properties are called, and how a rep gets a task within minutes. This is the template we would build for a GTM engineer or RevOps lead who owns both Clay and HubSpot.
It is not a HubSpot-native scoring guide; that lives in our HubSpot lead scoring setup post. Here Clay computes the score because Clay holds the enrichment data (headcount, tech stack, hiring, funding, website visits) and HubSpot only receives the result. The thinking behind what to score is in our data-driven lead scoring post. Checked November 2026 against Clay University's HubSpot integration overview. Clay renames actions (the older "Create or Update Contact" is now separate create and update actions, according to Clay community replies), so check the names in your workspace first.
The scoring model: fit, intent, timing
Use three sub-scores in separate columns. One blended number hides why a lead scored high, and reps stop trusting it within a month.
| Sub-score | Question it answers | Max points (template) | Typical inputs |
|---|---|---|---|
| Fit | Could they buy at all? | 50 | Headcount band, industry, HQ country, seniority, must-have tech (for example HubSpot in stack) |
| Intent | Are they showing interest in this problem? | 30 | Identified website visit, prior reply or meeting, engagement with your LinkedIn content |
| Timing | Why now? | 20 | Open role for the function you sell to, funding in the last 90 days, new executive under 6 months in seat |
The weights are a starting point, not a finding. Fit is the biggest block because a perfect-timing lead at a company that can never buy is still a waste; timing is the smallest because those signals expire fastest. Revisit after 60 days of booked meetings: if most came from B leads, the weights are wrong, not the reps.
The Clay table: columns and enrichments
Build on a people table (one row per contact) with a company lookup; HubSpot routes on contacts, so the score belongs on the person. A minimal column set:
- Identity: Name, Job Title, Work Email, Company Domain.
- Fit inputs: Employee Count, Industry, HQ Country, Technologies (tech-stack enrichment), Seniority derived from the title.
- Intent inputs: Website Visitor Match (true/false), Prior Engagement pulled from HubSpot with Look up object (last reply or meeting date), LinkedIn Engagement (true/false).
- Timing inputs: Open Roles Count (filtered to the function you sell to), Last Funding Date, Executive Start Date.
- Score columns: Fit Score, Intent Score, Timing Score, Total Score, Tier, Score Reasons, Scored At.
- HubSpot columns: HubSpot Contact ID (from Look up object), Push Result.
Use waterfalls for headcount and tech stack, because a blank there silently zeroes a sub-score (see our Clay waterfall enrichment guide). Have every formula treat a blank as zero and append "missing: headcount" to Score Reasons.
The formula column (template)
Clay's formula column takes a JavaScript expression over other columns in the row. Most teams write it with the AI formula generator: type the rule in plain language, insert column references with "/", click Generate Formula, review the sample output, save. Clay University's formula generator page describes this flow.
Fit Score in words: add 20 if Employee Count is between 50 and 500, 15 if Industry is a target industry, 10 if HQ Country is a target country, 5 if Job Title contains a seniority word (VP, Head, Director, Chief). Cap at 50.
Example only (verify in your workspace with the formula generator; column names and exact reference syntax must match your table):
Fit Score = ( >= 50 && <= 500 ? 20 : 0 ) + ( ["Software","IT Services","Financial Services"].includes() ? 15 : 0 ) + ( ["United States","Netherlands","Germany","United Kingdom"].includes() ? 10 : 0 ) + ( /\b(vp|head|director|chief)\b/i.test( || "") ? 5 : 0 ) Total Score = + + Tier = >= 70 ? "A" : ( >= 45 ? "B" : "C")
Three rules: one sub-score per column, because a 40-line formula cannot be reviewed; coerce types, because the text "250" compares differently from the number 250; build Score Reasons from the same conditions ("headcount 50-500; HubSpot in stack; SDR role open") and push it too, because reps read reasons, not numbers. Intent and Timing follow the same pattern (15 for a recent website visit, 10 for a prior reply or meeting, 5 for LinkedIn engagement; 10 for an open role, 6 for recent funding, 4 for a new executive). Test date math on five rows with known dates first.
Thresholds and tiers
Three tiers: A at 70 and above, B from 45 to 69, C below 45. A gets a human within minutes, B gets a sequence, C gets a nurture list. Keep the tier as a text column with exactly the values your HubSpot dropdown accepts; a mismatch fails the push for that row. Set thresholds from capacity, not from the score distribution: if two reps can each take six new conversations a day, the A threshold is whatever produces about twelve A leads a day. A tier that produces more than reps can touch within an hour is a C tier with a nicer label. Our lead routing and speed to lead post covers the response-time side.
Field mappings into HubSpot
Create the HubSpot properties first, then connect. Clay reads the writable properties of the object type you pick and shows them for mapping, and the object list includes your custom objects, according to Clay University's HubSpot integration overview.
| Clay column | HubSpot contact property (internal name) | HubSpot type | Note |
|---|---|---|---|
| Fit Score | clay_fit_score | Number | Send a number, not "20 pts" |
| Intent Score | clay_intent_score | Number | |
| Timing Score | clay_timing_score | Number | |
| Total Score | clay_total_score | Number | Separate from HubSpot's own HubSpot Score property |
| Tier | clay_tier | Dropdown select (A, B, C) | Values must match exactly; this is the workflow trigger |
| Score Reasons | clay_score_reasons | Multi-line text | Shown on the contact record for reps |
| Scored At | clay_scored_at | Date picker | Drives the staleness check |
The push is two or three actions. First, Look up object on Contact by email, which returns the HubSpot Object ID when the contact exists. Then a conditional run: if an ID came back, Update object with that ID; if not, Create object. Clay's overview lists "Ignore blank values" as on by default for Update object, which is what you want: a blank Timing Score should not wipe a value already in HubSpot. One trap from the same page: the custom-object scopes are Enterprise-only, and leaving them on when connecting a lower tier makes authorization fail. For companies, associations and owners, see our Clay to HubSpot integration post.
Routing off the score in HubSpot
Route in HubSpot, not Clay; HubSpot knows owners, territories and working hours. Build one contact-based workflow per tier, triggered on "clay_tier is A" (or B, or C), with re-enrollment on so a contact moving from B to A re-enters.
- Tier A: rotate owner within the territory, create a task due in 15 minutes with clay_score_reasons in the body, post to Slack.
- Tier B: assign an owner and enroll in a sequence, or use Clay's own "Enroll a contact in a sequence" action once the sequence permissions are enabled on the connection, per Clay's overview.
- Tier C: add to a nurture list and set a re-score date 90 days out.
Keeping scores fresh and the failure modes
Stale scores. Timing signals expire: funding rounds age, job posts get filled. Re-run the timing enrichments weekly for active segments, recompute, push. The Scored At property lets a HubSpot workflow drop any A or B contact scored more than 30 days ago to C until refreshed.
Duplicates. If Create object runs without a Look up first, a second table scoring the same person creates a second contact. Always look up by email first. If HubSpot already has duplicates, the push updates whichever record the lookup returns. Clean first; our CRM data hygiene post has the order of operations.
Overwritten judgment. A rep marks a contact as not a fit; the next Clay run pushes "A" again. Add a checkbox property (clay_scoring_paused) that Clay reads in its Look up step and skips.
Decision guide: Clay scoring, HubSpot scoring, or both
| Situation | Recommendation | Why |
|---|---|---|
| Outbound-led, 2 to 10 reps, HubSpot Starter or Professional, inputs come from enrichment | Clay computes, HubSpot routes (this template) | The inputs only exist in Clay |
| Inbound-led, score is mostly form fills, page views and email engagement | HubSpot-native scoring | HubSpot already holds the behavior data |
| Both motions, Sales Hub Professional or above | Clay fit and timing into custom properties, HubSpot engagement score alongside, a workflow combines them | Each system scores what it sees |
Every enrichment column costs Clay credits per row, so filter on cheap ICP columns first; our Clay advanced workflow recipes post has the conditional-run pattern.
When it makes sense to hand this to GenFlows
If you have a GTM engineer who owns Clay and a HubSpot admin who owns workflows, build this yourself in a week with the template above; an agency adds cost without adding much. Hand it over when nobody owns both halves, when the score has to survive staff changes, or when scoring is one piece of a larger outbound system that also needs list building, copy and sending infrastructure. GenFlows is a Clay Artisan Solutions Partner and builds this pattern for clients on HubSpot: scoring tables, the push, the tier workflows, staleness checks, and the first 60-day weight review. Pricing depends on the number of signals and systems, so that is a conversation, not a page. Book a strategy call
FAQ
Is there a ready-made Clay lead scoring template I can copy?
Clay ships table templates and the community shares more, but a scoring template is only as good as its weights and inputs, which are specific to your ICP. Copy the structure above and set the weights from your own closed-won data; expect to revise them after 60 days.
What field mappings does Clay lead scoring need in HubSpot?
A number property for the total, a dropdown for the tier, multi-line text for reasons and a date for when it was scored. Create them before connecting Clay and keep the dropdown values identical to the strings the Clay formula outputs.
Can Clay trigger lead routing rules directly?
Clay can enroll contacts in sequences and add records to lists through its HubSpot actions, so simple routing is possible from the table. For owner rotation, working hours and territory logic, HubSpot workflows triggered on the tier property are the better home; the ops team can change them without touching Clay.
How is this different from HubSpot's own lead scoring?
HubSpot scores what HubSpot sees: form fills, page views, email engagement. Clay scores what enrichment finds: headcount, tech stack, hiring, funding, identified website visits. Outbound teams usually need the second set.
Does the Clay HubSpot integration work on HubSpot Free or Starter?
Clay's overview does not state a minimum HubSpot tier for the standard contact and company actions. It does say the custom-object scopes are Enterprise-only and must be switched off before connecting on other tiers.
The GenFlows team builds AI-powered cold outbound systems for B2B teams.