10 n8n Workflow Examples You Can Actually Build and Sell

Most of the n8n workflows people share to look clever are four nodes and a webhook. A trigger, an HTTP request, a Slack message, done. They demo beautifully and solve nothing a business would pay to keep running.

The workflows worth stealing are the boring ones. The ones that quietly move data between tools a company already pays for, every hour, without anyone touching them. Those are the ones that turn into a monthly invoice.

I've watched people learn n8n, build one flashy AI demo, and then freeze because they can't connect it to a real problem. So let me hand you ten workflows that map directly to money. For each one I'll give you what it does, the actual node chain, and who pays for it.

If you're brand new to the tool, start with what n8n is and the step-by-step n8n tutorial first, then come back here for the ideas.

Here's the reframe I want you to carry through the whole post: a workflow is only worth building if someone would notice when it stops. That's the difference between a portfolio piece and a retainer.

Marketing workflows

These are the easiest to sell because marketers already understand that time spent copy-pasting is time not spent on strategy.

1. Lead capture, enrich, and route (beginner). A form or ad lead comes in and instantly gets cleaned up, scored, and dropped where the sales team actually looks.

Node chain: Webhook (form submission) -> HTTP Request (enrichment API like Clearbit or Apollo) -> IF/Switch (route by company size or budget) -> HubSpot/Airtable node (create contact) -> Slack node (alert the owner).

Who pays: any agency or B2B service business drowning in Typeform submissions that nobody follows up on fast enough. This alone is worth $300-600/mo because speed-to-lead is money, and you can prove it.

2. Abandoned-form and abandoned-cart follow-up (intermediate). Someone starts a checkout or a multi-step form, then bails. This flow waits, checks whether they finished, and nudges them if they didn't.

Node chain: Webhook (form/cart started) -> Wait node (30-60 min) -> HTTP Request (check if the order or submission completed) -> IF (not completed) -> Email/SMS node (send the nudge).

Who pays: e-commerce stores and course sellers. Recovering even 5% of abandoned carts pays your retainer ten times over, which makes this an easy yes. Beginner-friendly to build, but you need honest tracking so you don't message people who already bought.

3. AI content pipeline: news to draft social posts (intermediate). Pull fresh articles in your client's niche, summarize them, draft posts in the client's voice, and queue everything for a human to approve before anything goes out.

Node chain: RSS Feed / Schedule Trigger -> HTTP Request (fetch full article) -> AI/LLM node (summarize + draft 3 posts) -> Airtable or Notion node (save as "pending approval") -> Slack node (ping the marketer to review).

Who pays: personal brands, founders, and small marketing teams. The approval step is the whole trick. Never let AI post directly, because one hallucinated stat published to 40,000 followers ends the relationship. This is a comfortable $500-1000/mo service.

Sales and CRM workflows

Sales teams pay for anything that removes admin from the day, because admin is the thing keeping them off the phone.

4. New customer onboarding across apps (intermediate). A deal closes, and the new customer gets set up everywhere at once without anyone remembering the checklist.

Node chain: Stripe/CRM Trigger (payment or "won" stage) -> Create records in parallel: Google Workspace or app account, project in Asana/ClickUp, contact in the email tool -> Email node (branded welcome) -> Slack node (notify the account manager).

Who pays: SaaS companies and agencies onboarding clients by hand. Every new customer is 30-45 minutes of clicking. Automate it and you've saved real hours per week, which is the number you put on the invoice.

5. Support ticket triage with AI tagging (advanced). Every incoming ticket gets read, categorized, prioritized, and routed before a human sees it, so the urgent stuff surfaces first.

Node chain: Email/Help-desk Trigger (Zendesk, Freshdesk, Gmail) -> AI/LLM node (classify: category + urgency + sentiment) -> Switch (route by category) -> update ticket + assign -> Slack node (escalate anything flagged angry or urgent).

Who pays: any company with a support inbox that a person triages manually every morning. This is advanced because your prompt and your categories have to be tuned to their actual product, but it's sticky. Once it's running, nobody wants to go back.

Operations and finance workflows

This is where the least glamorous work hides, which is exactly why the money is good and the competition is thin.

6. Invoice and receipt data extraction (advanced). A PDF invoice lands in an inbox or a folder, and the important numbers get pulled out and logged without anyone typing them.

Node chain: Email Trigger or Google Drive Trigger (new PDF) -> Extract From File node (get the text) -> AI/LLM node (pull vendor, amount, date, line items into structured JSON) -> Google Sheets or QuickBooks node (append the row) -> Slack node (flag anything the AI wasn't confident about).

Who pays: bookkeepers, small finance teams, and agencies reconciling vendor bills. Manual data entry from PDFs is pure tedium and it's error-prone. Charge for the hours saved and the mistakes avoided, because both are real.

7. Website or price change monitor (beginner). Watch a page, a competitor's pricing, or a job board, and alert the client the moment something changes.

Node chain: Schedule Trigger (hourly/daily) -> HTTP Request (fetch the page) -> HTML Extract node (grab the target value) -> Compare against the last stored value (Data Store or a Sheet) -> IF (changed) -> Slack/Email node (notify).

Who pays: e-commerce teams tracking competitor prices, recruiters, and anyone monitoring stock or listings. One of the fastest workflows to build, and clients love it because it feels like a superpower. Great first paid deliverable.

8. Scheduled data sync between two SaaS tools (intermediate). Keep two tools that don't talk to each other in agreement on a schedule. No more exporting a CSV from one and importing it into the other every Monday.

Node chain: Schedule Trigger -> Source node (read records from tool A, e.g. Airtable or a database) -> transform/map fields -> Destination node (upsert into tool B, e.g. a CRM or Google Sheet) -> log the run.

Who pays: basically every business running two systems that "almost" integrate. It's unglamorous and permanent, which is exactly the kind of workflow that stays on a retainer for years.

AI and reporting workflows

AI makes these possible, but the boring scheduling and formatting around it is what makes them sellable.

9. Daily metrics digest (intermediate). Pull numbers from a few APIs every morning, format them into a clean readable summary, and drop it in the client's inbox or Slack before they've had coffee.

Node chain: Schedule Trigger (7am) -> multiple HTTP Request nodes (Stripe revenue, GA4 traffic, ad spend) -> Merge node -> AI/LLM node (write a short plain-English summary of what changed) -> Email or Slack node (send the digest).

Who pays: founders and marketing managers who currently log into five dashboards to answer "how did we do yesterday?" Bundle it with your other work or sell it standalone. The AI-written commentary is what makes it feel premium instead of just a data dump.

10. Inbound email classify and auto-draft reply (advanced). Read incoming email, understand what it's asking, and draft a reply the client only has to approve and send.

Node chain: Gmail/Outlook Trigger -> AI/LLM node (classify intent + urgency) -> Switch (sales / support / spam / personal) -> AI/LLM node (draft a reply using a knowledge base or past emails) -> Gmail node (save as draft) -> Slack node (notify: "draft ready to review").

Who pays: solo founders and small teams buried in repetitive email. The human-approves-before-send rule is non-negotiable here, both for quality and for trust. This is advanced, high-value work, and it's the kind of thing people quietly pay $1000-2000/mo to keep.

Turning these into a business, not a hobby

Notice the pattern. Every workflow above has a trigger a business cares about, a transformation that used to eat someone's afternoon, and a notification so a human stays in the loop. That structure is the product.

The builders making real money aren't chasing the flashiest AI demo. They pick two or three of these, get genuinely good at them, and sell them as a monthly service. One person running five of these for five clients is looking at $2,500-10,000/mo without hiring anyone. That's the whole one-person-agency model, and automation is one of the cleanest ways into it.

If you want the structured path instead of piecing it together from scattered videos, that's what CodingPhase is built for. The AI automation career path walks you from your first workflow to packaging and pricing client work, and how to become an AI automation specialist lays out the full roadmap.

Membership is $49/month, or $250/year (roughly $21/mo billed annually), with a 7-day money-back guarantee, so you can try it and bail if it's not for you. If you'd rather pay once and own it, the Tech Accelerator is $1,500 lifetime and adds live weekly mentorship on top of every course. Either way you get the automation path plus the one-person-agency playbook that turns these workflows into invoices.

FAQ

Do I need to know how to code to build these n8n workflows? No, and that's the point. n8n is visual, so you drag nodes and connect them. Light JavaScript in a Code node helps for the advanced ones (custom transforms, tricky data shapes), but you can build and sell the beginner and intermediate workflows here without writing much at all.

How much can I actually charge for one of these? Honestly, it depends on the pain you're removing. A simple page monitor might be $150-300/mo. A support triage or email-drafting system that saves a team hours daily can run $1000-2000/mo. Price the value to the client, not the hours it took you to build, because the client is buying the time back.

Is n8n better than Zapier for client work? For agency and reseller work, usually yes, because you can self-host it, which kills per-task fees that wreck your margins at scale. Zapier is faster to start and has more prebuilt integrations. I break the tradeoffs down in n8n vs Zapier so you can pick per client instead of picking a side.

What's the fastest workflow to build first? The page or price monitor (number 7) or the lead-routing flow (number 1). Both are beginner-level, both solve a problem a business feels immediately, and both make a strong first paid deliverable you can point to when you pitch the next client.

Won't AI hallucinations get me in trouble? Only if you let AI act without a human check. Every AI workflow here ends in a draft, a queue, or an approval step, never a direct send or post. Keep a person on the trigger for anything customer-facing and you get the speed of AI without betting your client relationship on a wrong guess.

Pick one workflow from this list. Not five. Build it end to end, break it, fix it, and get it running reliably for a single real use case, even if that use case is your own inbox. That one finished workflow teaches you more than ten half-built demos, and it's the thing you show the first client who asks what you can do.

You don't need to be an expert to start. You need one working automation and the nerve to charge for the next one. If you want a guide the whole way through, we've got you inside CodingPhase. Go build something that someone would miss when it stops.