Module 1: What n8n Is and Why It Matters
05. Real-World Use Cases: Automation in Action
Capsule overview
You already understand what automation is, you already compared tools, you already master the 7 key concepts. But concepts without context are like having a map without knowing where you want to go. This lesson gives you the destination: 16 real use cases, organized by business area, that show exactly how automation solves concrete problems you probably have today.
Each case follows the same pattern: the problem (what you do manually), the automated workflow (using the vocabulary from lesson 04), and the measurable impact (time saved, errors eliminated, money recovered). These aren't theoretical examples — they're scenarios that thousands of entrepreneurs, freelancers, and small teams implement with n8n every day. And you're going to read them with a detective's eyes: looking for which ones resemble YOUR situation.
By the end of this lesson, you'll have two things: a list of inspiration for your first automations, and a framework to identify automation opportunities in any business process. That connects directly with lesson 08, where you'll map 3 of your own processes ready to build in n8n.
How to Read the Use Cases
Don't read this lesson like a catalog. Read it like a mirror. Each case is designed to make you ask: "Do I do something similar?" They all follow the same structure:
- The Problem — what happens today manually, how long it takes, what goes wrong
- The Workflow — what the automated solution looks like, using the concepts from lesson 04 (trigger, nodes, actions, connections)
- The Impact — concrete numbers: hours saved, errors eliminated, speed gained
As you read, keep a note sheet handy. Every time a case makes you think "I do something similar," write it down. Those notes are the input for lesson 08.
An important clarification: in the diagrams you'll see tool names (Google Sheets, Slack, Gmail). You don't need to use exactly those tools. If you use Notion instead of Sheets, or WhatsApp instead of Slack, the workflow is the same — only the node changes.
Marketing
Case 1: Automatic Lead Capture
The Problem
You have a form on your website where people request information. Every time someone fills it out, you receive a notification email. You open the email, copy the name, email, and message. You open your leads spreadsheet, find the last empty row, paste the data. Then you open Gmail, draft a welcome email, copy the lead's name to personalize it, and send it. Finally, you notify your sales team on Slack that there's a new lead.
Total time: 15-20 minutes per lead. With 5 leads a day, that's 90 minutes a day doing copy-paste. And if you're in a meeting when a lead comes in, you forget. The lead waits hours — or days — before getting a response. By the time you reply, they've already requested information from your competition.
The Workflow
WORKFLOW: "Automatic lead capture"
┌─────────────┐ ┌──────────────┐ ┌──────────────┐
│ TRIGGER │ │ NODE 2 │ │ NODE 3 │
│ Web form │───▶│ Save to │───▶│ Send welcome │
│ submitted │ │ Google Sheets│ │ email │
└─────────────┘ └──────────────┘ └──────────────┘
│
▼
┌──────────────┐
│ NODE 4 │
│ Notify on │
│ Slack │
└──────────────┘
- Trigger: Web form submitted (webhook)
- Node 2 (action): Add row in Google Sheets with name, email, message
- Node 3 (action): Send a personalized welcome email with the lead's name
- Node 4 (action): Send a message to the #sales channel on Slack with the lead's data
- Credentials: Google Sheets, Gmail, Slack
- Estimated executions: 5 leads/day × 30 days = 150/month
The Impact
- ⏱️ From 90 min/day to 0 minutes of manual work
- 📩 Response time: from hours to seconds
- 🚫 Forgotten leads: from 2-3 per week to zero
- 📊 Database always up to date, with no copy-paste errors
Case 2: Social Media Publishing
The Problem
You know you should post on social media consistently. But every time you try, the same thing happens: you open Instagram, think about what to post, draft something, look for an image, publish. Then you do the same on LinkedIn. And on Twitter. By the time you finish, an hour has passed. You do it three days in a row, and on the fourth you forget. The following week you post once. The consistency falls apart.
You have a spreadsheet with content ideas, but opening it and running the publication manually is enough of a barrier that you don't do it.
The Workflow
- Trigger: Scheduled time (Monday, Wednesday, Friday at 9am)
- Node 2 (action): Read the next row from Google Sheets (your content bank)
- Node 3 (action): Publish on LinkedIn
- Node 4 (action): Publish on Twitter
- Node 5 (action): Mark the row as "published" in Google Sheets
- Credentials: Google Sheets, LinkedIn, Twitter
The Impact
- ⏱️ From 5 hours/week to 1 hour/week (only preparing the content in batches)
- 📅 Consistent publishing: you never forget again
- 📈 Organic reach grows because the algorithms reward consistency
Case 3: Weekly Metrics Report
The Problem
Every Monday morning, your boss (or you yourself if you're the business owner) wants to know how the week went: how many visits the website had, how much was spent on advertising, how many new followers arrived. You open Google Analytics, copy the numbers. You open Meta Ads Manager, copy other numbers. You open Instagram Insights, more numbers. You paste everything into a presentation or an email, format it, and send it. Two hours minimum. Every Monday.
And the worst part: if you focus on something else urgent on Monday, the report comes out Tuesday. Or it never comes out. And nobody makes data-based decisions that week.
The Workflow
WORKFLOW: "Weekly marketing report"
┌─────────────┐ ┌──────────────┐ ┌──────────────┐
│ TRIGGER │ │ NODE 2 │ │ NODE 3 │
│ Schedule │───▶│ Get data │───▶│ Get data │
│ Monday 8am │ │ Google │ │ Meta Ads │
│ │ │ Analytics │ │ │
└─────────────┘ └──────────────┘ └──────────────┘
│
▼
┌──────────────┐ ┌──────────────┐
│ NODE 5 │ │ NODE 4 │
│ Send email │◀───│ Compile into │
│ to the team │ │ Google Sheets│
└──────────────┘ └──────────────┘
- Trigger: Scheduled time (Monday at 8:00am)
- Node 2 (action): Query Google Analytics (visits, sessions, page views)
- Node 3 (action): Query Meta Ads (spend, impressions, clicks)
- Node 4 (action): Compile data into Google Sheets ("Weekly Report" tab)
- Node 5 (action): Send an email with the summary to the team
- Credentials: Google Analytics, Meta Ads, Google Sheets, Gmail
The Impact
- ⏱️ From 2 hours every Monday to 0 minutes
- 📊 The report always arrives at 8am, no exceptions
- 🎯 Data-based decisions every week, not just when "there's time"
Case 4: Automatic Email Segmentation
The Problem
You have a list of email subscribers. Some have already bought from you and are customers. Others only subscribed but never bought. Treating them the same is a mistake: to the customer you want to offer complementary products; to the prospect you want to convince them to buy for the first time. But segmenting manually — reviewing each subscriber, checking if they bought, tagging them — takes hours and you always end up with unclassified subscribers piling up.
The Workflow
- Trigger: Webhook (a new subscriber signs up)
- Node 2 (action): Query purchase history in the database
- Node 3 (IF decision): Do they have previous purchases?
- YES → Node 4a: Tag as "customer" and add to the cross-selling sequence
- NO → Node 4b: Tag as "prospect" and add to the welcome sequence
- Credentials: Email platform, database or CRM
The Impact
- ⏱️ Instant segmentation vs. weekly manual review
- 📈 Better open rate because each person receives relevant content
- 💰 More conversions: prospects get nurturing, customers get upselling
Sales
Case 5: Automatic Proposal Follow-up
The Problem
You send a business proposal to a prospect. Three days later, you should follow up. But you have 15 open proposals, meetings all day, and the reality is that you don't follow up with half of them. The prospect doesn't respond, you don't insist, and the sale is lost. Not because your proposal was bad, but because nobody followed the thread.
Studies say that 80% of sales require at least 5 follow-up interactions. Most salespeople give up after 1.
The Workflow
- Trigger: Deal marked as "proposal sent" in CRM
- Node 2 (action): Wait 3 days (wait node)
- Node 3 (IF decision): Did the prospect reply to the email?
- YES → End of the workflow
- NO → Node 4: Send a friendly follow-up email
- Node 5 (action): Wait 5 more days
- Node 6 (IF decision): Was there a reply?
- YES → End
- NO → Node 7: Notify the sales manager for personal intervention
- Credentials: CRM, Gmail, Slack
The Impact
- 🔄 100% of proposals get follow-up (vs. ~50% manual)
- ⏱️ 0 time spent remembering who to follow up with
- 💰 A 20-35% increase in close rate just from consistency in follow-up
Case 6: Lead Scoring
The Problem
You get 30 leads a month. Some are large companies with a real budget. Others are people who are "just looking." If you treat them all the same — you dedicate the same time to them, you call them with the same urgency — you waste hours attending to leads who are never going to buy, while the good leads wait.
You need a system to separate hot leads from cold leads. But doing it manually — opening each lead, researching the company, deciding the priority — takes 10 minutes per lead.
The Workflow
- Trigger: New lead registered in CRM
- Node 2 (action): Get the lead's data (company, role, indicated budget)
- Node 3 (action): Assign a score based on rules:
- Company with more than 50 employees → +30 points
- Indicated budget greater than $5,000 → +25 points
- Decision-maker role (Director, CEO, Manager) → +25 points
- Came through a referral → +20 points
- Node 4 (IF decision): Score greater than 70?
- YES → Assign to a senior salesperson, notify immediately
- NO → Add to the email nurturing sequence
- Credentials: CRM, Gmail, Slack
The Impact
- 🎯 Salespeople dedicate their time to leads with a higher probability of closing
- ⏱️ From 10 min/lead to qualify to instant qualification
- 💰 Hot leads get attention in minutes, not days
Case 7: Automatic Proposal Creation
The Problem
Every time a deal advances to the "proposal" stage in your CRM, someone has to create the document: open the template, copy the customer's data, fill in services and prices, check that there are no errors (last month you sent a proposal with another customer's name), export to PDF, and send by email. All of that takes 30-45 minutes. With 10 proposals a week, that's 6-7 hours a week just on paperwork.
The Workflow
- Trigger: Deal moved to the "Proposal" stage in CRM
- Node 2 (action): Get the customer's data from the CRM (name, company, services, prices)
- Node 3 (action): Generate the proposal from a template in Google Docs (replace dynamic fields)
- Node 4 (action): Export to PDF
- Node 5 (action): Send by email to the customer with a personalized message
- Node 6 (action): Notify the salesperson that the proposal was sent
- Credentials: CRM, Google Docs, Gmail, Slack
The Impact
- ⏱️ From 30-45 min per proposal to instant generation
- 🚫 Zero copy-paste errors (goodbye to sending the wrong name)
- 📄 Professional and consistent formatting across all proposals
Case 8: Real-Time Sales Pipeline
The Problem
The sales manager needs to know how many deals are open, what stage they're in, and how much the total pipeline is worth. But to know that, they have to ask each salesperson, or open the CRM and navigate deal by deal. In the weekly meeting, the information is already 3 days behind. Nobody knows for sure how many sales are going to close this month.
The Workflow
- Trigger: Any stage change in the CRM
- Node 2 (action): Update the dashboard sheet in Google Sheets (total pipeline, deals by stage)
- Node 3 (IF decision): Is it a deal over $10,000 that just closed?
- YES → Node 4: Notify the CEO on Slack with the deal's details
- NO → End
- Credentials: CRM, Google Sheets, Slack
The Impact
- 📊 Real-time visibility of the pipeline, without asking anyone
- 🔔 The CEO finds out about important sales instantly
- 🎯 More productive meetings: current data, not from 3 days ago
Operations
Case 9: Employee Onboarding
The Problem
Hiring someone new involves 15 manual steps that involve 4 departments. HR creates the record. IT has to create the email account, grant access to the tools, request equipment. The direct manager has to add the person to the team's Slack channel, send them the welcome document, schedule the orientation session. Administration has to add them to payroll.
All of these steps are done by email: "Hey, did you already create the email for María?" — "Oh, no, I forgot." The new employee arrives on Monday and doesn't have email, doesn't have a computer, and nobody notified the team.
The Workflow
- Trigger: New employee record in the HR system
- Node 2 (action): Create a corporate email account
- Node 3 (action): Add to the relevant Slack channels
- Node 4 (action): Send a welcome email with documents and a first-day guide
- Node 5 (action): Create an orientation event in Google Calendar
- Node 6 (action): Notify IT to prepare equipment
- Node 7 (action): Add data to the payroll system
- Credentials: HR system, Google Workspace, Slack, Google Calendar
The Impact
- ⏱️ From 2-3 hours of coordination between departments to automatic execution
- 🚫 Zero forgotten steps: all 15 steps always run
- 😊 The new employee arrives on Monday and EVERYTHING is ready
Case 10: Inventory Monitoring
The Problem
You sell physical products. You have an inventory in a spreadsheet (or in your point-of-sale system). When a product drops below a certain quantity, you should order more from the supplier. But nobody checks the inventory every day. One day you realize that your star product ran out 3 days ago and you didn't know. You lose sales, you lose customers, and the supplier takes a week to deliver.
The Workflow
- Trigger: Scheduled time (every day at 7am)
- Node 2 (action): Read inventory levels from the database or Google Sheets
- Node 3 (IF decision): Does any product have fewer than 10 units?
- YES → Node 4: Create an automatic purchase order
- YES → Node 5: Send an email to the supplier with the order
- YES → Node 6: Notify the operations manager on Slack
- NO → End (everything is fine)
- Credentials: Google Sheets or inventory system, Gmail, Slack
The Impact
- 🚫 You never run out of stock without noticing again
- ⏱️ Supplier orders generate themselves, without anyone having to remember
- 💰 Fewer lost sales due to lack of inventory
Case 11: Invoice Processing
The Problem
Every week you receive 15-20 supplier invoices by email. You open them one by one, extract the amount, the due date, the concept, and record it in your accounting system. Then you schedule the payment. Then you send confirmation to the supplier. It's tedious work, prone to errors (was that amount $1,500 or $15,000?), and if you miss an invoice, you pay late and lose early-payment discounts.
The Workflow
- Trigger: Email received with "invoice" in the subject (email trigger)
- Node 2 (action): Extract data from the email or the attachment (amount, date, supplier)
- Node 3 (action): Record in the accounting system or Google Sheets
- Node 4 (action): Schedule the payment date
- Node 5 (action): Send a receipt confirmation to the supplier
- Credentials: Gmail, Google Sheets or accounting system
The Impact
- ⏱️ From 3-4 hours/week processing invoices to minutes
- 🚫 Zero forgotten or late-paid invoices
- 📊 Accounting records always up to date
Case 12: Incident Reporting
The Problem
A customer has a problem and fills out your support form. The form arrives as an email, someone copies it into a "tickets" spreadsheet, decides who should handle it, and sends a confirmation to the customer. If the team is busy, the ticket gets lost. The customer doesn't receive a confirmation, gets frustrated, and writes again — now angry.
The Workflow
- Trigger: Support form submitted (webhook)
- Node 2 (action): Create a ticket in Google Sheets with a case number, date, customer data
- Node 3 (action): Assign to the corresponding team based on the type of incident
- Node 4 (action): Send a confirmation email to the customer ("We received your case #1234")
- Node 5 (action): Wait 24 hours
- Node 6 (IF decision): Is the ticket still open?
- YES → Node 7: Escalate to the service manager
- NO → End
- Credentials: Google Sheets, Gmail, Slack
The Impact
- 📩 The customer receives confirmation in seconds, not hours
- 🔔 Automatic escalation if nobody resolves it within 24 hours
- 📊 Complete record of all incidents for pattern analysis
Freelancers
Case 13: Project Management
The Problem
You're a freelancer and you work with 4-5 clients at the same time. Each new project requires: creating a folder in Google Drive, creating a board in Trello with the stages, sending a kickoff email to the client, and scheduling the first weekly check-in. Manually it takes 30-45 minutes per project. And sometimes you forget a step — the folder exists but you never sent the kickoff, or the check-in was never scheduled and the project starts off disorganized.
The Workflow
- Trigger: New project created in your management tool (or a manual form)
- Node 2 (action): Create a folder in Google Drive with subfolders (Briefing, Deliverables, Feedback)
- Node 3 (action): Create a board in Trello with predefined lists (To do, In progress, Review, Done)
- Node 4 (action): Send a kickoff email to the client with the timeline and next steps
- Node 5 (action): Create a recurring event in Google Calendar (weekly check-in)
- Credentials: Google Drive, Trello, Gmail, Google Calendar
The Impact
- ⏱️ From 30-45 minutes per new project to instant setup
- 🚫 Zero forgotten steps: every project starts complete
- 🎯 Professional impression from day 1 with the client
Case 14: Automatic Invoicing
The Problem
You finish a project. You should invoice immediately, but you're busy with other projects and 5 days go by. You create the invoice manually, you send it, but the client doesn't pay. You should send a reminder at 15 days — you don't do it because you forget. At 30 days you remember, but now it's awkward. The cash flow of your freelance business suffers.
The Workflow
WORKFLOW: "Automatic invoicing and collection"
┌─────────────┐ ┌──────────────┐ ┌──────────────┐
│ TRIGGER │ │ NODE 2 │ │ NODE 3 │
│ Project │───▶│ Generate │───▶│ Send │
│ marked │ │ invoice │ │ invoice by │
│ "complete" │ │ from │ │ email │
│ │ │ template │ │ │
└─────────────┘ └──────────────┘ └──────────────┘
│
▼
┌──────────────┐
│ NODE 4 │
│ Wait │
│ 15 days │
└──────────────┘
│
▼
┌──────────────┐
│ NODE 5 │
│ IF: Paid? │
└──────────────┘
│ │
YES NO
│ │
▼ ▼
┌──────┐ ┌──────────┐
│ END │ │ Send │
│ │ │ friendly │
└──────┘ │ reminder │
└──────────┘
│
▼
┌──────────┐
│ Wait │
│ 15 more │
│ days │
└──────────┘
│
▼
┌──────────┐
│ IF: Paid │
│ now? │
└──────────┘
│ │
YES NO
│ │
▼ ▼
┌──────┐ ┌──────────┐
│ END │ │ Urgent │
│ │ │ reminder │
└──────┘ └──────────┘
- Trigger: Project marked as "completed" in the management tool
- Node 2 (action): Generate an invoice from a template with the client's data and services
- Node 3 (action): Send the invoice by email
- Node 4 (action): Wait 15 days
- Node 5 (IF decision): Was the payment recorded?
- YES → End
- NO → Node 6: Send a friendly reminder
- Node 7 (action): Wait 15 more days
- Node 8 (IF decision): Was the payment recorded now?
- YES → End
- NO → Node 9: Send an urgent reminder
- Credentials: Management tool, Google Docs, Gmail
The Impact
- 💰 Immediate invoicing: you get paid the same day, not weeks later
- 🔄 Automatic collection follow-up: you're never embarrassed to ask for payment again
- 📊 Predictable and professional cash flow
Case 15: Content Calendar
The Problem
You want to position yourself as an expert by publishing weekly content. You have a bank of topics in a spreadsheet, but the distance between "I have an idea" and "I published the article" has too many manual steps. Every week you say "this week I really will publish" and every week it slips by without publishing.
The Workflow
- Trigger: Scheduled time (Monday at 8am)
- Node 2 (action): Read the next pending topic from your content bank in Google Sheets
- Node 3 (action): Create a draft in Google Docs from a template with the topic
- Node 4 (action): Send an email with the draft for review (to yourself or an editor)
- Node 5 (action): Mark the topic as "in progress" in Google Sheets
- Credentials: Google Sheets, Google Docs, Gmail
The Impact
- ⏱️ Eliminates the "I don't know where to start this week" barrier
- 📅 A system that pushes you to create content without depending on your motivation
- 📈 Consistent publishing = real audience growth
Case 16: Client Feedback Collection
The Problem
You deliver a project and move on to the next one. You never ask for feedback — not because you don't care, but because you forget. Result: you have no testimonials for your portfolio, you don't know what to improve, and happy clients never refer you because you never asked.
The Workflow
- Trigger: Project marked as "delivered"
- Node 2 (action): Wait 7 days (give the client time to use the deliverable)
- Node 3 (action): Send a feedback form by email
- Node 4 (action): Wait for a response (5 days)
- Node 5 (IF decision): Did the client respond?
- NO → Send a friendly reminder and finish
- YES → Evaluate the rating
- Node 6 (IF decision): Rating lower than 4/5?
- YES → Alert for personal follow-up (something didn't go well)
- NO → Send an email requesting a public testimonial
- Credentials: Management tool, Gmail, Google Forms
The Impact
- 📝 100% of projects get a feedback request (vs. ~10% manual)
- ⭐ Testimonials that accumulate automatically for your portfolio
- 🔍 Early alerts when a client isn't satisfied
Common Pattern: They All Follow the Same Structure
Did you notice something? The 16 use cases — whether they're marketing, sales, operations, or freelance — follow the same fundamental pattern:
TRIGGER → PROCESS → DECISION (optional) → ACTION → NOTIFICATION
"When" "What "Which path "Do "Notify
data to take?" something someone"
do I need?" concrete"
The vocabulary from lesson 04 applies to ALL of them. There's always a trigger that starts things. There are always nodes that run actions. Sometimes there are decisions (IF node) that create different paths. And there are always connections that determine the order.
Once you understand how to build ONE workflow in n8n, you'll be able to build any of these 16. And the ones that are unique to your business will also follow the same pattern.
ANY AUTOMATION:
┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐
│ TRIGGER │───▶│ PROCESS │───▶│ DECIDE │───▶│ ACT │
│ (when) │ │ (data) │ │ (IF/ELSE)│ │ (do) │
└──────────┘ └──────────┘ └──────────┘ └──────────┘
│
▼
┌──────────┐
│ NOTIFY │
│ (alert) │
└──────────┘
The next time you find yourself doing something repetitive, ask yourself: "Can I identify the trigger, the steps, and the final action?" If the answer is yes, you have an automation candidate.
Your Turn: Identify Your Cases
Now it's your turn. Think about your work, your business, your day-to-day. Ask yourself 4 questions:
1. What do I do more than 3 times a week that's repetitive? If you do the same thing over and over, with the same steps, it's a perfect candidate.
2. Where do I lose data or forget steps? If a lead ever went unanswered or a payment was delayed because you forgot to follow up — that's solved with automation.
3. What takes me more than 15 minutes but could be instant? Generating reports, creating documents from a template, notifying several people. If the process is predictable, it doesn't need your time.
4. Where do I need to connect 2 or more tools? Every time you move information between tools manually, there's an automation opportunity.
Write down at least 3 processes you identified. You'll use them in lesson 08.
Connection with the Mini-Project
In lesson 08, the module mini-project will ask you to map 3 business processes using the format from lesson 04 (trigger, nodes, actions, credentials). The 16 use cases you just read are your inspiration bank.
You don't need to copy any of them literally. Use the ones that most resemble your reality as a starting point:
- If you're a marketer → cases 1-4
- If you're in sales → cases 5-8
- If you handle operations → cases 9-12
- If you're a freelancer → cases 13-16
Adapt them to your specific tools and describe them in your own words. The exercise in lesson 08 will be much easier because you already saw 16 complete examples.
Exercises
Exercise 1: Identify Trigger and Actions (Easy)
For each of the following cases, identify: the type of trigger (manual, scheduled, or event), the main actions, and the necessary credentials.
Case A: Weekly metrics report (Case 3) Case B: Automatic lead scoring (Case 6) Case C: Client feedback collection (Case 16)
See solution
Case A: Weekly metrics report
- Trigger: Scheduled (runs every Monday at 8am)
- Actions: Query Google Analytics, query Meta Ads, compile into Google Sheets, send email
- Credentials: Google Analytics, Meta Ads, Google Sheets, Gmail
Case B: Automatic lead scoring
- Trigger: Event (new lead registered in CRM)
- Actions: Get the lead's data, calculate the score, assign to a salesperson or to a nurturing sequence
- Credentials: CRM, Gmail, Slack
Case C: Client feedback collection
- Trigger: Event (project marked as "delivered")
- Actions: Wait 7 days, send a form, evaluate the response, request a testimonial or alert for follow-up
- Credentials: Management tool, Gmail, Google Forms
Exercise 2: Your Own Use Case (Medium)
Write your own use case following this structure:
CASE NAME: _______________
THE PROBLEM:
What do you do manually today?
How long does it take?
What goes wrong when you do it manually?
THE WORKFLOW:
- Trigger: _______________
- Node 2: _______________
- Node 3: _______________
- (add as many as you need)
- Credentials: _______________
THE IMPACT:
- Time saved: _______________
- Errors eliminated: _______________
- Other benefit: _______________
See example solution
CASE NAME: Customer payment tracking
THE PROBLEM:
Every month I manually review my customer spreadsheet to see
who has paid and who hasn't. Then I write individual emails to those
who haven't paid. It takes ~45 minutes each month. Sometimes I miss
customers and I realize weeks later.
THE WORKFLOW:
- Trigger: Scheduled (day 5 of each month)
- Node 2 (action): Read Google Sheets with payment status
- Node 3 (IF decision): Did the customer pay this month?
- YES → End
- NO → Node 4
- Node 4 (action): Send a personalized reminder email
- Node 5 (action): Notify me on Slack with a list of unpaid customers
- Credentials: Google Sheets, Gmail, Slack
THE IMPACT:
- Time saved: 45 min/month → 0
- Errors eliminated: No more forgotten customers
- Other benefit: Faster collection, better cash flow
The important thing is that you can describe a real process using the format of trigger, nodes, actions, and credentials.
Exercise 3: Prioritize (Medium)
Imagine you identified these 5 possible automations. Rank them from 1 (do first) to 5 (do last) considering three factors: time saved per week, difficulty of implementation, and impact on the business.
| Automation | Time it takes manually | Frequency | Impact if it fails |
|---|---|---|---|
| A. Post on social media | 1 hour | 3x/week | Low |
| B. Lead follow-up | 30 min | Daily | High |
| C. Monthly expense report | 3 hours | 1x/month | Medium |
| D. Send invoices to clients | 45 min | 4x/month | High |
| E. Weekly file backup | 15 min | 1x/week | Low |
See solution
Recommended prioritization:
| Priority | Automation | Why |
|---|---|---|
| 1 | B. Lead follow-up | Highest total time (30 min × 20 days = 10 hrs/month) + high impact (lost sales if it fails) |
| 2 | D. Send invoices | High impact on cash flow + costly errors if forgotten |
| 3 | A. Post on social media | Good time savings (3 hrs/week) + consistency is key for growth |
| 4 | C. Expense report | 3 hours saved but only 1x/month = low volume |
| 5 | E. File backup | Little time and low immediate impact (though important in the long term) |
The framework to prioritize:
- Calculate the total monthly time saved (frequency × duration)
- Evaluate the impact if the process fails (do you lose money, customers, data?)
- Start with what saves the most time AND has the highest impact
Exercise 4: Estimated ROI (Hard)
Choose your best automation candidate (from exercise 2, or any of the 16 cases). Calculate the estimated return on investment using this formula:
ROI CALCULATION FOR AN AUTOMATION
Step 1: Time saved per week
___ minutes × ___ times per week = ___ minutes/week
Step 2: Time saved per year
___ minutes/week × 52 weeks = ___ minutes/year
___ minutes/year ÷ 60 = ___ hours/year
Step 3: Monetary value
___ hours/year × $___ your hourly rate = $___ annual value
Step 4: Cost of the automation
n8n Cloud Starter plan: ~$20/mo = $240/year
Step 5: ROI
($____ annual value - $240 cost) ÷ $240 cost × 100 = ___% ROI
See example solution
Example: Automating lead follow-up (Case 5)
Step 1: Time saved per week
15 minutes × 5 times per week = 75 minutes/week
Step 2: Time saved per year
75 minutes/week × 52 weeks = 3,900 minutes/year
3,900 ÷ 60 = 65 hours/year
Step 3: Monetary value
65 hours × $50/hour = $3,250 in annual value
Step 4: Cost of the automation
n8n Cloud Starter: $240/year
Step 5: ROI
($3,250 - $240) ÷ $240 × 100 = 1,254% ROI
An ROI of 1,254% means that for every dollar you invest in n8n, you recover $12.54 in productive time. And that's just ONE automation. When you have 5 or 10 active workflows, the return multiplies.
This calculation doesn't include intangible benefits like less stress, zero errors, and a better customer experience — which frequently are worth more than the time saved.
Summary
The 16 use cases in this lesson demonstrate a simple truth: automation isn't an abstract concept — it's the difference between spending your time doing copy-paste and spending it growing your business.
- Marketing (Cases 1-4) — Lead capture, social media publishing, metrics reports, email segmentation. The entire marketing operation can be systematized.
- Sales (Cases 5-8) — Follow-ups, lead scoring, proposals, real-time pipeline. Selling more isn't working more, it's automating the repetitive.
- Operations (Cases 9-12) — Onboarding, inventory, invoices, incidents. Internal processes are the ones that benefit most from automation because nobody sees them until they fail.
- Freelancers (Cases 13-16) — Project management, invoicing, content calendar, feedback. As a freelancer, your scarcest resource is your time. Automating is like hiring an assistant who never gets tired.
The universal pattern: TRIGGER → PROCESS → DECISION → ACTION → NOTIFICATION. All workflows follow this structure. Mastering it is mastering automation.
Next lesson: Create Your n8n Cloud Account — we leave the concepts behind. It's time to open n8n, see the interface for the first time, and get everything ready to build your first real workflow.
Resources
- n8n Templates Library — Hundreds of ready-to-use workflows, organized by category and tool. Search for your use case and see how others solved it.
- n8n Community Workflows — Workflows shared by the community with explanations and screenshots
- Marketing Automation — n8n Blog — Specific articles about marketing automation with n8n
- Sales Automation — n8n Blog — Use cases and tutorials for automating sales processes
- n8n for Freelancers — Official use cases page organized by role and need
- The ROI of Automation — Zapier Research — Study on the return on investment of automation in small businesses (the principles apply to n8n as well)