How-to · Typeform
Typeform lead scoring in monday.com: route leads by score
By Jefferson Huera Guzman Updated 6 min read
To use Typeform lead scoring in monday.com, give answers points in Typeform, then create two Calculated score automations in Typeform Integration Plus on the same form: one for scores at or above your threshold and one for scores below it. Each lead lands in one group, with its score in a Numbers column.
The flow you’re building
A demo request form brings in every kind of lead. Sales should call the strong ones today, and the rest can wait for a nurture sequence. This guide sends each lead to one of two groups on a board, based on the score Typeform calculates.
- Lead submits the form
- Typeform totals the score
- 60 or above: Sales-ready
- Below 60: Nurture
Use calculated scores and payments explains the template. This guide covers the decisions around it: how to score, where to set the line and how to stop two rules from firing at once.
What Calculated Score is
Calculated Score is Typeform’s number, not the app’s. Typeform keeps a running total in a variable called score, adds points through the logic on your form and sends the total with each response. The app reads that one number. It doesn’t calculate anything.
The app checks the score as soon as Typeform sends the response, before anything reaches monday.com:
| The response has | What the template does |
|---|---|
| A score above or below your Number | Compares the two as numbers, using your Condition |
| A score equal to your Number | Passes greater than or equal to, less than or equal to and equal to. Fails greater than and less than |
| A score of 0 | Treats it as a real score, so less than 60 passes |
| No score | Creates nothing, whichever Condition you picked |
Only score counts. If your form spreads points across other variables, such as one for fit and one for budget, the app can’t read them, so add every point to score.
A response that fails the check is skipped. It creates no item and leaves no entry in Run history, so a lead that’s missing from one group has usually gone to the other.
Give answers points in Typeform
Build the form first, because the app reads it when you set up the automation. These points are an example. Yours should reflect the leads your team actually closes.
| Question | Answer | Points |
|---|---|---|
| Company size | 1 to 10 | 0 |
| 11 to 50 | 10 | |
| 51 to 200 | 20 | |
| More than 200 | 30 | |
| Timeline | Just researching | 0 |
| This year | 20 | |
| This quarter | 40 | |
| Budget approved | Not yet | 0 |
| Yes | 30 |
Name, work email and company score nothing. They’re there to fill the item.
To pick the threshold, describe the weakest lead your sales team would still call. Here that’s an 11 to 50 company with budget approved, buying this year: 10 + 20 + 30 = 60. So 60 is the line.
Build the two automations
Both automations use the same template on the same form:
From Account, when a new entry in Form is received and only if the calculated score is Condition Number create an Item/Subitem in this Group/Item with this Typeform Data
| Automation | Condition | Number | Group/Item |
|---|---|---|---|
| High scores | greater than or equal to | 60 | Sales-ready |
| Low scores | less than | 60 | Nurture |
- On your board, click Automate, then Create, search for Typeform and choose the template above.
- Pick your Account and Form.
- Set Condition and Number from the first row of the table.
- In Item/Subitem, choose item, then pick the group in Group/Item.
- Click Typeform Data and map your answers, as described below.
- Click Create automation.
- Repeat these steps with the second row.

Put the score in a column
The group tells sales the tier. The number tells them who to call first. In Typeform Data, in both automations, map Calculated Score to a Numbers column named Score:

A form that takes a deposit can map its payment question too, as shown here. Keep these points in mind:
- Use a Numbers column. A Status column would add a new label for every score.
- Map the score on its own. Full Response posts the form’s answers, not the score, so map Calculated Score even if you also map Full Response to Item Update.
- Map the same answers in both automations. Otherwise, items in one group have empty columns.
Keep the rules from overlapping
Each automation checks every response on its own. There’s no “otherwise”, and every automation that passes creates its own item. So the two rules have to split the scores cleanly, and the threshold is where that goes wrong:
| Your two rules | Score 59 | Score 60 | Score 61 |
|---|---|---|---|
| greater than or equal to 60, less than 60 | Nurture | Sales-ready | Sales-ready |
| greater than or equal to 60, less than or equal to 60 | Nurture | Two items | Sales-ready |
| greater than 60, less than 60 | Nurture | No item | Sales-ready |
Use the same number in both rules, and let exactly one of them include it. When you move the threshold later, change Number in both automations. Changing only one opens a gap or an overlap.
If you want a third tier
A third automation is the usual way to overlap by accident. Add greater than or equal to 90 for a Hot group, and a score of 95 passes that rule and the 60 rule, so the lead gets two items. A 60 to 89 band can’t be built with a template, because each automation checks one number.
You have two options:
- Keep two groups and sort Sales-ready by Score. The strongest leads rise to the top, and there’s nothing new to overlap.
- Use a custom automation. Start with the Typeform response trigger, which passes Calculated Score to the next steps, and add monday.com’s own conditions. See Use Typeform responses in custom automations.
Test the threshold
Only responses submitted after you create the automations reach monday.com. Submit three test responses: a clear high score, a clear low score and a score of exactly 60. You should get three items, each in one group.
Inbound leads
Sales-ready
| Lead | Work email | Score | Timeline |
|---|---|---|---|
| Priya Nair | priya@example.com | 90 | This quarter |
| Sam Ortiz | sam@example.com | 60 | This year |
If the score of 60 created two items, or none, go back to the table above. If nothing arrived at all, see The automation doesn’t run.
Groups or a single column
Two automations aren’t the only setup. Pick the one that fits how your team works:
| Setup | Where leads land | Good for | Watch out for |
|---|---|---|---|
| Two Calculated score automations | One group per tier | Teams that work from groups | A repeat submission creates a second item, possibly in the other group |
| One create template with Calculated Score mapped | One group, sorted by Score | Thresholds that change often, because there’s no rule to edit | Nothing separates the leads for you |
| Update matching items, matched on email | One item per lead, with the score refreshed | Leads who come back to the form | Update templates take no score condition, and new items go to the board’s top group |
Plans are on the Typeform Integration Plus pricing page, and Plans and usage explains how runs are counted. For everything else the app does, read the Typeform monday.com integration guide.
Some screens shown on this site are illustrations, so yours may look a little different.
Frequently asked questions
What is Calculated Score?
It's the total in Typeform's score variable, which Typeform sends with each response. The app doesn't calculate anything. It reads that number and compares it with the one you set. Read more →
Can I use a Typeform variable other than score?
No. The app reads only the score variable, so other calculator variables can't be used in the condition or mapped to columns. Add all your points to score. Read more →
Why did one lead create two items?
Two automations passed. Each automation checks every response on its own, so rules that both include the threshold, or a third rule that overlaps, create one item each. Use greater than or equal to and less than with the same number. Read more →
Can I route leads into three tiers?
Not with templates alone. Each automation checks one number, so a band such as 60 to 89 can't be built. Sort your top group by score, or use a custom automation with monday.com's own conditions. Read more →
What happens when a lead submits the form twice?
Each submission creates a new item, because the Calculated score template only creates items. To keep one item per lead, use the update template and match on an email address, which leaves out the score condition. Read more →
Start with the complete guide
Complete guideTypeform monday.com integration: the complete guide
How to send Typeform responses to monday.com, create or update items, route them with conditions and embed forms in items and dashboards.
Read the guide →In the Help Center
- Use calculated scores and payments Create items only when a Typeform score passes a threshold or a payment succeeds, and map the score and payment status to board columns.
- Run an automation only for certain answers Use condition templates to create items only when an answer is a specific choice, a number passes a threshold or a text answer contains a word.
- Update existing items by matching a response Find the monday.com item that matches a Typeform answer, such as an email address, and update it, add a subitem to it or create a new item.
- Use Typeform responses in custom automations Start a custom automation or a monday Workflow with the Typeform response trigger and use each answer in the steps that follow.
- Field mapping and supported column types Which Typeform question types the app reads, which monday.com columns it can fill, how each value is written and what you can't map.
More Typeform guides
- Comparison
Typeform to monday.com without Zapier: options compared
Compare monday.com's built-in Typeform integration, Zapier or Make, and Typeform Integration Plus by question types, conditions, updates and cost.
- How-to
Embed a Typeform in monday.com with per-client forms
When to embed a Typeform in monday.com and when to automate, plus how to show each client's own form from a Link column on their item.