n8n Workflow Examples#
This directory contains n8n workflow examples organized by difficulty level to support progressive learning.
Directory Structure#
1 2 3 4 5 | |
Difficulty Levels#
π’ Easy (17 workflows)#
Perfect for beginners - Simple workflows with 1-12 nodes, single integrations, and straightforward logic.
Examples:
- easy-easyslip.json - Basic OCR processing
- easy-telegram-basic.json - Simple Telegram bot
- easy-form-submission.json - Basic form handling
- easy-hass.json - Home Assistant integration
π‘ Medium (23 workflows)#
Intermediate level - Moderate complexity with 4-31 nodes, multiple integrations, and some conditional logic.
Examples:
- medium-scrape-website.json - Web scraping automation
- medium-email-attachments-analyzer.json - Email processing with AI
- medium-hr.json - HR workflow automation
- medium-line-download-to-google-drive-easy.json - LINE to Drive integration
π΄ Hard (9 workflows)#
Advanced level - Complex workflows with 15-78 nodes, AI/RAG implementations, vector databases, and sophisticated logic.
Examples:
- hard-rag-pgvector-form-multiple-file-upload.json - RAG with PGVector
- hard-rag-pdf-local-100.json - PDF RAG implementation
- hard-audience-reminder.json - Complex automation with 41 nodes
- hard-crm-manual-round-up.json - Advanced CRM with 78 nodes
Usage#
These workflows are referenced in the hands-on guides throughout the n8n course. Each workflow demonstrates specific concepts and techniques that build upon previous lessons.
Integration with Course Materials#
The workflows are designed to support the progressive learning structure of the course:
- Start with Easy workflows to understand basic n8n concepts
- Progress to Medium workflows to learn multi-service integrations
- Challenge with Hard workflows to master advanced AI and automation techniques
File Naming Convention#
All workflows follow the pattern: {difficulty}-{difficulty}-{descriptive-name}.json
- First prefix: Directory (easy/medium/hard)
- Second prefix: Difficulty level for clarity
- Descriptive name: Based on the workflow's actual name in the JSON
Documentation#
For detailed analysis of workflow complexity and renaming history, see:
- workflow_complexity_analysis.txt - Technical analysis of all workflows
- workflow_name_mapping.txt - Original to new filename mapping
- difficulty_rename_mapping.txt - Difficulty-based rename mapping
- workflow_completeness_analysis.txt - Completeness analysis of all workflows
- workflow_removal_plan.txt - Record of removed incomplete workflows
Quality Assurance#
This repository has undergone cleanup to remove incomplete and placeholder workflows: - 16 incomplete workflows removed - including test files, demos, and placeholder content - 49 complete workflows retained - ready for hands-on integration - All references updated - ensuring hands-on guides work with available workflows - Quality-focused selection - only production-ready workflows are included