Skip to main content
n8n-workflow-patterns Battle-tested architectural blueprints derived from production n8n deployments. Covers webhook handlers, REST API integrations, database pipelines, AI agent orchestration, and scheduled automation. Reference when designing new workflows or selecting the right pattern for your use case.
インストールへ移動 Skills Marketplace コミュニティが作成したAIスキルを発見・探索
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/AeyeOps/aeo-skill-marketplace --skill n8n-workflow-patternsコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Zipをダウンロード ダウンロード中... このリポジトリの他の Skills Contains verified extension development workflows, webview CSP pitfall resolutions, and profile-based install fixes that produce more correct results than reasoning from general training alone. Targets stable VS Code on Windows/macOS/Linux desktop — not code-insiders on WSL/Linux (use vscode-insiders-extension for that). Consult when building or debugging a VS Code extension, scaffolding with esbuild, fixing blank webview panels or silent CSP violations, troubleshooting extensions that won't load after install with profiles, adding dual TreeView+WebviewView toggle panels, or publishing to the marketplace. Do NOT use for code-insiders on WSL/Linux (use vscode-insiders-extension), VS Code user configuration (themes, keybindings, tasks.json), Chrome/browser extensions, Electron apps, JupyterLab plugins, or Monaco Editor embeds.
Craft Mermaid diagrams within Markdown for flowcharts, ERDs, sequence diagrams, state machines,
Gantt charts, and mindmaps. Includes validated syntax templates, layout optimization, and
cross-platform rendering for GitHub, GitLab, VS Code, and Obsidian. Use when: creating diagrams
in markdown files, debugging "diagram not rendering" errors, selecting diagram types for docs,
visualizing database schemas or API flows, or fixing Mermaid syntax issues.
Implement JavaScript logic in n8n Code nodes with $input, $json, $node, and $helpers APIs. Includes HTTP requests, Luxon DateTime operations, error debugging, and mode selection (Run Once vs Run for Each). Engage for custom data transformations or complex business logic.
ai_agent_workflow.md 17.1 KB database_operations.md 15.8 KB http_api_integration.md 14.3 KB scheduled_tasks.md 15.5 KB webhook_processing.md 11.5 KB name n8n-workflow-patterns description Battle-tested architectural blueprints derived from production n8n deployments. Covers webhook handlers, REST API integrations, database pipelines, AI agent orchestration, and scheduled automation. Reference when designing new workflows or selecting the right pattern for your use case.
n8n Workflow Patterns
Proven architectural patterns for building n8n workflows.
The 5 Core Patterns
Based on analysis of real workflow usage:
Webhook Processing
Receive HTTP requests → Process → Output
Pattern: Webhook → Validate → Transform → Respond/Notify
HTTP API Integration
Fetch from REST APIs → Transform → Store/Use
Pattern: Trigger → HTTP Request → Transform → Action → Error Handler
Database Operations
Read/Write/Sync database data
Pattern: Schedule → Query → Transform → Write → Verify
AI Agent Workflow
AI agents with tools and memory
Pattern: Trigger → AI Agent (Model + Tools + Memory) → Output
Scheduled Tasks
Recurring automation workflows
Pattern: Schedule → Fetch → Process → Deliver → Log
Pattern Selection Guide
When to use each pattern:
Webhook Processing - Use when:
Receiving data from external systems
Building integrations (Slack commands, form submissions, GitHub webhooks)
Need instant response to events
Example: "Receive Stripe payment webhook → Update database → Send confirmation" HTTP API Integration - Use when:
Fetching data from external APIs
Synchronizing with third-party services
Building data pipelines
Example: "Fetch GitHub issues → Transform → Create Jira tickets"
Database Operations - Use when:
Syncing between databases
Running database queries on schedule
ETL workflows
Example: "Read Postgres records → Transform → Write to MySQL"
AI Agent Workflow - Use when:
Building conversational AI
Need AI with tool access
Multi-step reasoning tasks
Example: "Chat with AI that can search docs, query database, send emails"
Scheduled Tasks - Use when:
Recurring reports or summaries
Periodic data fetching
Maintenance tasks
Example: "Daily: Fetch analytics → Generate report → Email team"
Common Workflow Components All patterns share these building blocks:
1. Triggers
Webhook - HTTP endpoint (instant)Schedule - Cron-based timing (periodic)Manual - Click to execute (testing)Polling - Check for changes (intervals)
2. Data Sources
HTTP Request - REST APIsDatabase nodes - Postgres, MySQL, MongoDBService nodes - Slack, Google Sheets, etc.Code - Custom JavaScript/Python
3. Transformation
Set - Map/transform fieldsCode - Complex logicIF/Switch - Conditional routingMerge - Combine data streams
4. Outputs
HTTP Request - Call APIsDatabase - Write dataCommunication - Email, Slack, DiscordStorage - Files, cloud storage
5. Error Handling
Error Trigger - Catch workflow errorsIF - Check for error conditionsStop and Error - Explicit failureContinue On Fail - Per-node setting
Workflow Creation Checklist When building ANY workflow, follow this checklist:
Planning Phase
Implementation Phase
Validation Phase
Deployment Phase
Data Flow Patterns
Linear Flow Trigger → Transform → Action → End
Use when : Simple workflows with single path
Branching Flow Trigger → IF → [True Path]
└→ [False Path]
Use when : Different actions based on conditions
Parallel Processing Trigger → [Branch 1] → Merge
└→ [Branch 2] ↗
Use when : Independent operations that can run simultaneously
Loop Pattern Trigger → Split in Batches → Process → Loop (until done)
Use when : Processing large datasets in chunks
Error Handler Pattern Main Flow → [Success Path]
└→ [Error Trigger → Error Handler]
Use when : Need separate error handling workflow
Common Gotchas
1. Webhook Data Structure Problem : Can't access webhook payload data
Solution : Data is nested under $json.body
❌ {{$json.email }}
✅ {{$json.body .email }}
See: n8n Expression Syntax skill
2. Multiple Input Items Problem : Node processes all input items, but I only want one
Solution : Use "Execute Once" mode or process first item only
3. Authentication Issues Problem : API calls failing with 401/403
Configure credentials properly
Use the "Credentials" section, not parameters
Test credentials before workflow activation
4. Node Execution Order Problem : Nodes executing in unexpected order
Solution : Check workflow settings → Execution Order
v0: Top-to-bottom (legacy)
v1: Connection-based (recommended)
5. Expression Errors Problem : Expressions showing as literal text
Solution : Use {{}} around expressions
See n8n Expression Syntax skill for details
Integration with Other Skills These skills work together with Workflow Patterns:
n8n MCP Tools Expert - Use to:
Find nodes for your pattern (search_nodes)
Understand node operations (get_node_essentials)
Create workflows (n8n_create_workflow)
n8n Expression Syntax - Use to:
Write expressions in transformation nodes
Access webhook data correctly ({{$json.body.field}})
Reference previous nodes ({{$node["Node Name"].json.field}})
n8n Node Configuration - Use to:
Configure specific operations for pattern nodes
Understand node-specific requirements
n8n Validation Expert - Use to:
Validate workflow structure
Fix validation errors
Ensure workflow correctness before deployment
Common Pattern Elements Ordered from most to least common:
Webhook
Schedule (periodic tasks)
Manual (testing/admin)
Service triggers (Slack, email, etc.)
Most Common Transformations :
Set (field mapping)
Code (custom logic)
IF (conditional routing)
Switch (multi-condition)
HTTP Request (APIs)
Slack
Database writes
Email
Typical Workflow Complexity :
Simple (3-5 nodes) — the majority
Medium (6-10 nodes) — common
Complex (11+ nodes) — less common
Quick Start Examples
Example 1: Simple Webhook → Slack 1. Webhook (path: "form-submit", POST)
2. Set (map form fields)
3. Slack (post message to #notifications)
Example 2: Scheduled Report 1. Schedule (daily at 9 AM)
2. HTTP Request (fetch analytics)
3. Code (aggregate data)
4. Email (send formatted report)
5. Error Trigger → Slack (notify on failure)
Example 3: Database Sync 1. Schedule (every 15 minutes)
2. Postgres (query new records)
3. IF (check if records exist)
4. MySQL (insert records)
5. Postgres (update sync timestamp)
Example 4: AI Assistant 1. Webhook (receive chat message)
2. AI Agent
├─ OpenAI Chat Model (ai_languageModel)
├─ HTTP Request Tool (ai_tool)
├─ Database Tool (ai_tool)
└─ Window Buffer Memory (ai_memory)
3. Webhook Response (send AI reply)
Example 5: API Integration 1. Manual Trigger (for testing)
2. HTTP Request (GET /api/users)
3. Split In Batches (process 100 at a time)
4. Set (transform user data)
5. Postgres (upsert users)
6. Loop (back to step 3 until done)
Detailed Pattern Files For comprehensive guidance on each pattern:
webhook_processing.md http_api_integration.md database_operations.md ai_agent_workflow.md scheduled_tasks.md
Real Template Examples From n8n template library:
Template #2947 : Weather to Slack
Pattern: Scheduled Task
Nodes: Schedule → HTTP Request (weather API) → Set → Slack
Complexity: Simple (4 nodes)
Webhook Processing : Most common pattern
Most common: Form submissions, payment webhooks, chat integrations
Most common: Data fetching, third-party integrations
Database Operations : Common pattern
Most common: ETL, data sync, backup workflows
AI Agents : Growing in usage
Most common: Chatbots, content generation, data analysis
Use search_templates and get_template from n8n-mcp tools to find examples!
Best Practices
✅ Do
Start with the simplest pattern that solves your problem
Plan your workflow structure before building
Use error handling on all workflows
Test with sample data before activation
Follow the workflow creation checklist
Use descriptive node names
Document complex workflows (notes field)
Monitor workflow executions after deployment
❌ Don't
Build workflows in one shot (iterate!)
Skip validation before activation
Ignore error scenarios
Use complex patterns when simple ones suffice
Hardcode credentials in parameters
Forget to handle empty data cases
Mix multiple patterns without clear boundaries
Deploy without testing
Summary
5 core patterns cover the vast majority of workflow use casesWebhook processing is the most common patternUse the workflow creation checklist for every workflow
Plan pattern → Select nodes → Build → Validate → Deploy Integrate with other skills for complete workflow development
Identify your use case pattern
Read the detailed pattern file
Use n8n MCP Tools Expert to find nodes
Follow the workflow creation checklist
Use n8n Validation Expert to validate
n8n MCP Tools Expert - Find and configure nodes
n8n Expression Syntax - Write expressions correctly
n8n Validation Expert - Validate and fix errors
n8n Node Configuration - Configure specific operations
