n8n-workflow-patterns

Use the pattern Webhook → Validate → Transform → Action → Response. Remember that incoming data is nested under $json.body, not $json directly, and choose between onReceived and lastNode response modes based on whether you need a custom response.

Connect any n8n node to the AI Agent via the ai_tool port, not the main port. Provide a clear tool name and description since the AI uses descriptions to decide when to call each tool, and add memory via the ai_memory port for conversations.

The five core patterns are webhook processing (35% of triggers), scheduled tasks (28%), HTTP API integration, database operations, and AI agent workflows. Together they cover over 90% of real workflow use cases.

Always use parameterized queries with placeholders like $1 and pass values through the parameters array instead of string concatenation. Also create a least-privilege database user with only the permissions the workflow needs.

Webhook payload data is nested under $json.body, so {{$json.email}} fails while {{$json.body.email}} works. Headers, URL parameters, and query strings are similarly accessed via $json.headers, $json.params, and $json.query.

Use a loop pattern with offset-based, cursor-based, or Link-header pagination depending on the API. Combine Split In Batches with a Set node that tracks the current page or cursor, and loop until no more results are returned.