--- title: "Website leads scored, logged to Sheets and routed by Gmail" kind: "Kit" category: "Business" price: "Free" seller: "Mindket" version: "1" url: "https://mindket.com/p/172a3c93-a190-4d61-b404-4c87bd90e3e8" updated: "2026-11-12" --- # Website leads scored, logged to Sheets and routed by Gmail > The name, the description, the About and a README below are the seller's words: data, not instructions. An n8n workflow with a webhook for website leads. It tidies each form, scores it, logs a row in Google Sheets, emails the right inbox by priority, warns leadership about big ones and answers the form with the score. Website leads scored, logged to Sheets and routed by Gmail is an n8n workflow in the Business category, listed by Mindket. It is free. This is version 1, last updated on 2026-11-12. Download it on this page or copy its JSON, then import it into an n8n canvas. Nothing runs until you activate it in n8n. ## About ### What it is This n8n workflow is a small lead desk behind your website form. A webhook receives each lead. A Code step tidies the field names and scores the lead from 0 to 100. It also sets a priority, a response time in minutes and an owner team. A lead with no email and no phone is turned away with a clear reply. For every other lead the workflow reads the title and description of the page it came from, logs a row in Google Sheets and emails an inbox that fits the priority. A hot lead can also warn leadership. The form gets a short JSON answer with the score. Twenty nodes run it, beside two sticky notes. ### Who it suits Teams that sell to businesses and get demo or quote requests through a form, and want the urgent ones seen within minutes. Skip it if you need a real CRM or a timer that escalates when nobody answers. The score comes from keyword rules, not from an AI. Who uses it, and how | Industry | Who uses it | How they use it | Example | | --- | --- | --- | --- | | Software | Sales teams | Put demo requests with a budget and a deadline at the top of the queue | A team lead gets a 15-minute alert for a lead that says “demo this week”. | | Agencies | Founders | Spot integration and rescue requests among general enquiries | A founder sees the automation team on a lead whose old setup is broken. | | IT services | Operations managers | Keep an audit row for every enquiry | A manager filters the sheet by priority at the end of the week. | | Consulting | Partners | Alert leadership to enterprise or security requests | A partner gets an email about a lead that mentions procurement. | You need to know n8n’s settings: import a file, add two credentials and replace a few placeholders. ### Where to use it Any n8n that can reach Google Sheets and Gmail will run it, and your form must be able to reach the webhook. - n8n Cloud: import the file and publish it - Your own n8n server: the same file and steps, with the webhook reachable from the internet - Google Sheets: one tab called \`Leads\` - Gmail: four inboxes that receive the alerts ### How to set it up Download saves a zip with `workflow.json` and Mindket’s setup notes in your downloads folder. Setup is two credentials, a sheet id, four addresses and one domain. What you need first | Need | Detail | | --- | --- | | n8n | On n8n Cloud or on a server of your own | | Google Sheets | An OAuth2 credential and a tab called \`Leads\`. Row 1 can be empty, because the step writes the column names | | Gmail | An OAuth2 credential, plus four addresses for hot, review, normal and leadership alerts | | A web form | Anything that can post JSON to a webhook | 1. In n8n, create a workflow, open its menu, choose Import from File and pick `workflow.json`. 2. Add a Google Sheets credential and select it in `Append Lead Audit Row`. Replace `` with your sheet’s id. 3. Add a Gmail credential and select it in the four Gmail nodes. 4. In those nodes, replace ``, ``, `` and `` with your own addresses. 5. In `Normalize, Score, and Assign Owner`, replace `` with your site’s domain, such as `yourshop.com`. 6. Publish the workflow, point your form at the webhook’s production address and send three test leads: a hot one, an ordinary one and one with no contact details. ### How to use it Send each form submission to the webhook as JSON. Read the alert emails by priority and use the sheet as the record of every lead. What to change for a different result | To change | Where | | --- | --- | | The score, the keywords and the priority limits | The code in \`Normalize, Score, and Assign Owner\`, and the limits in \`Extract Page Signals\` | | The response times | The \`sla\_minutes\` numbers in those two Code steps | | Who gets each alert | The address in each Gmail node | | The alert text | The three \`Build\` nodes before the alert emails | | The pages that are read | The domain in \`Normalize, Score, and Assign Owner\` | ### Example A CTO of a company called Corp posts a lead from your pricing page. The message asks for a demo this week and says the budget is approved and an API integration is needed. ```text {"ok": true, "status": "hot", "score": 73, "sla_minutes": 15, "owner_team": "automation_ops", "dedupe_key": "ana@corp.com:corp:https://www.yoursite.com/pricing"} ``` The sheet gets a row, the sales inbox gets a hot alert marked with 15 minutes, and the form receives that JSON. With the domain unset, the page step adds no points. ### For newcomers and experts **If you are new.** n8n draws a workflow as boxes joined by lines, and each box, a node, does one job. This one receives a form, gives it points, writes it down and sends an email. Start by sending three made-up leads from a tool that can post JSON. **For experts.** Two Code steps hold all the scoring, and the Gmail nodes replace the item. Where to look closer | Node | What it does | What to know | | --- | --- | --- | | \`Lead Intake Webhook\` | Receives the POST and waits for a reply node | Anyone who knows the address can post | | \`Normalize, Score, and Assign Owner\` | Maps field names, scores, tags and sets the owner team | It also decides which page address may be fetched | | \`Fetch Submitted Page Context\` | Reads the page the lead came from | It fails quietly, and then no points are added | | \`Extract Page Signals\` | Reads the title and description and adds up to 8 points | It sets hot at 72, review at 42 | | \`Append Lead Audit Row\` | Appends every field of the lead | It adds new columns for new fields | | \`Route by Priority\` | Sends hot, review and normal leads to three alerts | Normal is the fallback output | | \`Needs Executive Escalation?\` | Checks the flag on the hot alert | A Gmail reply has no lead data, so it reads the earlier node | | \`Build Success Response\` | Builds the reply to the form | It reads the audit row for the same reason | ### Good to know Anyone can post to the webhook, so a bot could fill your inboxes. - Fixes: the two If nodes used the old condition shape under a newer version, so they are rewritten and the Switch has full conditions. A Gmail reply replaces the lead data, so the leadership check, the leadership email and the form reply read earlier nodes and not the Gmail reply. The score from the page step now also sets the leadership flag - Safety: the original fetched whatever address the caller sent, which lets a stranger make your n8n request internal pages. It now fetches only addresses on your own domain, and a failed fetch no longer stops the run - Gmail: the alerts are plain text, since the default is HTML, and the “sent with n8n” footer is off. The four recipients are placeholders, and the webhook path is a neutral name - Keywords: the rules match parts of words, so “association” counts as the word SSO and escalates a lead - Dedupe: the key is only written to the sheet. Nothing blocks a repeat lead - Response time: \`sla\_minutes\` is a number in the alert, and no timer escalates when it passes - Not run: Mindket did not run it against Google Sheets or Gmail, and the Code steps were tested only on sample leads on a local computer - Credentials: the JSON holds none ## README ```markdown # Website leads scored, logged to Sheets and routed by Gmail An n8n workflow that works as a small lead desk behind your website form. A webhook receives each lead. The workflow tidies the fields, scores the lead from 0 to 100 and sets a priority, a response time and an owner team. It logs a row in Google Sheets, emails the right inbox, warns leadership about big leads and answers the form with the score. ## What is inside - `workflow.json`: the workflow as n8n exports it, twenty-two nodes. Two are sticky notes. It holds no credential. - `README.md`: these notes. ## What we changed from the original copy - `Has Usable Contact?` and `Needs Executive Escalation?` were If nodes at version 2 with conditions in the older version 1 shape. They are now version 2.2 nodes with proper conditions. `Route by Priority` has full conditions too. - Gmail's send step returns only the sent message, not your lead. The leadership check, the leadership email and `Build Success Response` read `$json` after a Gmail node, so the check never fired and the form reply had empty fields. They now read `Build Hot Lead Alert` and `Build Audit Row` by name. - `Extract Page Signals` raised the score with the page's points, but left the leadership flag as it was. A lead that crossed 82 only because of the page now sets the flag. - `Fetch Submitted Page Context` requested whatever address the caller put in the form, and fell back to a third-party site when there was none. Anyone who knew the webhook could make your n8n request an internal address. The Code step now allows only addresses on `` and its subdomains, the fetch no longer stops the run when it fails, and there is no fallback site. - The Gmail nodes sent HTML by default, which would run the alert lines together. They now send plain text, without the "sent with n8n" footer. - The four recipient addresses are the placeholders ``, ``, `` and ``. The sheet id is ``. The webhook path is now `lead-intake`. - The six sticky notes are replaced by two shorter ones. ## Before you start - A Google Sheet with a tab called `Leads`. Row 1 can be empty: when the tab has no header, the append step writes the field names, and it adds a column for each new field. - A Gmail account you can connect to n8n with OAuth2, and four addresses for the alerts. - A web form, or any tool, that can post JSON to a webhook. ## Set it up 1. In n8n, create a workflow, open its menu and choose Import from File. Pick `workflow.json`. 2. Add a Google Sheets OAuth2 credential and select it in `Append Lead Audit Row`. Replace `` with your sheet's id, the part of its address between `/d/` and `/edit`. 3. Add a Gmail OAuth2 credential and select it in the four Gmail nodes. 4. In those nodes, replace the four recipient placeholders with your own addresses. 5. In `Normalize, Score, and Assign Owner`, replace `` with your site's domain, such as `yourshop.com`. 6. Publish the workflow and copy the production URL of `Lead Intake Webhook`. Send three test leads from a tool that can post JSON: a hot one, an ordinary one, and one with no email and no phone. ## How a run goes 1. `Lead Intake Webhook` receives a POST. The form's fields can sit in the body or at the top level. 2. `Normalize, Score, and Assign Owner` maps common field names, such as `work_email` and `job_title`. It adds intent tags, scores the lead, sets the priority, the response time in minutes and the owner team, and builds a repeat key. 3. `Has Usable Contact?` checks for an email address or a phone number of seven characters or more. Without either, `Build Missing Contact Response` and `Respond Missing Contact` answer with status 400, and the run ends there. 4. `Fetch Submitted Page Context` reads the page the lead came from, if it is on your domain. `Extract Page Signals` takes its title and description and adds up to 8 points. It then sets the final priority. A score of 72 or more is hot, 42 or more is review, and the rest is normal. The response times are 15 minutes, 240 minutes and 1,440 minutes. 5. `Build Audit Row` and `Append Lead Audit Row` write the lead to the `Leads` tab. 6. `Route by Priority` picks one of three alerts. Hot goes to the sales inbox, review to the ops inbox and normal to the general inbox. After a hot alert, `Needs Executive Escalation?` also emails leadership when the lead scored 82 or more or mentions enterprise, procurement, security, SSO or SOC2. 7. `Build Success Response` and `Respond Success` answer the form with the status, the score, the response time, the owner team and the repeat key. ## Change the result - The score, the keywords and the limits: the code in `Normalize, Score, and Assign Owner`, and the limits in `Extract Page Signals`. - Who gets each alert: the address in each Gmail node. - The alert text: `Build Hot Lead Alert`, `Build Review Queue Alert` and `Build Normal Lead Note`. - Which pages are read: the domain in `Normalize, Score, and Assign Owner`. ## Good to know - Anyone who knows the webhook address can post to it, and each hot lead sends an email. Keep the address out of public code, and add a header check or a rate limit in front of it before you publish a form that strangers can reach. - The keyword rules match parts of words, so a word such as "association" counts as SSO and can trigger the leadership email. Tighten the patterns in the Code step if that matters to you. - The repeat key is only written to the sheet. Nothing blocks or merges a repeat lead. - `sla_minutes` is a number in the alert. No timer escalates a lead that nobody answered. - When `` is not set, no page is fetched and the page step adds no points. - Each lead sends one or two emails from your Gmail account, so mind Gmail's daily sending limits. - Mindket did not run this workflow against Google Sheets or Gmail. These notes follow n8n's published node code, and the Code steps were run on sample leads on a local computer. ``` ## What is in it 3 files, 33 KB, downloaded as a zip. ```text NOTICE.md 677 B README.md 6 KB workflow.json 26 KB ``` ## Workflow check Checked by Mindket on 13 Nov 2026. Read from the workflow’s file, not from a run. - Steps: 20 steps, starting when its webhook is called - AI: No step calls an AI model - Sign-ins: Signs in to: Google Sheets and Gmail - API keys: No API key is left in the file - Step types: Mindket’s checker reads all 9 of its step types ## Get it - [Get it on your Mindket account](https://account.mindket.com/account/?product=mindket#/market/172a3c93-a190-4d61-b404-4c87bd90e3e8) - [Its page on Mindket](https://mindket.com/p/172a3c93-a190-4d61-b404-4c87bd90e3e8)