czlonkowski/n8n-skills▌

Proven architectural patterns for building n8n workflows across five core use cases. \n \n Covers five foundational patterns: webhook processing, HTTP API integration, database operations, AI agent workflows, and scheduled tasks, each with specific triggers, transformations, and outputs \n Includes a pattern selection guide with real-world examples, helping developers choose the right architecture for their use case \n Provides a workflow creation checklist spanning planning, implementation, val

Write correct n8n expressions with double braces, proper variable syntax, and webhook data access patterns. \n \n Use {{}} syntax for all dynamic content; access current node data with $json , other nodes with $node[\"Node Name\"] , and webhook payloads from $json.body (not root) \n Node names are case-sensitive and require quotes; field names with spaces use bracket notation like $json['field name'] \n Code nodes use direct JavaScript access without {{}} braces; expressions don't work in webhoo

Expert guide for interpreting and fixing n8n validation errors. \n \n Covers three severity levels: errors (block execution), warnings (optional fixes), and suggestions (nice-to-have improvements) \n Includes five common error types with fix strategies: missing_required, invalid_value, type_mismatch, invalid_expression, and invalid_reference \n Provides three validation profiles (minimal, runtime, strict, ai-friendly) for different workflow stages, with runtime recommended for pre-deployment che

Write and debug JavaScript code in n8n Code nodes with proper data access and return formatting. \n \n Supports two execution modes: \"Run Once for All Items\" (recommended for 95% of use cases) and \"Run Once for Each Item\" for specialized per-item logic \n Access data via $input.all() , $input.first() , or $input.item ; always return array format [{json: {...}}] \n Built-in helpers include $helpers.httpRequest() for HTTP calls, DateTime (Luxon) for date operations, and $jmespath() for JSON qu

Operation-aware node configuration with progressive discovery and property dependency management. \n \n Start with get_node({detail: \"standard\"}) for 95% of configuration needs; escalate to full detail or search_properties mode only when standard doesn't provide required information \n Resource and operation determine which fields are required; use validation iteratively to discover conditional dependencies controlled by displayOptions rules \n Common patterns include resource/operation nodes

$22

$22