January 22, 2026

Google Sheets + Email: instant lead roadmaps sent

Lisa Granqvist Partner Workflow Automation Expert

Get a free AI assessment → ⬇️ Use template

Your lead form works. The problem starts right after. Someone has to copy the details into a sheet, think through a “quick plan,” format it nicely, and send it fast enough that the lead still cares.

This lead roadmap automation hits marketing managers first, because speed and consistency are the whole game. But agency owners feel it too. Same for a solo consultant who wants to look polished without living in their inbox.

This workflow logs every new lead in Google Sheets, generates a tailored roadmap with AI, sends it by email as clean HTML, and flags delivery for follow-up. You’ll see what it does, what you need, and how the pieces fit together.

How This Automation Works

The full n8n workflow, from trigger to final output:

n8n Workflow Template: Google Sheets + Email: instant lead roadmaps sent

Click to explore

flowchart LR

    subgraph sg0["Style Agent Flow"]
        direction LR
        n0["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/webhook.dark.svg' width='40' height='40' /></div><br/>Webhook"]
        n1["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/telegram.svg' width='40' height='40' /></div><br/>Send a text message"]
        n2@{ icon: "mdi:message-outline", form: "rounded", label: "Send email", pos: "b", h: 48 }
        n3@{ icon: "mdi:robot", form: "rounded", label: "Style Agent", pos: "b", h: 48 }
        n4@{ icon: "mdi:robot", form: "rounded", label: "AI Consultant", pos: "b", h: 48 }
        n5@{ icon: "mdi:message-outline", form: "rounded", label: "Generated Roadmap to Customer", pos: "b", h: 48 }
        n6@{ icon: "mdi:cog", form: "rounded", label: "Add Customer Data", pos: "b", h: 48 }
        n7@{ icon: "mdi:cog", form: "rounded", label: "Update row(s)", pos: "b", h: 48 }
        n8@{ icon: "mdi:brain", form: "rounded", label: "GPT 5 Nano", pos: "b", h: 48 }
        n9@{ icon: "mdi:brain", form: "rounded", label: "GPT 5 Mini", pos: "b", h: 48 }
        n0 --> n6
        n9 -.-> n3
        n8 -.-> n4
        n3 --> n5
        n4 --> n3
        n7 --> n2
        n7 --> n1
        n6 --> n4
        n5 --> n7
    end

    %% Styling
    classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
    classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
    classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
    classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
    classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
    classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
    classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
    classDef disabled stroke-dasharray: 5 5,opacity: 0.5
    class n3,n4 ai
    class n8,n9 aiModel
    class n0 api
    classDef customIcon fill:none,stroke:none
    class n0,n1 customIcon

The Problem: Great leads go cold while you “get back to them”

Most teams don’t lose leads because they’re bad at marketing. They lose them in the gap between “new submission” and “meaningful response.” Someone sees the form entry, pastes it into Google Sheets, skims the website, guesses what the lead needs, writes a rough plan, then tries to make the email look professional. Meanwhile the lead is comparing you with two competitors who replied faster. And honestly, even if you do respond, the quality swings depending on who’s busy, who’s tired, and who’s remembering your process this week.

It adds up fast. Here’s where it breaks down.

Leads sit for hours (or days) because “someone needs to draft the reply.”
Your first-touch emails vary wildly, so prospects get different levels of clarity and confidence.
Copy-paste entry into a sheet leads to missing fields, typos, and messy tracking later.
You can’t reliably tell who received what unless somebody manually updates delivery status.

The Solution: AI-generated roadmaps delivered instantly, tracked in your sheet

This n8n workflow turns a plain lead form submission into a fast, high-quality “next steps” roadmap that lands in the lead’s inbox automatically. It starts with an inbound webhook that receives the lead details from your form or website. The workflow then stores (or updates) that lead in a table so you have a reliable record from the beginning. Next, an AI agent generates a tailored roadmap based on what the lead submitted, then a second agent wraps it in professional HTML styling so it reads like a real deliverable, not a raw AI blob. Finally, the workflow emails the finished roadmap to the lead, marks the delivery status, and can notify your team internally so follow-up is consistent.

The workflow begins the moment the form is submitted. AI produces the roadmap and formats it into an email-ready HTML document. Then n8n sends it, records what happened, and pings you for follow-up so nothing disappears into the void.

What You Get: Automation vs. Results

What This Workflow Automates

Results You’ll Get

Captures lead data from your form via a webhook and stores it automatically.
Generates a personalized roadmap using an AI model based on the lead’s inputs.
Formats the roadmap into clean, email-ready HTML with consistent styling.
Sends the roadmap email and then updates delivery status for tracking.

Cut first-response effort from about 20 minutes to near zero per lead.
Every lead gets an instant “wow” moment instead of a generic receipt email.
Follow-ups get easier because your team sees delivery status and context.
Fewer copy-paste errors, which means cleaner reporting and segmentation later.
A more consistent first impression, even when your team is slammed.

Example: What This Looks Like

Say you get 10 inbound leads a week. Manually, it’s usually about 10 minutes to log the details in Google Sheets and about 10 minutes to write and format a “mini roadmap,” so roughly 20 minutes per lead (over 3 hours a week). With this workflow, you spend maybe 2 minutes checking the sheet and skimming the generated roadmap for edge cases, while the AI + email delivery runs in the background. That’s about 3 hours back every week, and the lead gets their plan within minutes instead of tomorrow.

What You’ll Need

n8n instance (try n8n Cloud free)
Self-hosting option if you prefer (Hostinger works well)
Google Sheets for logging leads and delivery status.
Email (SMTP) to send the roadmap to leads.
OpenAI-compatible API key (get it from your OpenAI or Azure OpenAI dashboard).

Skill level: Intermediate. You’ll connect a webhook to your form, set up email credentials, and adjust prompts so the roadmap matches your offer.

Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).

How It Works

A form submission triggers everything. Your website or form tool sends the lead’s fields (name, email, company, goals, budget, notes) to an n8n webhook endpoint. One request, instantly captured.

The lead is saved and prepared for AI. The workflow upserts the record so returning leads don’t create duplicates, then normalizes fields into a clean structure the AI agent can understand.

AI builds the roadmap and polishes it. The “Automation Advisor” agent produces the actual plan (phases, quick wins, timeline, and recommended next step). Then the HTML styling agent turns it into a readable, branded-looking email layout so you aren’t sending a wall of text.

Email goes out and tracking updates happen automatically. n8n sends the roadmap to the lead, marks delivery status in your table, and pushes internal notifications via Telegram and/or an internal email so your team knows who to follow up with.

You can easily modify the roadmap structure to match your service packages, sales process, or industry. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Webhook Trigger

Set up the inbound endpoint that receives lead data and starts the workflow.

Add and open Inbound Webhook Trigger.
Set HTTP Method to POST.
Set Path to lead-magnet.
Save the node to generate the production URL, then copy it for your lead capture form.

Make sure your form payload uses fields that match the expressions used later, such as body.name, body.email, body.primaryGoal, body.companyUrl, and body.companyType.

Step 2: Connect the Lead Data Table

Store incoming lead data and prepare it for the AI roadmap generation.

Add Upsert Client Record and connect it to Inbound Webhook Trigger.
Set Operation to upsert.
Choose your Data Table in dataTableId (e.g., Lead Magnet).
In Columns, map values exactly as shown: Name to ={{ $json.body.name }}, Email to ={{ $json.body.email }}, Challenges to ={{ $json.body.primaryGoal }}, CompanyURL to ={{ $json.body.companyUrl }}, CompanyType to ={{ $json.body.companyType }}, EmailSent to false, and Tag to New.
In Filters, set the Email condition to ={{ $json.body.email }} to avoid duplicates.

⚠️ Common Pitfall: If the incoming webhook doesn’t include body.email, the upsert will fail to match existing records.

Step 3: Set Up the AI Roadmap Generation

Generate the automation roadmap and convert it into a styled HTML email.

Connect Automation Advisor after Upsert Client Record.
Set Text to ={{ $json.Challenges }} and keep Prompt Type as define.
Connect Nano Language Model as the language model for Automation Advisor.
Credential Required: Connect your openAiApi credentials to Nano Language Model. (Credentials are added to the language model node, not the agent.)
Connect HTML Styling Agent after Automation Advisor.
Set Text in HTML Styling Agent to ={{ $json.output }} and keep Prompt Type as define with the provided system message.
Connect Mini Language Model as the language model for HTML Styling Agent.
Credential Required: Connect your openAiApi credentials to Mini Language Model. (Credentials are added to the language model node, not the agent.)

The AI chain flows as Upsert Client Record → Automation Advisor → HTML Styling Agent to produce email-ready HTML.

Step 4: Configure Outbound Email and Status Updates

Send the roadmap to the lead and update delivery status in your data table.

Add Deliver Roadmap Email after HTML Styling Agent.
Credential Required: Connect your smtp credentials.
Set HTML to ={{ $json.output }}.
Set Subject to Your roadmap is ready!.
Set To Email to ={{ $('Upsert Client Record').item.json.Email }}.
Set From Email to [Your Company] <[YOUR_EMAIL]>.
Add Mark Delivery Status after Deliver Roadmap Email and set Operation to update.
In Mark Delivery Status, set Tag to Delivered and EmailSent to true.
Set the filter keyValue to ={{ $('Upsert Client Record').item.json.id }} to update the correct record.

⚠️ Common Pitfall: If Upsert Client Record does not return an id, the update in Mark Delivery Status won’t apply. Confirm your data table is set to return item IDs.

Step 5: Configure Notifications (Parallel Branch)

Send internal alerts once delivery is marked complete.

Connect Internal Email Alert and Telegram Alert Notice after Mark Delivery Status.
Mark Delivery Status outputs to both Internal Email Alert and Telegram Alert Notice in parallel.
In Internal Email Alert, set Subject to New Client!, To Email to [YOUR_EMAIL], and From Email to Lead Magnet <[YOUR_EMAIL]>.
Credential Required: Connect your smtp credentials.
Set HTML to the combined content: =Client: {{ $json.Name }} {{ $json.Email }} {{ $json.CompanyURL }} Type: {{ $json.CompanyType }} {{ $json.Challenges }} {{ $('HTML Styling Agent').item.json.output }}.
In Telegram Alert Notice, set Chat ID to [YOUR_ID] and Text to =Client: {{ $json.Name }} {{ $json.Email }} {{ $json.CompanyURL }} Type: {{ $json.CompanyType }} {{ $json.Challenges }}.
Credential Required: Connect your telegramApi credentials.

Parallel alerts ensure internal teams receive updates without delaying email delivery to the lead.

Step 6: Test and Activate Your Workflow

Verify the workflow end-to-end and enable it for production.

Click Execute Workflow and send a test POST request to the Inbound Webhook Trigger URL with sample lead data.
Confirm a new or updated record appears from Upsert Client Record with Tag set to New.
Verify Deliver Roadmap Email sends a styled HTML email to the lead’s address.
Check Mark Delivery Status updates the record to EmailSent true and Tag Delivered.
Confirm both Internal Email Alert and Telegram Alert Notice fire in parallel.
Toggle the workflow to Active to use it in production.

🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Common Gotchas

Google Sheets permissions and OAuth scopes can trip you up. If rows aren’t writing, check the connected Google account in n8n Credentials and confirm it can edit the target sheet.
If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.

Frequently Asked Questions

How long does it take to set up this lead roadmap automation automation?

About 30 minutes once your email and AI credentials are ready.

Do I need coding skills to automate lead roadmap automation?

No. You’ll mostly connect accounts and adjust a few prompts and fields.

Is n8n free to use for this lead roadmap automation workflow?

Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in OpenAI API costs, which are usually a few cents per roadmap depending on length.

Where can I host n8n to run this automation?

Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.

Can I customize this lead roadmap automation workflow for different industries?

Yes, and you should. The easiest win is updating the “Automation Advisor” agent prompt to include your industry, your offer, and the way you like to structure phases (for example: “audit, quick wins, 30-day plan, 90-day plan”). You can also adjust the HTML styling agent to match your brand colors, add a logo, or include a calendar link for booking. If you want different outputs by lead type, add a Switch node that routes prompts based on a field like budget, company size, or goal.

Why is my Google Sheets connection failing in this workflow?

Usually it’s expired Google credentials or the wrong account connected. Re-authenticate the Google Sheets credential in n8n, then confirm the sheet is shared with that account and the workflow is pointing at the correct spreadsheet/tab. If it works for some leads and fails for others, look for unexpected blanks or extra-long text fields coming from your form that break your mapping.

How many leads can this lead roadmap automation automation handle?

On n8n Cloud, the limit is mainly your monthly executions (Starter is fine for small pipelines, and higher plans cover more). If you self-host, there’s no hard execution cap, so it mostly depends on your server and email provider rate limits. Practically, this workflow can handle dozens of leads a day on a basic setup, and more if you keep prompts tight and avoid huge HTML outputs.

Is this lead roadmap automation automation better than using Zapier or Make?

Often, yes, because n8n handles multi-step logic, routing, and AI agent workflows without you fighting plan limits every time you add a branch. Self-hosting is also a big deal if your volume grows. Zapier or Make can still be fine if you only want a simple “form submission → send email” flow with no AI, no formatting, and no tracking. This workflow is doing more than that. Talk to an automation expert if you want a quick recommendation for your exact setup.

You set this up once, and every new lead gets a fast, polished roadmap that feels personal. The workflow handles the repetitive parts so you can spend your time on real conversations.

Need Help Setting This Up?

Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.

Lisa Granqvist

Workflow Automation Expert

Expert in workflow automation and no-code tools.

{
"meta": {
"instanceId": "c6c03371d29d259bbb2b27e733a1ea5f09dc30c07104013ef5e918eb5395fe76"
},
"name": "Automated Lead Capture Delivery",
"tags": [],
"nodes": [
{
"id": "flowpast-topbar-9973",
"name": "Flowpast Branding",
"type": "n8n-nodes-base.stickyNote",
"position": [
0,
20
],
"parameters": {
"color": 7,
"width": 1160,
"height": 80,
"content": "## Flowpast.com | Automation Workflow Library\n**\ud83d\udcd6 Full tutorial & setup guide:** flowpast.com"
},
"typeVersion": 1
},
{
"id": "64ba1a8b-05ce-4d71-a65e-aa44049b9091",
"name": "Inbound Webhook Trigger",
"type": "n8n-nodes-base.webhook",
"position": [
10,
140
],
"webhookId": "dad5bd4f-33f9-4447-b960-164f5e14dc37",
"parameters": {
"path": "lead-magnet",
"options": [],
"httpMethod": "POST"
},
"typeVersion": 2.1
},
{
"id": "92cf2fe4-cc6a-49c9-8024-6a212aa6c58e",
"name": "Telegram Alert Notice",
"type": "n8n-nodes-base.telegram",
"position": [
660,
550
],
"webhookId": "6758bab3-ca3e-46e7-96c1-46412ed5dba2",
"parameters": {
"text": "=Client:\n{{ $json.Name }}\n{{ $json.Email }}\n{{ $json.CompanyURL }}\n\nType: {{ $json.CompanyType }}\n{{ $json.Challenges }}\n",
"chatId": "[YOUR_ID]",
"additionalFields": {
"parse_mode": "HTML",
"appendAttribution": false
}
},
"credentials": {
"telegramApi": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 1.2
},
{
"id": "08c00b8e-6316-43a2-81db-de66e804d918",
"name": "Internal Email Alert",
"type": "n8n-nodes-base.emailSend",
"position": [
310,
580
],
"webhookId": "6ff6bcba-60ec-45c5-8562-87d2ff3317ae",
"parameters": {
"html": "=Client:\n{{ $json.Name }}\n{{ $json.Email }}\n{{ $json.CompanyURL }}\n\nType: {{ $json.CompanyType }}\n{{ $json.Challenges }}\n\n{{ $('HTML Styling Agent').item.json.output }}",
"options": {
"appendAttribution": false
},
"subject": "New Client!",
"toEmail": "[YOUR_EMAIL]",
"fromEmail": "Lead Magnet <[YOUR_EMAIL]>"
},
"credentials": {
"smtp": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 2.1
},
{
"id": "03d9bd9c-3058-4769-8ae7-28c00a4ec789",
"name": "HTML Styling Agent",
"type": "@n8n/n8n-nodes-langchain.agent",
"position": [
450,
360
],
"parameters": {
"text": "={{ $json.output }}",
"options": {
"systemMessage": "=# System Prompt: Professional HTML Report Generator\n\nYou are an AI agent that transforms reports into professional, email-ready HTML documents. Output must be complete and require no revisions.\n\n## Core Rules\n\n1. **NEVER ask follow-up questions** - work with provided information\n2. **Output only complete HTML** - all CSS inline in `<style>` tags\n3. **Email-compatible** - no external dependencies, simple CSS only\n4. **Self-contained** - ready to copy/paste into email and send\n\n## Required HTML Structure\n```html\n<!DOCTYPE html>\n<html lang=\"en\">\n<head>\n    <meta charset=\"UTF-8\">\n    <meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\">\n    <title>[Report Title]</title>\n    <style>\n        /* Inline CSS here */\n    </style>\n<link rel="preload" as="image" href="https://flowpast.s3.eu-north-1.amazonaws.com/featured_blog_images/106439.webp"><link rel="preload" as="image" href="https://flowpast.s3.eu-north-1.amazonaws.com/featured_blog_images/106439.webp"></head>
\n<body>\n    <header>\n        <img src=\"[Your Logo Link]\" alt=\"Company Logo\" class=\"logo\">\n        <h1>[Report Title]</h1>\n        <p>[Date and subtitle]</p>\n    </header>\n    \n    <section>\n        <h2>[Section Title]</h2>\n        <!-- Content -->\n    </section>\n    \n    <footer>\n        <p>Generated: [Date] | [Source]</p>\n    </footer>\n</body>\n</html>\n\nStandard CSS (Always Include Inline)\ncss* { margin: 0; padding: 0; box-sizing: border-box; }\nbody { font-family: 'Segoe UI', Arial, sans-serif; line-height: 1.6; color: #333; background: #fff; max-width: 900px; margin: 0 auto; padding: 40px 20px; }\nheader { border-bottom: 3px solid #2c5282; padding-bottom: 20px; margin-bottom: 30px; }\n.logo { max-height: 30px; margin-bottom: 20px; }\nh1 { color: #1a365d; font-size: 2.2em; margin-bottom: 10px; }\nh2 { color: #2c5282; font-size: 1.6em; margin-top: 30px; margin-bottom: 15px; border-bottom: 2px solid #e2e8f0; padding-bottom: 8px; }\nh3 { color: #2d3748; font-size: 1.2em; margin-top: 20px; margin-bottom: 10px; }\np { margin-bottom: 15px; }\nsection { margin-bottom: 35px; }\ntable { width: 100%; border-collapse: collapse; margin: 20px 0; box-shadow: 0 2px 4px rgba(0,0,0,0.1); }\nthead { background-color: #2c5282; color: white; }\nth, td { padding: 12px 15px; text-align: left; border: 1px solid #e2e8f0; }\nth { font-weight: 600; text-transform: uppercase; font-size: 0.9em; }\ntbody tr:nth-child(even) { background-color: #f7fafc; }\ntbody tr:hover { background-color: #edf2f7; }\nul, ol { margin: 15px 0 15px 25px; }\nli { margin-bottom: 8px; }\nfooter { margin-top: 50px; padding-top: 20px; border-top: 2px solid #e2e8f0; text-align: center; color: #718096; font-size: 0.9em; }\n.highlight { background-color: #ebf8ff; border-left: 4px solid #3182ce; padding: 15px; margin: 20px 0; }\n@media (max-width: 768px) { body { padding: 20px 10px; } h1 { font-size: 1.8em; } table { font-size: 0.9em; } }\n\nContent Organization\nHeader: Title (h1), date/subtitle (p)\n\nBody Sections:\nKey metrics/executive summary (use tables or .highlight boxes)\nMain findings (h2 headings, lists for clarity)\nDetailed analysis (h3 subsections)\nData tables (always use thead/tbody)\n\nFooter: Generation date, source/author\nFormatting Rules\n\nUse semantic HTML: <header>, <section>, <footer>\nProper heading hierarchy: h1 \u2192 h2 \u2192 h3\nTables: clear headers, alternating row colors, numbers right-aligned\nLists: concise bullets (1-2 lines each)\nWhite space: generous spacing between sections\n\nEmail Compatibility\n\nInline CSS only (no external stylesheets)\nWeb-safe fonts (Arial, Segoe UI, Verdana)\nSimple CSS (avoid flexbox, grid, complex selectors)\nMax-width: 900px on body\nUse hex colors only\n\nOutput Format\nProvide ONLY the complete HTML document. No explanations, no markdown code blocks, no commentary. Start with <!DOCTYPE html> and end with </html>. Document must be immediately usable in email."
},
"promptType": "define"
},
"typeVersion": 2.2
},
{
"id": "5dbbc30e-9997-4b3f-ab19-3903360eb0bf",
"name": "Automation Advisor",
"type": "@n8n/n8n-nodes-langchain.agent",
"position": [
650,
130
],
"parameters": {
"text": "={{ $json.Challenges }}",
"options": {
"systemMessage": "=## Overview\nYou are an **Expert AI Automation Consultant** from *[Your Company Name]*.  \nYour role is to take any manual, repetitive, or inefficient business process described in the provided information and transform it into a **clear, personalized automation roadmap** \u2014 focused on results, ROI, and next steps.\n\nYou think like a **strategic consultant**, not a technician:  \n- Diagnose first, prescribe second.  \n- Prioritize business value and clarity over technical detail.  \n- Never ask follow-up questions; use only the information given to produce your best, most actionable report.\n\n---\n\n## Core Responsibilities\n\n### 1. Diagnose the Current Workflow\n- Analyze the description to identify the main process, tools used, time involved, and bottlenecks.  \n- Determine whether AI is needed or if simpler automation (e.g., n8n, Zapier, CRM workflow) is faster and more cost-effective.\n\n### 2. Expose Inefficiencies\n- Map the workflow: triggers \u2192 inputs \u2192 decision points \u2192 outputs.  \n- Highlight pain points: delays, manual errors, compliance risks, or resource waste.\n\n### 3. Design the Automation Roadmap\nStructure the roadmap into three actionable phases:  \n- **Quick Wins (MVP: 1\u20132 weeks)** \u2013 fast, low-cost automations with measurable ROI.  \n- **Scalable Solution (4\u20138 weeks)** \u2013 integrated automations and CRM/AI logic.  \n- **Long-Term Improvements (3\u20136+ months)** \u2013 advanced AI, analytics, governance, or multi-channel systems.\n\nEach phase should include:  \n- Goals and deliverables  \n- Key tools/platforms (e.g., n8n, APIs, HubSpot, vector DBs, etc.)  \n- Estimated time or effort\n\n### 4. Quantify ROI\n- Estimate time saved, cost reduction, or efficiency gain.  \n- Express ROI in clear, concrete terms:  \n  Example: \u201cAutomating this saves 12 hours/week \u00d7 $60/hour = $2,880/month.\u201d  \n- Include a payback period estimate (e.g., \u201cROI achieved within 1\u20132 months\u201d).\n\n### 5. Deliver a Clear, Readable Output\n- Write in plain, confident, business language.  \n- Use section headers, tables, and short bullet points.  \n- Avoid jargon; focus on clarity and practical outcomes.  \n- Optionally personalize based on any form data (company size, role, goals).\n\n---\n\n## Output Format\n\n**Outbound Automation Roadmap \u2014 [Process/Company Name]**  \n_Date: [current date]_\n\n### Executive Summary\nBriefly describe the problem, opportunity, and value of automating this process.\n\n### Diagnosis of Problem\nSummarize what\u2019s inefficient or costly in the current setup.\n\n### Why It\u2019s Inefficient\nList the causes (manual tasks, lack of tracking, no standardization, etc.).\n\n### Automation Roadmap\nStructure by phase:\n- **MVP / Quick Wins (1\u20132 weeks)**  \n- **Scalable Solution (4\u20138 weeks)**  \n- **Long-Term Improvements (3\u20136+ months)**\n\n### Estimated ROI\nTable or summary showing time saved, cost reduction, and ROI/payback.\n\n### Next Steps\nShort list of recommended actions or priorities.\n\n### CTA \u2014 Discovery Call\nWant this automation blueprint tailored and implemented for your business?  \n[**Book your 30-min Automation Strategy Call \u2192**]([Your Calendly Link])\n\n---\n\n## Style & Voice\n- Structured, clear, and result-driven.  \n- Avoid buzzwords \u2014 sound like a seasoned consultant, not a salesperson.  \n- Prioritize clarity, speed, and ROI communication.  \n- Every paragraph should move the reader closer to:  \n  \u201cThis is worth automating \u2014 and [Your Company] can do it.\u201d\n"
},
"promptType": "define"
},
"typeVersion": 2.2
},
{
"id": "4a0b9ca8-858c-4dde-ac05-679ddb62bd58",
"name": "Deliver Roadmap Email",
"type": "n8n-nodes-base.emailSend",
"position": [
250,
380
],
"webhookId": "f32f3993-2e49-4b2d-8e54-3954a03f6aa9",
"parameters": {
"html": "={{ $json.output }}",
"options": {
"appendAttribution": false
},
"subject": "Your roadmap is ready!",
"toEmail": "={{ $('Upsert Client Record').item.json.Email }}",
"fromEmail": "[Your Company] <[YOUR_EMAIL]>"
},
"credentials": {
"smtp": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 2.1
},
{
"id": "cc365b08-f5bd-4fda-b830-5d905a6181ee",
"name": "Upsert Client Record",
"type": "n8n-nodes-base.dataTable",
"position": [
320,
180
],
"parameters": {
"columns": {
"value": {
"Tag": "New",
"Name": "={{ $json.body.name }}",
"Email": "={{ $json.body.email }}",
"EmailSent": false,
"Challenges": "={{ $json.body.primaryGoal }}",
"CompanyURL": "={{ $json.body.companyUrl }}",
"CompanyType": "={{ $json.body.companyType }}"
},
"schema": [
{
"id": "Name",
"type": "string",
"display": true,
"removed": false,
"readOnly": false,
"required": false,
"displayName": "Name",
"defaultMatch": false
},
{
"id": "Email",
"type": "string",
"display": true,
"removed": false,
"readOnly": false,
"required": false,
"displayName": "Email",
"defaultMatch": false
},
{
"id": "CompanyType",
"type": "string",
"display": true,
"removed": false,
"readOnly": false,
"required": false,
"displayName": "CompanyType",
"defaultMatch": false
},
{
"id": "CompanyURL",
"type": "string",
"display": true,
"removed": false,
"readOnly": false,
"required": false,
"displayName": "CompanyURL",
"defaultMatch": false
},
{
"id": "Challenges",
"type": "string",
"display": true,
"removed": false,
"readOnly": false,
"required": false,
"displayName": "Challenges",
"defaultMatch": false
},
{
"id": "EmailSent",
"type": "boolean",
"display": true,
"removed": false,
"readOnly": false,
"required": false,
"displayName": "EmailSent",
"defaultMatch": false
},
{
"id": "Tag",
"type": "string",
"display": true,
"removed": false,
"readOnly": false,
"required": false,
"displayName": "Tag",
"defaultMatch": false
}
],
"mappingMode": "defineBelow",
"matchingColumns": [],
"attemptToConvertTypes": false,
"convertFieldsToString": false
},
"filters": {
"conditions": [
{
"keyName": "Email",
"keyValue": "={{ $json.body.email }}"
}
]
},
"operation": "upsert",
"dataTableId": {
"__rl": true,
"mode": "list",
"value": "[YOUR_ID]",
"cachedResultUrl": "/projects/[YOUR_ID]/datatables/[YOUR_ID]",
"cachedResultName": "Lead Magnet"
}
},
"typeVersion": 1
},
{
"id": "32b008e6-a03b-4e44-b9aa-aa6504a02980",
"name": "Mark Delivery Status",
"type": "n8n-nodes-base.dataTable",
"position": [
0,
350
],
"parameters": {
"columns": {
"value": {
"Tag": "Delivered",
"EmailSent": true
},
"schema": [
{
"id": "Name",
"type": "string",
"display": true,
"removed": true,
"readOnly": false,
"required": false,
"displayName": "Name",
"defaultMatch": false
},
{
"id": "Email",
"type": "string",
"display": true,
"removed": true,
"readOnly": false,
"required": false,
"displayName": "Email",
"defaultMatch": false
},
{
"id": "CompanyType",
"type": "string",
"display": true,
"removed": true,
"readOnly": false,
"required": false,
"displayName": "CompanyType",
"defaultMatch": false
},
{
"id": "CompanyURL",
"type": "string",
"display": true,
"removed": true,
"readOnly": false,
"required": false,
"displayName": "CompanyURL",
"defaultMatch": false
},
{
"id": "Challenges",
"type": "string",
"display": true,
"removed": true,
"readOnly": false,
"required": false,
"displayName": "Challenges",
"defaultMatch": false
},
{
"id": "EmailSent",
"type": "boolean",
"display": true,
"removed": false,
"readOnly": false,
"required": false,
"displayName": "EmailSent",
"defaultMatch": false
},
{
"id": "Tag",
"type": "string",
"display": true,
"removed": false,
"readOnly": false,
"required": false,
"displayName": "Tag",
"defaultMatch": false
}
],
"mappingMode": "defineBelow",
"matchingColumns": [],
"attemptToConvertTypes": false,
"convertFieldsToString": false
},
"filters": {
"conditions": [
{
"keyValue": "={{ $('Upsert Client Record').item.json.id }}"
}
]
},
"operation": "update",
"dataTableId": {
"__rl": true,
"mode": "list",
"value": "[YOUR_ID]",
"cachedResultUrl": "/projects/[YOUR_ID]/datatables/[YOUR_ID]",
"cachedResultName": "Lead Magnet"
}
},
"typeVersion": 1
},
{
"id": "54e6232d-f20c-4824-9567-72bb9381b080",
"name": "Nano Language Model",
"type": "@n8n/n8n-nodes-langchain.lmChatOpenAi",
"position": [
1060,
120
],
"parameters": {
"model": {
"__rl": true,
"mode": "list",
"value": "gpt-5-nano",
"cachedResultName": "gpt-5-nano"
},
"options": []
},
"credentials": {
"openAiApi": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 1.2
},
{
"id": "16bcece4-e570-42eb-9a26-ffd26b81cd66",
"name": "Mini Language Model",
"type": "@n8n/n8n-nodes-langchain.lmChatOpenAi",
"position": [
1040,
340
],
"parameters": {
"model": {
"__rl": true,
"mode": "list",
"value": "gpt-5-mini",
"cachedResultName": "gpt-5-mini"
},
"options": {
"timeout": 60000
}
},
"credentials": {
"openAiApi": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 1.2
}
],
"active": false,
"pinData": [],
"settings": {
"executionOrder": "v1"
},
"versionId": "",
"connections": {
"Inbound Webhook Trigger": {
"main": [
[
{
"node": "Upsert Client Record",
"type": "main",
"index": 0
}
]
]
},
"Mini Language Model": {
"ai_languageModel": [
[
{
"node": "HTML Styling Agent",
"type": "ai_languageModel",
"index": 0
}
]
]
},
"Nano Language Model": {
"ai_languageModel": [
[
{
"node": "Automation Advisor",
"type": "ai_languageModel",
"index": 0
}
]
]
},
"HTML Styling Agent": {
"main": [
[
{
"node": "Deliver Roadmap Email",
"type": "main",
"index": 0
}
]
]
},
"Automation Advisor": {
"main": [
[
{
"node": "HTML Styling Agent",
"type": "main",
"index": 0
}
]
]
},
"Mark Delivery Status": {
"main": [
[
{
"node": "Internal Email Alert",
"type": "main",
"index": 0
},
{
"node": "Telegram Alert Notice",
"type": "main",
"index": 0
}
]
]
},
"Upsert Client Record": {
"main": [
[
{
"node": "Automation Advisor",
"type": "main",
"index": 0
}
]
]
},
"Deliver Roadmap Email": {
"main": [
[
{
"node": "Mark Delivery Status",
"type": "main",
"index": 0
}
]
]
}
},
"id": ""
}