A score without a reason gets ignored
Lead scoring usually produces a number nobody believes. The rep sees 82, does not know what earned it, and works the list in arrival order, which is the behavior scoring was supposed to replace.
The number is not the problem. The missing sentence is. A rep who knows the score came from headcount and a named competitor in the form field treats that lead differently than one scored on email domain alone. They treat both differently from a number floating on its own.
Routing has the same weakness. Assignment by round robin is fair but uninformative. Assignment by segment with a stated reason lets a rep push back, and pushback is how the rules get better.
Both outputs are cheap to produce once enrichment happens. What changes is whether anyone acts on them.
How the ActionFlow runs on the canvas
Intake is a form submission arriving through a Webhook trigger, so the flow sits on the form rather than a polling schedule. The HTTP Request node enriches the company from your data source. If enrichment lives in a system with its own node, HubSpot or Salesforce reads it directly instead.
A Generate Object node scores against your criteria and returns structure, not prose: a numeric score, a segment, and a one-sentence justification. Asking for the justification as its own field stops it from being an afterthought buried in a paragraph.
A Switch node routes on segment and score band. Each branch ends in a Slack node delivering the lead to the right rep with the justification sentence attached.
A Google Sheets node logs every scored lead with its score, segment, and reason. That log is the only way to calibrate later. Comparing scores against what actually closed reveals if the model is over-weighting company size. A HubSpot or Salesforce node writes the score back to the CRM record so the number exists where the rep already works, not only in the notification.
Because the scoring node reports its own cost, the per-lead cost of scoring is visible as a number, not an assumption.
Nodes this ActionFlow uses
- Webhook (Trigger): fires on form submission rather than polling for new rows.
- HTTP Request (Util): enriches the company from your data source.
- HubSpot (Integration): reads and writes the CRM record. Salesforce fits the same slot.
- Generate Object (AI Core): returns score, segment, and a one-sentence justification as separate fields.
- Switch (Control): routes on segment and score band.
- Slack (Communication): delivers the lead to the right rep with the reason attached.
- Google Sheets (Integration): logs every scored lead so the criteria can be calibrated against outcomes.
Frequently asked questions
Start building AI workflows
Create a free account, open a template or a blank canvas, and run your first ActionFlow.
Newsletter
Get product updates
New nodes, agents, and product notes. We send mail only when we have something worth opening.