Set of 5 n8n workflows: how to stop drowning in leads, CRM, and reports

Why routine eats up your hours

If you run a micro-agency or work as a content producer, this picture is familiar: leads come in from a website form, Telegram, Instagram Direct, and email. You manually move them into a spreadsheet, then into a CRM, clarify the budget and the task, create a deal, and at the end of the month put together a client report. Each step on its own takes minutes, but together — dozens of hours a week.

The problem isn't that you work slowly. The problem is that the processes aren't connected to each other. Data lives in different services, and you play the role of the "human integration." That's exactly the role that automation on n8n takes over.

What n8n is and why it suits agencies

n8n is a platform for visually building workflows. You connect nodes into a chain: trigger → processing → action. A workflow can receive data from a webhook, call an API, filter, enrich, and send the result to the right service.

For a micro-agency, three properties of n8n matter:

• Flexibility. You can connect forms, Telegram, email, HubSpot, Google Sheets, and internal APIs into a single flow.
• Transparency. The logic is visible on the canvas, and it's easy to edit without a developer.
• Repeatability. A scenario configured once runs on a schedule or on an event.

Next — a practical scheme of five workflows that cover the lead's journey from first touch to client report.

Workflow 1. Capturing leads from all channels

The goal is to collect requests in one place and not lose a single one.

How to build it:

1. Create a separate workflow in n8n with a Webhook trigger. This will be the "front door" for website forms.

2. For Telegram use the Telegram Trigger, for email — the IMAP Email Trigger, for Instagram — a webhook via an intermediary service or API.

3. Bring all incoming data to a single structure: name, contact, source, request text, date.

4. Add a Set node to normalize fields and a Remove Duplicates node so you don't multiply duplicates if a person wrote in two channels.

As a result, you get a single stream of requests that can then be qualified and sent to the CRM.

Workflow 2. Lead qualification

The goal is to separate target inquiries from spam and non-target ones, so the manager spends time only on relevant requests.

Qualification logic may include:

• checking required fields (contact, budget, task);
• filtering by stop words and obvious spam;
• scoring by simple rules: there's a budget + there's a deadline + a suitable service = hot lead;
• an automatic clarifying question if data is missing.

In n8n this is implemented via If, Switch, and Code nodes. For example, if the budget isn't specified in the request, the workflow sends the client a polite message asking them to clarify, and marks the request as "needs clarification." If all fields are filled in — the lead moves on, to the CRM.

Important: qualification shouldn't be a black box. Keep the logic simple and clear so it can be quickly adjusted for new services.

Workflow 3. Creating deals in HubSpot

The goal is to automatically create a deal and contact in HubSpot right after qualification.

Steps:

1. Check whether the contact exists in HubSpot by email or phone (HubSpot node → Search).

2. If the contact doesn't exist — create it (HubSpot → Create Contact).

3. Create a deal (HubSpot → Create Deal) and link it to the contact.

4. Fill in the deal properties: source, stage, amount (if known), owner.

5. Write the deal ID back to the original spreadsheet or database to preserve the link.

Such a workflow removes manual data copying and reduces the risk that a request "gets stuck" in a chat. The manager sees the deal in the pipeline from day one.

Workflow 4. Generating client reports

The goal is to automatically compile a report for a project or client and send it on a schedule.

What the workflow does:

• via a Schedule Trigger it runs once a week or month;
• pulls data from HubSpot, Google Sheets, ad accounts, or an internal database;
• builds a summary: how many leads, how many deals, which stages, which tasks were completed;
• assembles the report in Google Docs, PDF, or an HTML email;
• sends it to the client via Email or Telegram.

The key point is the template. Describe the report structure once, and from then on n8n will insert current data into it. This saves time and removes the risk of forgetting to send the report.

Workflow 5. Notification system

The goal is to keep the team informed about events without manual reminders.

Typical notifications:

• a new hot lead — to the sales department chat;
• a deal moved to a new stage — to the responsible manager;
• the client hasn't responded for N days — a reminder;
• the report has been sent — a note in the CRM;
• an error in the workflow — an alert to the administrator.

In n8n, notifications are built via Telegram, Slack, Email, or Webhook. The main thing is not to turn this into noise. Set priorities: critical events go to a separate channel, the rest — into a digest once a day.

How to tie everything into one kit

The five workflows work like a conveyor:

1. Capture collects requests from all channels.

2. Qualification filters out non-target ones and clarifies data.

3. HubSpot creates the contact and deal.

4. Reports inform the client.

5. Notifications keep the team on their toes.

Each workflow can be run separately, but together they cover the full cycle. If you don't want to build this from scratch, take a look at the ready-made automation bundle for a micro-agency: lead generation, qualification, CRM, and reporting on n8n — these scenarios are already built and described there.

What to consider during implementation

Start with one channel. Don't connect all sources at once. Set up capture from one form, check how the data reaches the CRM, and only then expand.

Describe the fields in advance. The clearer the data structure (name, contact, source, budget, task), the easier it is to build qualification and reports.

Keep logs. n8n has an execution history. It helps you understand where the workflow stumbles.

Don't automate chaos. If a process isn't described, automation will simply speed up the disorder. First — a simple scheme on paper, then — the nodes.

Test on test data. Run the workflow with a fake request to make sure the deal is created, the report is generated, and the notification arrives.

How much time this frees up

The exact numbers depend on the volume of requests and the number of clients. But the logic is simple: every manual step — transferring data, creating a deal, compiling a report, a reminder — takes minutes. When n8n performs these steps, you stop spending your attention on them. The freed-up hours go to sales, working with clients, and growing the agency.

If, besides leads and CRM, you have content tasks, take a look at the content factory for micro-agencies: competitor monitoring, rewriting, and auto-publishing on n8n — it covers another part of the routine.

Conclusion

Five workflows on n8n are not "magic," but a clear sequence: collect leads, qualify, create them in HubSpot, report to the client, notify the team. Each step is automated separately, and together they form a system that works without your constant involvement.

Start with the one workflow that hurts the most. If you want to speed things up and not build everything manually, take a look at the ready-made automation bundle for a micro-agency — there, lead generation, qualification, CRM, and reporting are already brought together into a single kit.