How I Am Automating Lead Funnels With n8n, Telegram, and Slack

Four production sites are live. Leads are coming in through contact forms, newsletter signups, and direct project inquiries. The database captures all of them.

The next question is: what happens after capture?

Without automation, the answer is: nothing, until I open the admin panel and check. That could be hours later, or a day later if I am deep in a client project. First response time is one of the highest-impact variables in lead conversion. Delayed responses lose leads.

Here is the automation layer I am building to close that gap.

The Funnel Architecture

The funnel has four stages:

1. —Capture — Lead arrives (contact form, newsletter signup, direct message)
2. —Notify — I am alerted within 5 minutes, regardless of what I am doing
3. —Qualify — Basic qualification happens automatically (which page, which service, message content)
4. —Route — High-value leads go to immediate follow-up; low-intent leads go to a nurture sequence

n8n as the Orchestration Layer

n8n is an open-source workflow automation tool. Think Zapier, but self-hostable and significantly more flexible for technical users.

The relevant n8n setup for the lead funnel:

Trigger: New Supabase row in contact_submissions n8n can poll a Supabase table or receive a webhook from a Supabase database trigger. When a new row appears, the workflow starts.

Step 1: Parse the submission Extract the name, email, message, and source page. The source page is the first qualifier — an inquiry from /services/ai-content-systems has a different intent than an inquiry from the blog.

Step 2: Score the lead A simple scoring function: Does the message mention a budget? Does it describe a specific project? Does it include a company name? Higher-scoring leads get priority routing.

Step 3: Notify via Telegram For any lead above the minimum threshold, send a Telegram message:

New lead from /services/ai-content-systems

Name: Alex Morgan
Email: alex@company.com
Score: 7/10

Message preview: "Looking for help building a content system for our
marketing team, budget around $X..."

[View in Admin] [Reply via Email]

This notification arrives within 2 minutes of the form submission. I can read it on my phone while in a meeting and decide whether to respond immediately or within the hour.

Step 4: Low-score leads to Slack Leads below the threshold (newsletter signups, vague inquiries, students) go to a Slack channel for review during a weekly admin session. They are not lost — they are just not prioritized for immediate response.

The Nurture Sequence (Planned)

Leads that do not convert immediately go into a Supabase table (nurture_queue) with a scheduled follow-up date. An n8n scheduled workflow runs daily, finds leads whose follow-up date has passed, and sends a draft email to Slack for my review before sending.

This is not yet fully built. The intent is to avoid the pattern where a strong lead gets a first response, has a good conversation, and then falls out of contact because neither party followed up explicitly.

What I Expected vs. What Is Happening

Expected: the notification workflow would surface leads I was missing. Actual: it confirmed that I was missing about 30% of contact form submissions — not because they went to spam, but because they arrived during project-focused work sessions when I did not check email for hours.

The Telegram notification has changed that. The time from submission to first response has dropped from an average of 6 hours to an average of 45 minutes.

Expected: lead scoring would be complex to calibrate. Actual: a five-variable scoring function (service page, budget mention, company mention, message length, returning visitor flag) captures the most important signal with no ML required.

The n8n Self-Hosting Note

n8n can run on a Vercel serverless function, a DigitalOcean droplet, or Railway. For this use case, Railway is the simplest: one-click deploy from the n8n template, $5/month, persistent workflow execution. For a setup this small, a VPS is not necessary.

---

Resources

• —n8n documentation — the open-source automation platform; self-hostable and significantly more flexible than Zapier for technical use cases
• —Railway — n8n template — one-click n8n deployment on Railway; $5/month, persistent, no configuration needed
• —Supabase webhooks (database triggers) — how to fire an HTTP request when a new row is inserted, which is the trigger for this entire funnel
• —Telegram bot API — sendMessage — the endpoint n8n calls to send a lead notification; supports HTML and Markdown formatting

Related Posts

• —Building a Lead and CRM System Into Your Portfolio Site — the Supabase CRM layer that n8n reads from and writes to
• —Case Study: santoshpaudel.me — A Portfolio That Runs Like a Business — the full platform the automation layer connects to
• —Your Portfolio Should Not Just Show Work — It Should Run Your Business — why this automation layer exists and what it changes

---

Want an automated lead funnel for your site? I build n8n workflows, Supabase webhooks, and Telegram notification pipelines as part of full-stack projects. See my services or get in touch.