File size: 4,695 Bytes
0a84888 | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 | ---
#https://www.notion.so/n8n/Frontmatter-432c2b8dff1f43d4b1c8d20075510fe4
title: Code node common issues
description: Documentation for common issues and questions in the Code node in n8n, a workflow automation platform. Includes details of the issue and suggested solutions.
contentType: [integration, reference]
priority: high
---
# Code node common issues
Here are some common errors and issues with the [Code node](/integrations/builtin/core-nodes/n8n-nodes-base.code/index.md) and steps to resolve or troubleshoot them.
<!-- vale off -->
## Code doesn't return items properly
<!-- vale on -->
This error occurs when the code in your Code node doesn't return data in the expected format.
In n8n, all data passed between nodes is an array of objects. Each of these objects wraps another object with the `json` key:
```javascript
[
{
"json": {
// your data goes here
}
}
]
```
To troubleshoot this error, check the following:
* Read the [data structure](/data/data-structure.md) to understand the data you receive in the Code node and the requirements for outputting data from the node.
* Understand how data items work and how to connect data items from previous nodes with [item linking](/data/data-mapping/data-item-linking/index.md).
<!-- vale off -->
## A 'json' property isn't an object
<!-- vale on -->
This error occurs when the Code node returns data where the `json` key isn't pointing to an object.
This may happen if you set `json` to a different data structure, like an array:
```javascript
[
{
"json": [
// Setting `json` to an array like this will produce an error
]
}
]
```
To resolve this, ensure that the `json` key references an object in your return data:
```javascript
[
{
"json": {
// Setting `json` to an object as expected
}
}
]
```
## Code doesn't return an object
This error may occur when your Code node doesn't return anything or if it returns an unexpected result.
To resolve this, ensure that your Code node returns the [expected data structure](/data/data-structure.md):
```javascript
[
{
"json": {
// your data goes here
}
}
]
```
This error may also occur if the code you provided returns `'undefined'` instead of the expected result. In that case, ensure that the data you are referencing in your Code node exists in each execution and that it has the structure your code expects.
## 'import' and 'export' may only appear at the top level
This error occurs if you try to use `import` or `export` in the Code node. These aren't supported by n8n's JavaScript sandbox. Instead, use the `require` function to load modules.
To resolve this issue, try changing your `import` statements to use `require`:
```javascript
// Original code:
// import express from "express";
// New code:
const express = require("express");
```
<!-- vale off -->
## Cannot find module '<module>'
<!-- vale on -->
This error occurs if you try to use `require` in the Code node and n8n can't find the module.
/// warning | Only for self-hosted
n8n doesn't support importing modules in the [Cloud](/manage-cloud/overview.md) version.
///
If you're [self-hosting](/hosting/index.md) n8n, follow these steps:
* Install the module into your n8n environment.
* If you are running n8n with [npm](/hosting/installation/npm.md), install the module in the same environment as n8n.
* If you are running n8n with [Docker](/hosting/installation/docker.md), you need to extend the official n8n image with a [custom image](https://docs.docker.com/build/building/base-images/){:target=_blank .external-link} that includes your module.
* Set the `NODE_FUNCTION_ALLOW_BUILTIN` and `NODE_FUNCTION_ALLOW_EXTERNAL` [environment variables](/hosting/configuration/configuration-examples/modules-in-code-node.md) to allow importing modules.
## Using global variables
Sometimes you may wish to set and retrieve simple global data related to a workflow across and within executions. For example, you may wish to include the date of the previous report when compiling a report with a list of project updates.
To set, update, and retrieve data directly to a workflow, use the [static data](/code/cookbook/builtin/get-workflow-static-data.md) functions within your code. You can manage data either globally or tied to specific nodes.
/// info | Use Remove Duplicates when possible
If you're interested in using variables to avoid processing the same data items more than once, consider using the [Remove Duplicates node](/integrations/builtin/core-nodes/n8n-nodes-base.removeduplicates/index.md) instead. The Remove Duplicates node can save information across executions to avoid processing the same items multiple times.
///
|