Practical lead scoring bot demo

A developer’s demo shows how a sales form can be triaged automatically: one workflow scores each lead from 0 to 100 and routes the result to chat, email, or a spreadsheet. (x.com) The setup uses n8n, a low-code automation tool that can start from a built-in form or a webhook, then pass the submission through connected steps. n8n’s documentation says Form Trigger starts a workflow from a submitted form, while Webhook can receive data from other apps and services. (docs.n8n.io, docs.n8n.io) The language model piece is Google’s Gemini, which can be told to return structured JavaScript Object Notation instead of free text. Google says Gemini supports JSON Schema-based structured outputs, which makes it easier to return a score, a reason, and a routing label that later steps can read reliably. (ai.google.dev) That is the basic lead-scoring pattern: turn messy form answers into a small set of fields a sales team can act on. In this demo, the action buckets are “hot” leads sent to Telegram, “warm” leads sent an email, and “cold” leads logged to Google Sheets. (x.com) n8n already ships the plumbing for that kind of flow. Its product pages show ready-made combinations for Gmail, Google Sheets, Telegram, and artificial intelligence tools, and its workflow library includes Gemini-based outreach templates that write personalized emails and update Sheets records. (n8n.io, n8n.io, docs.n8n.io) The appeal for small sales teams is speed at the top of the funnel. A Telegram alert can reach a human as soon as a high-scoring form arrives, while lower-scoring leads can be answered or archived without someone reading every submission by hand. (x.com, n8n.io) The tradeoff is that an automated score is only as good as the prompt and the fields it sees. Google’s Gemini documentation frames structured output as a way to keep responses predictable, but it does not make the underlying judgment correct; teams still have to define what counts as a qualified buyer, urgent request, or low-value inquiry. (ai.google.dev) There are also operational limits once a workflow starts sending mail at volume. Google says Gmail and Google Workspace accounts can hit daily sending and recipient caps, and accounts that exceed those limits can be blocked from sending new messages for up to 24 hours. (support.google.com, support.google.com) n8n’s own deployment model matters too. Its documentation says forms and webhooks use test URLs while a workflow is being built, then switch to production URLs after the workflow is published, which is the step that makes a demo behave like a live intake system. (docs.n8n.io, docs.n8n.io) What the post captures is not a new model or a new sales tactic, but a practical assembly of existing parts: a form, a scoring prompt, a routing rule, and three destinations. Inbound volume that once sat in a shared inbox can now be sorted the moment it arrives. (x.com, ai.google.dev, docs.n8n.io)