n8n · HTTP Request node
Forbidden - perhaps check your credentials (HTTP Request)
Short answer
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.
VerifiedLast verified
01Error text
Forbidden - perhaps check your credentials02Likely causes
- The selected credentials cannot authenticate, or lack the permissions or scopes for the operation.
03How to fix it
- Review the selected credentials and make sure you can authenticate with them.
- Update permissions or scopes so that your API key or account can perform the operation you've selected.
- Format your generic credential in a different way, or generate a new API key or token with the appropriate permissions or scopes.
04Official documentation
→Related errors
- 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.
- 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.
- 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.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for n8n work:Open n8n jobsn8n rates and salaries