A set of 5 n8n workflows: how to stop managing leads, deals, and reports manually

A familiar picture: leads get lost, deals get forgotten, reports get copy-pasted

You run a micro-agency or work as an info-producer. Requests come in from a website form, Telegram, Instagram, sometimes email. Each one needs to be: read, checked against a checklist, entered into the CRM, given a reminder, used to compile a client report, and have a notification sent to the team. If you do this by hand, the day turns into an endless context switcher.

The problem isn't that you work poorly. The problem is that there's no automatic bridge between the lead source and the deal in HubSpot. And while you're copying data from a chat into a spreadsheet, the client is already messaging a competitor.

The solution isn't to hire an assistant, but to build 5 connected n8n workflows: lead capture and qualification, deal creation in HubSpot, client report generation, and a notification system. Below is a practical blueprint for how to set this up step by step.

Why n8n specifically, and not "yet another service"

n8n is an open-source automation platform that you can install on your own server or use in the cloud. It can connect webhooks, CRMs, spreadsheets, messengers, and LLMs into a single scenario. For an agency, this means: you don't pay per user in a separate "builder," but instead build transparent chains that you can see and control.

Important: n8n doesn't replace your CRM and doesn't do the work for you. It removes manual operations between systems. It's precisely at the junctions — form → qualification → HubSpot → report → notification — that hours get lost.

Step 1. Capture leads from all channels into one point

First, gather incoming requests into a single n8n webhook. What this gives you: it doesn't matter where the lead came from — a Tilda form, a Telegram bot, an email, or a chat — it lands in one scenario with the same field structure.

What to set up:

• A Webhook node in n8n as the entry point. Each source sends a POST request here with fields: name, contact, source, request text, UTM tags.
• Data normalization: bring phones and emails to a single format, trim extra spaces, remove duplicates.
• Duplicate check: before creating a record, find the contact in HubSpot by email or phone. If it exists — update it rather than creating a second one.

At this stage you're already saving time: no need to manually move requests from five windows into one.

Step 2. Qualify the lead by your criteria

Next, the lead needs to be evaluated. Qualification isn't "like / don't like," but a set of rules. For example: budget, timeline, type of task, region, readiness for a call.

How to build this in n8n:

• A Filter or Switch node: passes the lead onward if it meets at least the basic conditions (for example, a budget is specified and there's a contact for reaching out).
• An AI node (optional): if the request comes in as free text, the model can extract key parameters from it — task, timeline, industry. This doesn't replace your assessment, but it structures the incoming flow.
• Status assignment: "hot," "warm," "not a target." The status is written to the contact or deal fields.

The main rule: don't overcomplicate. Qualification should filter out obvious spam and highlight those who need to be answered first. Everything else is at the manager's discretion.

Step 3. Create a deal in HubSpot automatically

Once the lead has passed qualification, n8n creates a deal in HubSpot. Here it's important to correctly link the contact, company, and deal so there are no "orphans" in the CRM.

What the workflow does:

• Creates or updates the contact in HubSpot with the fields from step 1.
• Creates a deal and links it to the contact and company.
• Sets the funnel stage depending on the qualification status.
• Records the source (UTM, channel) so you can later understand where the best leads come from.
• Sets a task for the manager: "reach out within X hours."

If you handle several clients or projects, add a "direction" field — this will simplify reporting. By the way, similar chains for agencies are collected in a ready-made automation bundle for a micro-agency: lead generation, qualification, CRM, and reporting on n8n — you don't have to build everything from scratch, you can adapt it to your processes.

Step 4. Client reports without manual copy-paste

Reports are the second time-eater. Every week or month you gather data from HubSpot, spreadsheets, and ad accounts, and manually lay out a PDF or email.

The automation looks like this:

• A scheduled trigger (Cron in n8n): once a week or month.
• Data collection: n8n pulls deals, stages, amounts, and tasks from HubSpot and other sources.
• Report generation: a template in Google Docs, Notion, or an HTML email. Substituting data per client.
• Sending: an email to the client or a message in Telegram/Slack with the finished report.

Important: the report should be clear, not an "export for the sake of an export." Add 2–3 key metrics and a short comment — for example, how many leads came in and how many made it to a deal.

Step 5. A notification system that won't let you forget

Notifications are the glue of the whole system. Without them, automation runs "into the void": the deal is created, but the manager doesn't know.

What to set up:

• An instant notification about a hot lead — to the team in Telegram or Slack.
• A reminder if a deal hasn't moved for N days.
• An alert about a stage change — so client service gets involved on time.
• A daily digest: how many new leads, how many deals in progress, what needs attention.

Notifications should be measured. If the bot messages every five minutes, people will stop reading it. Set priorities: critical — immediately, the rest — in the digest.

How to put it all together and not drown

Five workflows aren't five separate scenarios, but a conveyor:

1. Capture → 2. Qualification → 3. Deal in HubSpot → 4. Report → 5. Notifications.

Practical tips:

• Start with one channel. Don't connect all sources at once — debug on one, then scale.
• Log errors. In n8n you can set up a separate workflow that reports failures.
• Store keys in credentials, not in nodes.
• Test on real data, but with a copy of the CRM or a test account.
• Don't automate chaos. First describe the process on paper, then move it into n8n.

If you work with content and clients in parallel, part of the routine can be covered by adjacent scenarios — for example, a content factory for micro-agencies: competitor monitoring, rewriting, and auto-publishing on n8n. This isn't a mandatory step, but it's useful if, besides leads, you also manage clients' social media.

The bottom line

A set of 5 n8n workflows solves a specific task: it removes manual labor at the junction of "lead → CRM → report → notification." You stop being an operator and start managing the process. Saving 20+ hours a week isn't magic, but a consequence of dozens of small actions being performed by a scenario rather than a human.

Start with one workflow — lead capture. When you see that requests are no longer getting lost, add qualification and HubSpot. Then reports and notifications will fall into place.

Ready-made scenarios that you can adapt to yourself are collected in the automation bundle for a micro-agency. Take a look at how the workflows are structured and choose the ones that will close your bottlenecks.