n8n-workflow-patterns

Match your trigger type to a pattern: use Webhook Processing for incoming HTTP events, HTTP API Integration for fetching external data, Database Operations for sync and ETL, AI Agent Workflow for tool-using chatbots, and Scheduled Tasks for recurring jobs.

Start with a Webhook trigger node, add a Set or Code node to transform the payload, then connect an output node like Slack or HTTP Request. Validate each node configuration, test with sample data, and activate the workflow after adding error handling.

Webhook data is nested under $json.body, so referencing $json.email fails while $json.body.email works. This is the most common gotcha when mapping incoming webhook fields in Set or Code nodes.

Add an Error Trigger node connected to a separate error-handling branch, use IF nodes to check error conditions, or enable Continue On Fail per node. Every production workflow should include an error path such as a Slack notification on failure.

Yes, use the Split In Batches node with a loop back connection to process items in chunks, such as 100 records at a time. This loop pattern prevents timeouts when syncing or transforming large database result sets.

Avoid branching, parallel, or multi-agent structures when a simple linear trigger-transform-action flow solves the problem. The Skill recommends starting with the simplest pattern and iterating rather than building complex workflows in one shot.