n8n errors
Common n8n errors, grouped by component. Open one for the exact error text, its likely causes, the fix and the official documentation.
- Errors
- 33
- Components
- 16
- Verified
- 33
- Official docs
- docs.n8n.io
33 errors in 16 groups
AI Agent node4
- A Chat Model sub-node must be connectedThis n8n AI Agent error displays when n8n tries to execute the node without a Chat Model connected. Click the + Chat Model button at the bottom of the screen when the node is open, or the Chat Model + connector when the node is closed, and pick a Chat Model.
- Error in sub-node Simple MemoryThis n8n AI Agent error displays when n8n runs into an issue with the Simple Memory sub-node, most often an older version of the node. Remove the Simple Memory node from your workflow and add it again, so that you use the latest version of the node.
- Internal error: 400 Invalid value for 'content'This n8n AI Agent error can occur if the Prompt input contains a null value. Make sure your expressions reference valid fields and resolve to valid input rather than null.
- No prompt specifiedThis n8n AI Agent error occurs when the agent expects to get the prompt from the previous node automatically. Find the Prompt parameter of the AI Agent node and change it from Connected Chat Trigger Node to Define below, then build the prompt manually.
Airtable node2
- Forbidden - perhaps check your credentials (Airtable)This n8n Airtable error displays when you try to perform actions not permitted by your current level of access. Give the Airtable credential the scopes it requires on the resources you manage.
- Service is receiving too many requests from you (Airtable)This n8n Airtable error is a 429 from Airtable, which has a hard API limit on requests made with personal access tokens. Wait 30 seconds before resuming requests.
Code node5
- 'import' and 'export' may only appear at the top levelThis n8n Code node error occurs if you use import or export, which the n8n JavaScript sandbox does not support. Change your import statements to use require, for example const express = require("express");.
- A 'json' property isn't an objectThis n8n Code node error occurs when the node returns data where the json key does not point to an object. Make sure that the json key references an object in your return data.
- Cannot find module '<module>'This n8n Code node error occurs if you use require and n8n cannot find the module. On self-hosted n8n, install the module into your n8n environment. With npm, install it in the same environment as n8n. With Docker, extend the official n8n image with a custom image that includes your module.
- Code doesn't return an objectThis n8n Code node error may occur when the node does not return anything or returns an unexpected result. Make sure that the Code node returns the expected data structure. n8n expects an array of objects, each wrapping another object under the json key.
- Code doesn't return items properlyThis n8n Code node error occurs when the code does not return data in the expected format. Return an array of objects in which each object wraps your data under the json key.
Discord node1
Execute Command node2
- Command failed: <command> /bin/sh: <command>: not foundThis n8n Execute Command error occurs when the shell environment cannot find one of the commands in the Command parameter. Check that the command and its arguments don't have typos in the Command parameter.
- Error: stdout maxBuffer length exceededThis n8n Execute Command error happens when your command returns more output than the node can process at one time. Reduce the output your command produces. Check the command's documentation for flags that limit or filter output.
Gmail and Gmail Trigger nodes1
Gmail node2
- Bad request - please check your parameters (Gmail)This n8n Gmail error most often occurs if you enter a Message ID, Thread ID or Label ID that does not exist. Try a Get operation with the ID to confirm it exists.
- Forbidden - perhaps check your credentials (Gmail)This n8n Gmail error displays next to certain dropdowns in the node, such as Label Names or IDs. Turn on Impersonate a User in the Google Service Account credential.
Google Sheets node1
HTTP Request node7
- 429 - The service is receiving too many requests from youThis n8n HTTP Request error displays when the node receives a 429 from the service you are calling, which often means you have hit its rate limits. Use Batching. In the HTTP Request node, select Add Option > Batching, set Items per Batch, and set Batch Interval (ms) to add a delay between requests.
- Bad request - please check your parametersThis n8n HTTP Request error displays when the node receives a 400 error indicating a bad request. Review the API documentation for your service to format your query parameters.
- Connection refused (ECONNREFUSED)ECONNREFUSED in the n8n HTTP Request node means the node reached a host but the target port has no listener, most often because of Docker networking on self-hosted n8n. Address the target by a name the container can route to, such as host.docker.internal or the Compose service name.
- Forbidden - perhaps check your credentials (HTTP Request)This n8n HTTP Request error displays when the node receives a 403 error indicating authentication failed. Review the selected credentials and make sure you can authenticate with them.
- JSON parameter need to be an valid JSONThis n8n HTTP Request error displays when you pass a parameter as JSON and it is not formatted as valid JSON. Test your JSON in a JSON checker or syntax parser to find errors.
- The resource you are requesting could not be foundThis n8n HTTP Request error displays when the endpoint URL you entered is invalid. Refer to your service's API documentation to verify you have a valid endpoint.
- Unsupported media type (415) when you send a fileThis n8n HTTP Request error displays when the API expects multipart/form-data but the request body is not multipart. Set Body Content Type to Form-Data.
Ollama Chat Model node1
Question and Answer Chain node1
Schedule Trigger node1
Telegram Trigger and Google Sheets Trigger nodes1
Telegram Trigger node1
Webhook node2
- 524 timeout on n8n Cloud webhooksAn incoming webhook request on n8n Cloud fails with a 524 status code if your webhook does not respond within 100 seconds. For long-running processes, introduce polling logic with two separate webhooks.
- Only one webhook per path and methodn8n shows this message because it only permits registering one webhook for each path and HTTP method combination. Unpublish the workflow with the conflicting webhook.
WhatsApp Business Cloud node1
More for n8n work:Open n8n jobsn8n rates and salaries
The iPaaS Brief
Subscribe to The iPaaS Brief.
The iPaaS newsletter for the people who run integrations. From iPaaS Group.
Free. You finish on theipaasbrief.com and confirm by email.