mcpField
N
n8n-code-javascript

n8n-code-javascript

github.com/sickn33Development49.2k70 installsUpdated today
Repository

About n8n-code-javascript

A guidance skill for writing JavaScript in n8n Code nodes, aimed at workflow authors handling logic that exceeds simpler nodes. It covers when to use the node and calls out prerequisites and validation requirements.

Key features

  1. 01Complex data transformations
  2. 02Custom calculations and business logic
  3. 03Recursive and multi-step conditional logic
  4. 04Parsing complex API responses
  5. 05Aggregating data across items

Use cases

  1. 01Implementing complex steps in workflows
  2. 02Parsing nested API responses
  3. 03Aggregating data from multiple items

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sickn33/agentic-awesome-skills --skill n8n-code-javascript

After installing, type/n8n-code-javascriptin Claude Code to confirm it loaded.

Bundled filesreferences/detailed-guide.md

Details

From the project README

JavaScript Code Node

Expert guidance for writing JavaScript code in n8n Code nodes.


Detailed Guide

Read the detailed guide before executing this skill. It retains the complete procedure and reference material. Treat its safety, prerequisites, and validation requirements as mandatory. For focused work, load the relevant sections; for end-to-end work, read the guide completely.

When to Use Code Node

Use Code node when:

  • ✅ Complex transformations requiring multiple steps
  • ✅ Custom calculations or business logic
  • ✅ Recursive operations
  • ✅ API response parsing with complex structure
  • ✅ Multi-step conditionals
  • ✅ Data aggregation across items

Consider other nodes when:

  • ❌ Simple field mapping → Use Set node
  • ❌ Basic filtering → Use Filter node
  • ❌ Simple conditionals → Use IF or Switch node
  • ❌ HTTP requests only → Use HTTP Request node

Code node excels at: Complex logic that would require chaining many simple nodes


Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Comments

Markdown supported