n8n-code-javascript

To return data from an n8n Code node correctly, you must structure your JavaScript output as an array of objects using the required `[{ json: ... }]` format. This ensures downstream nodes can parse the transformed items reliably without workflow errors.

You can access webhook body data inside an n8n Code node by referencing the payload via `.body` on the input item. Combine this with `$input` and `$node` conventions to properly shape webhook payloads and merge data from previous workflow nodes.

Yes, you can use Luxon `DateTime` for date logic and `$helpers.httpRequest()` for HTTP calls inside n8n Code nodes. You can also use `$jmespath()` for JSON querying to perform complex data transformation within your workflow automation.

The best way to aggregate and filter items in an n8n Code node is to apply production-grade JavaScript patterns using `$input` conventions. This approach handles batching, loop semantics, and accumulates results across iterations while safely managing missing fields.

An n8n Code node often fails when transforming multiple items if the JavaScript does not follow n8n-specific safety rules or return results in the required array structure. Avoid common runtime mistakes by using `$json` patterns and wrapping output objects correctly.