n8n Automation: 15 Real-World Examples That Save Hours Every Week

The most common entry point for n8n in sales teams. A visitor fills out any lead form — on your website, Typeform, Calendly, or a landing page — and n8n handles everything that used to happen manually: creating a contact in the CRM, notifying the assigned sales rep in Slack with the lead's details, and triggering the first email in your drip sequence.

The key value here isn't just speed — it's consistency. Without automation, leads who come in at 6pm Friday don't get a Slack notification until Monday morning. The response rate on those leads is significantly lower. With n8n running 24/7, every lead gets processed in under 30 seconds, regardless of when they submit.

The Slack message format matters — include the lead's company, the page they came from (pass this as a hidden field in the form), and a direct link to the new CRM record. Sales reps spend zero time looking up context.

When a deal moves to "Proposal Sent" or "Contract Signed" in your CRM, three things usually need to happen: the manager gets notified, the event gets logged in a shared spreadsheet for pipeline tracking, and — if it's a won deal — onboarding gets triggered. Without automation, at least two of these steps get forgotten, especially the logging.

In n8n, this workflow uses the CRM's webhook trigger (HubSpot, Pipedrive, and Salesforce all support deal-update webhooks) to fire whenever a deal stage changes. An IF node checks which stage it moved to and branches accordingly — different Slack messages for "Negotiation" vs "Won" vs "Lost", and the "Won" branch additionally creates a Google Sheets row and triggers a welcome email to the new customer.

Sales reps spend a surprising amount of time researching new leads before making contact — looking up the company size, industry, tech stack, LinkedIn profile. This workflow cuts that research time by enriching CRM contacts automatically with data from external sources the moment they're created.

When a new contact appears in HubSpot or Pipedrive, n8n calls a data enrichment API (Clearbit, Hunter.io, Apollo.io, or RocketReach depending on your stack), gets back company info — size, revenue, industry, headquarters, social profiles — and writes all of it back to the CRM contact fields automatically. The rep opens the CRM record and the research is already there.

The Set node is important here — it maps the API response fields to your CRM's field structure, which differs between platforms. This workflow requires configuring an API key but still no custom code.

The setup: your marketing team manages a content calendar in Airtable or Notion. Each row is a post — text, image URL, target platform, publish date. The n8n workflow runs every morning, reads all rows with a "Scheduled" status and a publish date matching today, and posts each one to the appropriate platforms (Twitter/X via API, LinkedIn via HTTP, Buffer or later.com for Instagram).

After posting, n8n updates the row's status to "Published" and logs the post URL back to the spreadsheet. The marketing team plans content in their preferred tool; the workflow handles all the actual publishing without anyone logging into social media platforms manually. For teams posting 10–20 pieces per week across 3+ channels, this removes an hour of daily work.

This workflow runs every Monday at 9am. It pulls last week's data from three sources — Google Analytics 4 (sessions, conversions, top pages), Google Search Console (impressions, clicks, average position), and your ad platform (spend, clicks, ROAS) — formats it into a structured Slack message, and posts it to the #marketing channel before the team's weekly standup.

The result is that every Monday, the whole team sees the previous week's performance before they've opened a single dashboard. The n8n "Function" node handles date calculations (last Monday to last Sunday) and number formatting (rounding ROAS to 2 decimal places, formatting large numbers with commas). Once built, this workflow requires zero maintenance unless you change your reporting structure.

When a new post is published on your blog (WordPress, Webflow, Ghost — anything with an RSS feed), n8n detects it via the RSS Feed trigger node and automatically: posts a teaser to Slack for the internal team, creates a draft social post in Buffer for review, sends the article URL to your newsletter tool (Mailchimp, ConvertKit) for the weekly digest queue, and optionally sends a Telegram notification to your subscriber channel.

The n8n RSS trigger checks for new items every hour by default. When a new post appears, all distribution steps happen in parallel using n8n's parallel branch capability — Slack, Buffer, and Mailchimp run simultaneously, so the total execution time is the slowest single API call, not the sum of all of them. This matters when you're distributing to 5+ channels.

One of the most consistently valuable n8n workflows in medium-sized teams. When a new hire record is created in BambooHR, Workday, or even a Google Sheet that HR manages, n8n kicks off the full onboarding sequence automatically: creates a Google Workspace account with the right email format, adds the new hire to the correct Slack channels (based on their department and location), creates a Notion onboarding page from a template with their name and start date, assigns a checklist in Asana or Jira for the IT setup tasks, and sends a welcome email to the new hire's personal email with their first-day details.

Without this workflow, onboarding involves at minimum 5 people touching different systems, often in the wrong order. Teams consistently report that before automation, new hires sometimes started without Slack access or couldn't log into their tools until day 2 or 3. The automation ensures every step completes before the start date, not after the hire is already sitting at their desk.

Finance teams receive dozens of vendor invoices per week by email. Each invoice is a PDF attachment that needs to be opened, the key fields (vendor, amount, due date, invoice number) extracted and entered into the accounting system, and the original PDF saved to a folder. This is 3–5 minutes of work per invoice that n8n handles automatically.

The workflow monitors a designated Gmail inbox (invoices@yourcompany.com). When an email with a PDF attachment arrives, n8n downloads the attachment, sends it to a document parsing service (Mindee, Google Document AI, or the OpenAI Vision API for lower volume), extracts the structured data, and creates a bill record in QuickBooks or Xero. The PDF gets saved to Google Drive in the correct vendor folder, and a Slack message goes to the finance channel with a summary and a link to the new accounting entry.

Purchase requests, expense approvals, time-off requests — any decision that needs a manager's sign-off before an action is taken. The pattern: an employee submits a request (via a Google Form, an internal tool, or even a Slack slash command), n8n sends the manager a Slack message with the request details and two buttons — Approve and Reject. The manager clicks one; n8n receives the response via a Slack webhook, records the decision in a spreadsheet, and takes the appropriate follow-up action (notifying the requester, creating a PO in the procurement system, or updating the HR platform).

This workflow eliminates email chains entirely. The approval loop — request, review, decide, notify — happens in Slack in minutes instead of hours. Building interactive Slack messages in n8n requires using the Slack API's Block Kit format in the HTTP node rather than the standard Slack node, but the n8n documentation covers this pattern specifically.

Support teams spend significant time simply reading tickets to figure out where they should go: billing? technical? onboarding? The triage step itself — before any actual support work happens — can consume 30–60 minutes per day for a busy team. This workflow replaces that triage entirely.

When a new support ticket arrives (via email, Zendesk, Intercom, or a custom form), n8n sends the ticket text to an AI Agent node with a system prompt that classifies it: category (billing/technical/onboarding/feature request), urgency (low/medium/high/critical), and a sentiment score. Based on the classification, the IF node routes it to the correct Slack channel and assigns it to the right team. The AI then drafts a suggested first response — not a final answer, but a starting point that the agent can review and send in seconds rather than writing from scratch.

Every busy professional has a variant of this problem: the inbox fills with emails that need some response, and every response requires reading the email, deciding what to say, and writing it. For emails that follow predictable patterns — vendor questions, scheduling requests, standard customer inquiries — the AI can produce a near-final draft that takes 10 seconds to review and send rather than 5 minutes to write.

This workflow monitors a Gmail label ("needs-draft") or runs on a schedule. It reads unprocessed emails, sends each one to Claude or GPT-4 with your personal context (who you are, what your company does, your typical tone, any specific instructions for common email types), and saves the draft response back to Gmail as a draft — not sent, always for your review. In the morning you open Gmail, scan the pre-written drafts, make any adjustments, and send. Teams that adopted this report reducing email processing time by 40–60%.

This is n8n's most technically impressive use case and one that previously required a full engineering project to build. The goal: a team uploads their internal documents (SOPs, product specs, HR policies, legal contracts) and employees can ask questions about them in plain English — "What's our policy on remote work expense reimbursement?" — and get accurate, sourced answers.

The ingestion workflow runs when a new document is added to a Google Drive folder: n8n downloads the PDF, splits it into chunks using a text splitter node, generates embeddings for each chunk via OpenAI's embedding API, and stores them in a Supabase or Pinecone vector database with metadata. The query workflow: user sends a question via a chat interface or Slack command → n8n embeds the question → retrieves the most similar chunks from the vector DB → passes them to Claude or GPT-4 with the question → returns an answer with the source document cited. Accuracy depends heavily on chunk size and embedding quality — both configurable in n8n's vector store nodes.

Cart abandonment rates average 70% across e-commerce — 7 out of 10 people who add to cart don't complete the purchase. The difference between stores that recover 5% of those vs 15% is almost always whether they have a timed recovery sequence running. With n8n connected to Shopify or WooCommerce, this sequence runs automatically for every abandoned cart.

When Shopify fires the "checkout abandoned" webhook, n8n starts the sequence: after 1 hour, send a friendly reminder email ("You left something behind"). If no purchase in 24 hours, send a second email with a discount code generated specifically for this customer. If no purchase in 72 hours, optionally send an SMS via Twilio and mark the cart as lost in your tracking sheet. The n8n Wait node handles the delays — the workflow literally pauses for 1 hour, then continues. No polling required. The discount code can be generated dynamically via the Shopify API within the workflow.

Running out of stock on a best-selling SKU is one of the most expensive operational mistakes for an e-commerce business — you lose sales and potentially damage your marketplace ranking at the same time. This workflow prevents it by checking inventory twice a day and acting on anything that drops below a threshold.

The workflow runs at 9am and 3pm. It pulls current stock levels from Shopify, WooCommerce, or a warehouse management system via API. It compares each SKU against a threshold table in Google Sheets (which the operations team manages — different thresholds for different product categories and lead times). For any SKU below threshold, it sends a Slack alert to the purchasing team with the SKU, current stock, and threshold. For pre-approved supplier relationships, it optionally drafts a purchase order email to the supplier with the reorder quantity pre-calculated based on average daily sales (also pulled from the store).

Development teams that use both GitHub and Jira end up with a data synchronisation problem: the PR exists in GitHub, the linked Jira ticket exists in Jira, and keeping them in sync requires manual updates on both sides. When a PR is opened that references a Jira ticket number in its title or branch name (a common convention — "feature/PROJ-123-new-payment-flow"), n8n automates the full loop.

The GitHub webhook fires when a PR is opened or converted from draft. n8n extracts the Jira ticket number from the PR title using a regex in the Set node, updates the Jira ticket status to "In Review", adds a comment to the Jira ticket with a link to the PR, and posts a Slack message to the team channel with the PR title, author, branch name, and a direct link. If the PR is marked as ready for review (not a draft), n8n also uses GitHub's API to assign a reviewer based on a rotation list stored in Google Sheets — so reviewer assignment happens automatically without the PR author having to pick someone manually.