How we set up n8n lead routing with Rocket.Chat
Updated: Oct 19
A new inquiry comes in through your website. It lands in a shared inbox. Everyone assumes someone else saw it. By the time anyone replies, the customer has already called someone else. If that sounds familiar, this post is for you.
Here's how we set up n8n lead routing at ScaleStack Lab. The flow takes a lead from a web form and puts it in front of the right person, on their phone, in Rocket.Chat. There's no code in this post. It covers what the flow does, the pieces involved, and what to decide before you build lead follow-up like this for yourself.
Why leads slip through the cracks
Most small businesses don't lose leads because nobody cares. They lose them because of how the leads arrive.
One shared inbox, many owners. When a form goes to info@ and three people can see it, nobody is clearly responsible for it.
Email is noisy. A new lead sits between invoices, newsletters, and vendor updates. It's easy to scroll past.
The right person isn't the one looking. The person who handles quotes isn't the one checking the inbox. The lead waits until it gets forwarded.
After hours, nobody is checking. A lead that comes in at 6 PM can sit until whoever opens the inbox first the next morning.
None of this is a people problem. It's a routing problem. And routing is the kind of job automation handles well.
What the flow does, in plain words
In one sentence: when someone fills out the contact form, the flow sends the details straight to the right person's Rocket.Chat channel, with what they need to follow up.
Step by step:
A visitor fills out the contact form.
n8n receives the submission.
n8n looks at what the person asked about and what time it is.
Based on a few simple rules, n8n picks who should get the lead.
n8n posts a clear, readable message to that person's or team's Rocket.Chat channel.
Their phone shows a notification. They tap it and see the lead.
That's it. No one has to forward anything, and there's a clear record of each routed lead in one place.
The pieces: form, n8n, Rocket.Chat
There are three parts, and each does one job.
The form. This is where the lead starts. It can be a form on your website or a form tool you already use. What matters is that it can pass each submission along the moment it's sent, usually through a webhook (an automatic hand-off that sends each submission to another system). Our website contact form collects a name, an email address, what they need, and their consent to be contacted.
n8n. n8n is a workflow automation tool. Think of it as the dispatcher. It receives the form submission, cleans up the data, applies your routing rules, and sends the message. We run n8n self-hosted, meaning on a server you own or one we run for you, not a shared SaaS account. So routing happens on a system under your control, with fewer third-party accounts in between.
Rocket.Chat. Rocket.Chat is a team chat platform, which we also self-host. It's where the team actually sees the lead. It has desktop and mobile apps, so the notification shows up on their phone as well as their desktop.
Routing rules (by service, by time of day)
This is where n8n lead routing earns its keep. The rules don't need to be clever. They need to match how your business actually works.
By service. The form asks what the person needs. n8n reads that answer and routes the lead by service type:
Each service type goes to its matching team channel
"Something else" or a blank answer goes to a general leads channel that one named person owns
That last rule matters. A lead needs a default home, so a lead that doesn't fit a rule still has an owner.
By time of day. n8n checks the time when the lead comes in. During business hours, it goes straight to the person who handles that service. Outside business hours, it goes to a general channel that's checked first thing the next morning. The automation runs around the clock. People don't, and the flow is built around that honestly.
Keep the rules readable. We keep routing rules simple enough that anyone on the team can look at the n8n canvas (the visual workflow screen) and understand where a lead will go. If your routing takes a page of notes to explain, it's probably too complicated to maintain.
What the team sees on their phone
A good Rocket.Chat lead notification answers the obvious questions without anyone having to open another app. Ours shows:
The person's name
How to reach them
What they need, in their own words
When it came in
The message is formatted to read cleanly on a phone screen, with the most important details at the top. The team member gets a push notification from the Rocket.Chat app, taps it, and has what they need to call or reply.
Because the lead lives in a Rocket.Chat channel, we recommend replying in the thread with "I've got this one." That small habit makes it obvious who owns each lead, which fixes the shared-inbox problem from the start of this post.
What to decide before you build one
The technical part is usually the easy part. The decisions are what make small business lead follow-up automation actually work. Before you build, or before you ask someone to build it for you, settle these:
Where do your leads come from today? List every source: website form, email, phone messages, anything else. Start with the one that brings in the most.
Who owns which kind of lead? Write down each service and the person responsible. If the answer is "it depends," figure out what it depends on.
What's the default? Decide who gets a lead that doesn't fit any rule.
What happens after hours? Decide where after-hours leads go and who looks at them first the next business day.
What does the person need to see? Pick the fields that let someone follow up without digging.
How will you know it's working? Send test leads through every path before going live, and check them again whenever you change the form or the team.
Who keeps it running? Self-hosted tools need updates and backups. Decide whether that's you, someone on staff, or a provider.
Get these answers down on one page and the build itself becomes straightforward. See how we work with clients, from first call to running it.
Want help setting this up?
ScaleStack Lab is an Arizona IT business. We implement and run self-hosted messaging and automation for small businesses, in the cloud or on hardware at your location. We use Rocket.Chat, n8n, Skilled AI Agents, and other advanced tools that fit your business. n8n lead routing is one of the simplest places to start. If your leads are sitting in an inbox waiting for someone to notice, contact us and we'll talk through what a flow like this would look like for you.
Comments