Chris Alarcon | The Boring Claude Setup That Actually Works

n8n Tutorial for Beginners: Step-by-Step Guide

I tried n8n a handful of times before it clicked. Heads up: some links in this post are affiliate links — a small kickback to me at no cost to you. I only recommend tools I've actually run. Each time I quit because it felt too complex, too overwhelming, too... much. Authentication errors. Weird node configurations. Tutorials that assumed I already knew what I was doing. Everyone said n8n was "easy" and "just like Zapier but free" but I kept bouncing off it. Then I picked one project I actually wanted to ship and committed to finishing it in n8n. The result was clunky. I built four agents where one would have done. But it worked, and that was enough for the model in my head to settle. This is the tutorial I wish I'd had on attempt one: a setup walkthrough, three workflows you can build in a sitting, and the debugging tricks that turn "this is too hard" into "okay, I get it now." What Is n8n? (And Why It's Worth Learning Even Though Zapier Is Easier) n8n is a free, open-source automation tool that connects apps and services together. Think Zapier or Make.com, but you own it. Here's the rough shape (always check current pricing - SaaS plans move):Feature n8n Zapier MakeCost Free self-hosted or paid cloud Tiered, per-task Tiered, per-operationWorkflows Unlimited Limited by plan Limited by planLearning curve Steeper Easiest MediumCustomization Full code access Limited MediumExecution limits None (self-hosted) Plan-based Plan-basedWhy people choose n8n:No per-execution fees (huge if you run workflows at scale) Self-hosting means you control everything Code nodes let you customize anything Open-source community constantly adds integrationsWhy it's harder: Zapier holds your hand. n8n expects you to figure some things out. Authentication setup is more manual. Error messages are less friendly. The first hour is rougher. But here's the thing: once you get past the setup friction, n8n becomes your most powerful tool. You're not locked into pricing tiers. You're not limited by "tasks per month." You build what you need, exactly how you need it. Worth it? For me, absolutely. One important update: if you're using AI coding agents now, n8n is not the whole stack. It is the automation layer. I broke down the split in Claude Code vs n8n and the lean stack in AI stack for solo founders.Related Reading:n8n workflow examples worth building How to Automate Social Media with AIHow to Set Up n8n (2 Options: Cloud vs Self-Hosted) You have two paths. Pick based on your comfort level and budget. Option 1: n8n Cloud (Fastest) If you just want to start building:Go to n8n.io Click "Start for free" Sign up with email You're in. Start building immediately.Pros: Zero setup. Free trial. Good for testing. Cons: Recurring fee. You're on their infrastructure. Option 2: Self-Hosted on a small VPS (What I Use) This is what I run. One-time setup, then you own the box. What you'll need:A VPS like Hostinger (their entry-level plan is fine) Basic command line comfort (I'll walk you through)Steps:Spin up a small VPS SSH into your server Install Docker: curl -fsSL https://get.docker.com -o get-docker.sh && sh get-docker.sh Run n8n container: docker run -it --rm --name n8n -p 5678:5678 -v ~/.n8n:/home/node/.n8n n8nio/n8n Access at http://your-server-ip:5678Some hosts now have one-click n8n installers, which makes this even faster. The manual Docker route is still short. Why self-hosted: Unlimited workflows, no per-execution fees, full control. The trade-off is you own the maintenance. First Login: What You'll See You'll land in a blank canvas with a "+" button. This is your workflow editor. Don't panic - it's simpler than it looks. Click the "+" and you'll see the node library. Over 400 integrations. Ignore most of them for now. The 7 n8n Nodes That Actually Matter (Ignore the Other 400+) n8n has 400+ nodes. I use the same 7 for 90% of my workflows. Here's what I learned: You don't need to learn all the nodes. You need to master the ones you'll actually use.1. Schedule Trigger Runs workflows on a schedule (daily at 9am, every Monday, etc.). Perfect for recurring automations. 2. Webhook Trigger Lets external services trigger your workflow via URL. Foundation for Zapier-style integrations. 3. Code Node Write custom JavaScript. This is where n8n becomes infinitely flexible. I use this constantly. 4. Switch Node Routes data based on conditions (if status = "paid", do X; if status = "pending", do Y). Essential for complex logic. 5. IF Node Simple true/false logic. Cleaner than Switch when you only need 2 paths. 6. Set Node Formats data. Renames fields, extracts values, cleans up messy API responses. 7. Wait Node Pauses workflow execution (wait 5 minutes, wait until specific date). Critical for timing-sensitive automations. Bonus: AI Agent Node Connects Claude, ChatGPT, and other LLMs directly into workflows. This is where workflows stop being "if-this-then-that" and start handling judgment calls. If you want to build agentic workflows that make decisions and use tools, check out my AI Agent node guide. Start with these. Once you're comfortable, explore the other 393 nodes. But you can build 90% of useful automations with just this core set. Workflow #1: Gmail to Slack Notification (The "Hello World" of n8n) Let's build your first workflow. Simple, practical, teaches the fundamentals. What it does: When you get an important email, it sends a Slack notification instantly.Step-by-step:Add Gmail TriggerClick "+" → Search "Gmail Trigger" Select "On Message Received" Click "Connect my account" Authorize Google (this is the authentication step everyone struggles with - just follow the OAuth flow)Add IF NodeClick "+" → Search "IF" Set condition: {{ $json["subject"] }} contains "urgent" This filters only urgent emailsAdd Slack NodeClick "+" → Search "Slack" Connect your Slack workspace Choose channel (e.g., #alerts) Message: New urgent email from {{ $json["from"]["name"] }}: {{ $json["subject"] }}Test ItClick "Execute Workflow" Send yourself a test email with "urgent" in subject Check SlackWhat you just learned:Authentication (connecting Gmail + Slack) Triggers (Gmail watching for new emails) Data mapping (those {{ $json["field"] }} expressions) Testing workflows before activating themCommon error: "Authentication failed" → Go back to the node, click "Reconnect", re-authorize. n8n's OAuth sometimes needs a second try. Workflow #2: Daily Twitter/X Post Automation (Schedule Trigger + AI) Now let's build something that runs on autopilot. What it does: Every day at 9am, Claude generates an automation tip and posts it to Twitter/X. Step-by-step:Add Schedule TriggerClick "+" → "Schedule Trigger" Set to "Every Day" at 9:00amAdd AI Agent NodeClick "+" → Search "AI Agent" Connect Claude API (you'll need an Anthropic API key) Prompt: Write a 1-sentence automation tip for solo builders running lean AI businesses. Make it actionable and specific. No hashtags.Add Twitter NodeClick "+" → Search "Twitter" Connect your Twitter account Tweet text: {{ $json["output"] }}Activate ItClick the toggle in top-right: "Inactive" → "Active" Your workflow is now live. It'll run every morning at 9am automatically.Key difference from Workflow #1: This one RUNS without you. Once activated, n8n executes it on schedule. You're not clicking "Execute" - it just happens. What you just learned:Schedule triggers (time-based automation) AI integration (Claude generating content) Activating vs testing (live workflows vs manual execution)This is where automation starts to feel worth it. You build it once, then it runs unattended (until something upstream changes - which it will). Workflow #3: Webhook to Google Sheets (Capture Data from Anywhere) Final workflow: the foundation for advanced automation. What it does: Create a custom webhook URL that receives data and saves it to Google Sheets. Use this for form submissions, Zapier alternatives, custom integrations - anything. Step-by-step:Add Webhook TriggerClick "+" → "Webhook" Method: POST Copy the webhook URL (looks like https://your-n8n.com/webhook/abc123)Add Set Node (optional but recommended)Formats incoming data Map fields: name = {{ $json["body"]["name"] }}, email = {{ $json["body"]["email"] }}Add Google Sheets NodeClick "+" → "Google Sheets" Connect your Google account Choose spreadsheet and sheet Map columns to data fieldsTest ItUse Postman or curl to send test POST request:curl -X POST https://your-n8n.com/webhook/abc123 \ -H "Content-Type: application/json" \ -d '{"name":"Chris","email":"test@example.com"}'Check Google Sheets - data should appearWhat you just learned:Webhooks (HTTP endpoints you control) Data transformation (Set node cleaning up messy inputs) Google Sheets integration (foundational for so many workflows)This pattern matters. Most SaaS tools, form builders, and APIs can send webhook data. Once you understand this one workflow, the connectable surface area gets a lot bigger.Want more n8n workflows? I send practical automation systems from the Ship Lean build - real workflows I'm testing, not recycled theory. No spam, unsubscribe anytime. Get the free prompt pack →What Just Broke? The n8n Debugging Guide That Actually Works You'll hit errors. Everyone does. Here's how to fix the most common ones.Error #1: "Authentication Failed" What it means: The app connection dropped or expired. Fix:Click on the node with the error Click "Reconnect" or "Select Credential" Re-authorize the app (OAuth flow) Test againError #2: "Cannot Read Property of Undefined" What it means: You're trying to access data that doesn't exist. Fix:Click the node BEFORE the error Look at the output data (bottom panel) Check your expression: {{ $json["field"] }} must match actual field names Use the "Expression Editor" (click the = icon) to see available fieldsError #3: "Expression Could Not Be Resolved" What it means: Syntax error in your data mapping. Fix:Common mistakes: Missing brackets: {{ $json["name"] }} not {{ $json[name] }} Wrong node reference: {{ $node["Node Name"].json["field"] }} Typo in field nameUse the Expression Editor to validate syntaxMy 5-Step Debug Process:Execute one node at a time - Click "Execute Node" instead of "Execute Workflow" Check the output panel - Bottom of screen shows exactly what data the node produced Use the Code node to log data - Add console.log(items) to see what's actually there Test with static data first - Use "Set" node with hardcoded values to isolate issues Check the n8n community forum - Someone's hit your exact error beforeTurns out: Debugging is half the skill. Get good at reading error messages and checking data output, and you'll fix issues in 2 minutes instead of 2 hours. How to Learn from 1,000+ Pre-Built Workflows (Without Copy-Pasting) You don't have to build everything from scratch. Where to find templates: n8n.io/workflows - 1,000+ pre-built workflows How to use them:Browse templates (filter by category: Marketing, Sales, Productivity, etc.) Click "Use Workflow" It opens in your n8n editor Reconnect credentials (templates don't include your API keys) Modify to fit your use caseBest templates for beginners:"Send Slack notification for new Gmail" - Teaches triggers + messaging "Save form submissions to Google Sheets" - Teaches webhooks + data storage "Daily weather report to email" - Teaches schedule triggers + external APIs "Summarize web articles with AI" - Teaches AI integration + HTTP requestsHere's what I learned: Don't just copy-paste. Study how they built it. See how they structured nodes. Then adapt the pattern to your own workflows. The template library is a masterclass in workflow design. Use it. Lessons From Actually Using n8n Here's what I wish I'd known on day one: 1. Plan First, Build Second I used to jump straight into n8n. Bad move. Now I sketch workflows in Excalidraw first. 10 minutes of planning saves hours of rebuilding. 2. Only a Few Nodes Matter You don't need to learn 400 nodes. Master the core 7-10. I still barely touch 90% of the library. 3. Find the Nodes You Enjoy Some people love the Code node. Others prefer visual logic (IF, Switch). Figure out which style fits your brain and lean into it. 4. Give Yourself Permission to Fail Not every workflow needs to be perfect. Some are stepping stones. My first automation (that faceless YouTube workflow) was clunky - 4 agents when it should've been 1 - but it taught me how the tool actually behaves. 5. Start with Templates, Then Customize Templates teach you patterns. Once you understand the pattern, you can apply it anywhere. 6. Debugging Is Part of the Process I used to think errors meant I was doing it wrong. Now I know: errors are just feedback. Read them, fix them, move on. 7. Self-Hosting Earns Its Keep Quickly If you're going to run more than a couple of workflows, self-hosting n8n on a small VPS like Hostinger usually wins on cost vs per-task SaaS pricing. Unlimited workflows, no execution limits, full control. The trade-off is you own the box. Callback: My first n8n project was a mess. But it worked, and that was enough to keep going. Ship something clunky. Refine later. Your Next Steps: From Beginner to Builder You've built 3 workflows. You know the core nodes. You can debug basic errors. Now what? Immediate (Next 24 Hours):Build one of the 3 workflows above (pick the one you'd actually use) Test it until it works Activate it and let it runThis Week:Explore the template library - find 3 workflows you'd use Customize one template to fit your exact use case Break something, then fix it (seriously, debugging practice is how you learn)This Month:Build one automation that removes a recurring chore from your week Examples: Daily digest of top Hacker News posts → email New blog post → drafted social posts, queued for review Form submissions → auto-add to CRM + send confirmation emailOnce that's boring:Self-host n8n on your own server Build multi-step workflows with more logic (Switch, Loop, Merge nodes) Add an LLM step where judgment matters (see the n8n AI Agent tutorial) Connect n8n to the rest of your stackRelated Reading:n8n workflow examples worth building How to Automate Social Media with AIYou're Not Behind - You're Right on Time I tried n8n a handful of times before it worked. You might need two tries. You might get it on the first one. Doesn't really matter. What matters: you now know how to set up n8n, build three working workflows, and debug the most common errors. That puts you ahead of most people who hear "n8n" and think "too complicated." You have the tutorial. You have the workflows. You have the debugging checklist. The only thing left is to actually build something. Pick one workflow from this guide. Build it. Break it. Fix it. Then build another. Before you go full speed, read how to save time with automation. It'll help you pick the right workflows first - the ones that actually pay off instead of sitting there untouched. And if you're not sure which repetitive tasks to tackle, here's my workflow mapping process. If you'd rather skip the building and have a content workflow set up around your videos, Content Flywheel DFY is the done-for-you version. Otherwise, start here and I'll send you the free prompt pack plus the next useful system I package.This post is part of the n8n AI agents hub: definitions, tutorials, workflow patterns, and the build-vs-run decision pages in one place.

n8n Workflow Examples: 7 Automations Worth Building (and 2 That Aren't)

My first n8n workflow was clunky, overcomplicated, and had four agents where one would have done. But it worked. That ugly pipeline scraped Reddit, wrote scripts, generated voiceovers, and stitched everything together with Creatomate. A faceless YouTube setup, built by someone who'd never touched n8n before. I never published from it - the real value was learning the tool. Here's the thing about content work: the actual creative part is maybe 20% of the time. The other 80% is formatting, scheduling, cross-posting, research. The repetitive tasks that pile up before you even start writing. n8n is the layer I kept coming back to for that 80% across two years of running it. Self-hosted, unlimited workflows, no per-task fees. (My own automation has since moved into Claude Code — but for trigger-based content workflows like these, n8n is still what I'd point you to.) Heads up: some links in this post are affiliate links — a small kickback to me at no cost to you. I only recommend tools I've actually run. Quick caveat before the list: building the right automation matters more than building one well. I've burned plenty of weekends on systems I never used. Here's the framework I use to decide what's worth automating - run any workflow on this list through it before you commit. What follows are seven workflows worth building. Most of them I have run or built myself; where a pattern is one I would wire rather than one I have shipped, I say so in the section. Treat the time and engagement notes as my own ballparks, not promises - your numbers depend on your volume and audience. Updated July 2026: n8n's template gallery now lists over 10,000 workflows. That is the problem, not the solution. Nobody needs another list of what you can build. So this is seven worth building, plus two I killed and why - including one on this very list that I no longer think anyone should build. If you're deciding where n8n should sit next to a coding agent, read my Claude Code vs n8n decision rule first. n8n is best as the reliable trigger/routing layer, not the whole brain.The whole page in one table, including the two workflows this post kills. The frequency test above everything: if you don't do it weekly, don't automate it. Before you build anything: the frequency test The most expensive n8n mistake is not a badly built workflow. It is a well-built workflow you never use. Plan first. Before you touch the canvas, brainstorm the use case with whatever LLM you already pay for - Claude, ChatGPT, Gemini, whatever. n8n costs you real time, and you do not want to spend hours or days or weeks building something you will barely touch. Build something you can maintain and understand. The rules I would hold you to:The weekly threshold. If you are not doing the task at least weekly, do not automate it. One r/n8n comment puts the bar well: "if you're doing the same copy-paste or lookup more than 3x a week, automate it. everything else is procrastination disguised as productivity." The three-hour kill rule. If you are three hours into troubleshooting and still not close to working, that is your signal to stop, not to dig in. Platform limits are a stop sign, not a challenge. If the API does not support it, that is your answer. The one-week test. Build the simplest version of one use case. Use it for a week. If you did not touch it, you failed - and you learned that for a week instead of a month.Land on one, two, or three concrete use cases. Then do one at a time and feel it out. Build the simplest version first and scale from there. More nodes does not make you smarter. Complex workflows are hard to debug, hard to test, take too long to build, and then you do not use them. That framing is why two workflows later on this page get killed rather than refreshed. Why n8n Over Other Automation Tools? Before diving into the workflows, let me address the obvious question: why n8n? I've tried them all. Zapier's pricing made me do math every time I wanted to automate something. Make (formerly Integromat) is solid, but the visual interface gave me headaches. n8n hits different:Self-hosted option: Run it on a small VPS and skip per-workflow fees Unlimited executions: No task counters Visual workflow builder: See exactly what's happening at each step Big integration library: Connect to most of the tools you already use Open source: Community nodes cover the edge casesThe learning curve is real - plan on a weekend to get comfortable. But once it clicks, the per-workflow cost goes near zero. (New to n8n? Start with my beginner's tutorial that walks through the interface and your first workflow.) Workflow 1: Content Repurposing Engine What it's for: Stop manually rewriting the same idea into five formats. This is the workflow that started it all. I write one blog post, and n8n transforms it into:3 LinkedIn posts (hook, insight, story format) 5 Twitter/X threads 1 YouTube script outline 1 newsletter sectionHow it works:Webhook triggers when I publish a new post Claude API extracts key insights and quotable moments Separate branches format content for each platform Everything lands in my Notion content calendarWant more powerful AI integration? If you want to make Claude truly autonomous - not just generating content, but making decisions and using tools - check out my my AI Agent node guide. The work is in the prompts. Generic "summarize this" prompts produce garbage. I keep iterating on prompts that match my voice and each platform's shape - it's never one-and-done. (Want to see the exact prompts I use? They're in my social media automation tutorial.) Setup time: About 2 hours for the full pipeline Key nodes: Webhook Trigger → Claude AI → Multiple branches → Notion API Killed: the Engagement-Aware Scheduler (replaced by Workflow 2) Status: do not build the smart-timing version. This slot used to hold a scheduler that nudged posting times based on past engagement data. The clever layer is gone. The data-driven scheduling matters less than people think, and the bigger win was always just being consistent - which makes the engagement layer a lot of nodes buying you very little. What survives is the boring half, and it is genuinely worth building. Workflow 2: Deterministic Stats Pull What it's for: Getting your real numbers into one place, on a schedule, without touching an API by hand. The honest use case here is deterministically pulling raw data into one dashboard. This is n8n's real strength. Not judgment. Fetching, on schedule, reliably. The pattern I'd wire:Cron trigger, daily or weekly Query the free YouTube Data API for video stats Pull LinkedIn numbers via Apify (realistically the only way to get them) Normalize and write into an n8n Data Table - native structured storage now, no spreadsheet middleman Read the week-over-week view whenever you want itWhy this one survives the frequency test: you want these numbers every single week, forever, and the task never needs a judgment call. That is the exact shape worth automating. Honest disclosure: personally I would just do this with Claude, because for me it is easier. But if you want it running on a schedule without you in the loop, this is the version of it I would build in n8n - and pulling deterministic data is a genuinely good use case for the tool. Setup time: 60-90 minutes, most of it in API credentials. Workflow 3: Trending Topics Monitor What it's for: Stop endlessly scrolling for what's blowing up. Let the workflow shortlist it. How it works:Scheduled trigger every few hours Pulls from a few sources: subreddits I care about, X/Twitter trends, Google Trends Claude scores each item for relevance to my audience Filters by quality Sends a Slack message with the top few opportunitiesThe real value isn't time saved - it's catching topics while they're still warm. Most won't be worth covering. The point is to surface the few that are. Setup time: A couple of hours Note: Reddit API requires developer access. The X API got expensive. Perplexity, news APIs, or RSS-based sources are reasonable alternatives. Want a content flywheel built around your videos? If you'd rather skip the wiring entirely - workflow, voice prompts, approval queue - take a look at Content Flywheel DFY. Workflow 4: Email Newsletter Automation What it's for: Cut the "blank-page Thursday" panic before sending a weekly newsletter. My newsletter workflow is embarrassingly simple, but it removed the biggest weekly headache. How it works:Every Thursday at 9 AM, workflow triggers Pulls my top-performing content from the week (based on analytics) Grabs any bookmarked links from my research Claude drafts the newsletter with my structure Sends draft to my email for reviewI still edit and personalize. But the 80% that's just assembly? Automated. Setup time: 1 hour Key insight: Don't try to fully automate newsletters. The personal touch matters. Automate the structure, not the soul. Workflow 5: Research and Clipping Pipeline What it's for: Stop losing the ideas that pop up at random times. Every content creator has the same problem: ideas pop up at the wrong moment and disappear before you can use them. This workflow captures everything. How it works:Multiple entry points: email forwarding, Slack command, browser extension webhook Everything funnels into a central processor Claude categorizes, tags, and summarizes Stores in Notion with full metadata Weekly digest of unused clipsMy "content ideas" folder used to be a graveyard. With this in place, it's at least searchable and tagged - which is the difference between an idea I can find later and one I lose. Setup time: 2 hours The thing that actually matters: The categorization step. Without it, you just create a different kind of mess. Killed: YouTube Thumbnail and Title Testing Status: do not build this. I killed mine. This page used to recommend it. It generated title variations, made thumbnail text variants, ran YouTube's built-in title test, and logged results to a spreadsheet for pattern analysis. Two reasons it is gone:It didn't work. The dataset never got big enough or clean enough to tell me anything I could act on. It produced activity, not answers. It costs more than the alternative. Every generated variant burns API credits. I can test the same ideas for free inside the ChatGPT subscription I already pay for.That is the whole obituary. A workflow that costs money to produce worse results than a thing you already own is not an automation, it is a hobby. Keep the underlying habit - testing titles and thumbnails is genuinely worth doing. Just do it in a chat window, for free, when you are about to upload. Workflow 6: Your n8n Workflows as Tools for Claude (MCP Server Trigger, new in 2026) What it's for: Letting the AI you already talk to trigger the automations you already built. This is the newest thing on this list and the one I would look at first if you are starting today. n8n can now act as an MCP server - meaning your workflows become tools that Claude or another assistant can call directly. The pattern I'd wire:MCP Server Trigger node, which gives you a test URL and a production URL Bearer or header auth so it is not open to the world Behind it, the workflows you already trust - the stats pull, the clipping pipeline Connect it to Claude Desktop, then just ask in plain languageWhy this matters: it resolves the tension running through this whole page. n8n is the reliable trigger and integration layer. The reasoning lives in the model. You stop trying to make n8n think, and you stop hand-running your automations. Setup time: 30 minutes if the workflow already exists. Workflow 7: Content Performance Dashboard What it's for: Stop opening five analytics tabs to figure out what's working. This workflow doesn't create content. It tells me what's working. How it works:Daily trigger at midnight Pulls analytics from: Google Analytics, YouTube, Twitter, LinkedIn Normalizes data and calculates week-over-week trends Generates a Slack report with insights Flags posts that need updating or promotionThe strategic value is hard to quantify. But having a single daily report instead of five tabs makes it more likely I'll actually look at the numbers. Setup time: 3 hours (most complex workflow on this list) Note: Analytics APIs can be finicky. Expect some debugging. Getting Started: The Practical Path Don't try to build every workflow on this page in one weekend. That's a recipe for burnout. Here's what I'd recommend: Week 1: Pick ONE workflow that addresses your biggest pain point. Build the simplest version that works. Week 2: Refine that workflow. Add error handling. Test edge cases. Make it bulletproof. Week 3: Add a second workflow. Build on what you learned. Each workflow you finish makes the next one easier - you reuse credentials, prompt patterns, and debugging instincts. That's the real compounding, not a tidy hours-saved number. The Honest ROI Picture Let me be straight about what to expect: Upfront investment:n8n learning curve: a weekend, give or take Each workflow: a few hours to build, more to make reliable Refinement: ongoingReturns:Less time on the boring 80% (formatting, scheduling, cross-posting) Faster turnaround on ideas Less burnout A system you can keep editing instead of rebuilding from scratchWhat you don't get: a magic ratio. Time savings depend on what you're already doing manually. The compound effect shows up after a few months of running and tweaking, not week one. Common Mistakes to Avoid The repeating mistakes I see (and have made):Over-engineering from day one. Start simple. Add complexity later.No error handling. Workflows break. Build in notifications so you know when they fail.Generic AI prompts. The quality of your AI-powered workflows depends entirely on your prompts. Invest time here.Forgetting the human element. Some things shouldn't be automated. Editorial judgment, relationship building, creative direction - keep those human.Not documenting. Future you will thank present you for leaving notes about what each workflow does and why.What's Next These are the workflows I keep coming back to. They handle the boring parts so I can spend time on the parts that actually need a human - and the two I killed are on the page precisely because knowing what to skip saves you more time than another template ever will. Automation isn't about being lazy. It's about being strategic with the time you actually have. Pick one workflow. The one that'll remove the chore you hate most. Build that this week. Then come back and grab the next one. More n8n Tutorials Step-by-step guides with screenshots, prompts, and the patterns I use:Social Media Automation: How to automate social media posts with AI Agentic workflows: n8n AI Agent tutorial Stack split: Claude Code vs n8nGet the free prompt pack →This post is part of the n8n AI agents hub: definitions, tutorials, workflow patterns, and the build-vs-run decision pages in one place.