n8n Workflow Patterns helps an agent choose and build the right structure before it places a single node. It describes six patterns: webhook processing, HTTP API integration, database operations, AI agent workflows, scheduled tasks and batch processing.
The skill adds a guide for picking between them, a planning and deployment checklist, data flow shapes, a native-nodes-first rule for transformation, and gotchas for Google Sheets and Google Drive. One guide per pattern sits beside it.
What You Get
- Six pattern guides with node chains such as Webhook, Validate, Transform, Respond
- A selection guide that matches each pattern to the situations it fits
- A workflow creation checklist for planning, implementation, validation and deployment
- Batch processing advice: choosing a batchSize, carrying data across iterations, nested loops and API pagination
- Integration notes for Google Sheets and Google Drive, plus common gotchas such as webhook data structure and multiple input items
Common Use Cases
- Planning a webhook that receives a payment event, updates a database and sends a confirmation
- Designing a scheduled job that fetches API data, processes it and logs the result
- Building an AI agent workflow with a model, tools and memory
- Processing a large dataset in batches while respecting API rate limits
- Checking a finished workflow for connection mistakes before activating it
What Makes It Unique
The patterns are tied to a set of rules that keep workflows small: use a native node before a Code node, keep a Set node only as a named step, and let n8n run per-item by default. The lifecycle section adds a step many guides skip, which is reading the connections object directly after validation, because a green validation does not prove the wiring is right.
Under The Hood
The skill is instructions only with no scripts. The agent loads SKILL.md and opens a pattern guide when it needs one. While following it the agent calls n8n-mcp tools: validating a workflow, fetching it from the connected n8n instance, running a test and finally activating it with a partial update. Testing runs real nodes, so calls to external services and writes can happen. Patterns that call APIs or databases are built from HTTP Request and database nodes inside n8n.