n8n · error message

n8n: Forbidden - perhaps check your credentials

ConfigurationHTTP 403Errors from external services

Last verified

The exact message
Forbidden - perhaps check your credentials

What it means

n8n shows this when the service returned HTTP 403. The n8n docs explain it as authentication failing or the credential lacking permission for the operation. The request reached the right endpoint, but the service refused it for this credential.

Most often the credential is valid but under-scoped: an OAuth app missing a scope, an API key with read-only rights used for a write, or a user without access to a specific resource. Sometimes the generic credential type in n8n does not send the header in the format the API expects. When n8n calls a website rather than an API, a 403 can also be the site's bot protection; see HTTP 403.

What is not wrong: the URL and usually the request body.

What it looks like

Forbidden - perhaps check your credentials
errorDetails: { "httpCode": "403" }

Why it happens

  • The token or key lacks the scope or permission for this operation.
  • The connected user has no access to the specific resource (sheet, channel, repository).
  • The generic credential sends authentication in the wrong format.
  • The API key was revoked or regenerated.
  • A website's firewall blocks the n8n server.

How to fix it

  1. Read the service's response body in the error details for the specific permission.
  2. Add the missing scopes or permissions in the service's app settings and reconnect the credential.
  3. Check that the connected user can access the resource.
  4. Verify the authentication format (header name, Bearer prefix) against the API docs.
  5. Generate a new key or token if the current one may be revoked.

How to stop it recurring

Create credentials with the documented scopes for each operation, use service accounts that own the resources, and test credentials after changing permissions.

Official documentation: docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/common-issues. See all n8n error messages or the n8n limits and quotas.

Related errors

Definitions

Quick answers

What does "Forbidden - perhaps check your credentials" mean in n8n?

n8n shows this when the service returned HTTP 403. The n8n docs explain it as authentication failing or the credential lacking permission for the operation. The request reached the right endpoint, but the service refused it for this credential.

How do I fix "Forbidden - perhaps check your credentials"?

1. Read the service's response body in the error details for the specific permission. 2. Add the missing scopes or permissions in the service's app settings and reconnect the credential. 3. Check that the connected user can access the resource. 4. Verify the authentication format (header name, Bearer prefix) against the API docs. 5. Generate a new key or token if the current one may be revoked.

Error handling you can see in the workflow

Autonoly workflows have per-node retries, timeouts, continue-on-fail and error-handler branches, so a failing step can be retried or routed instead of stopping the whole run. Saved workflows have no loop node; lists are worked through by the AI agent or one run per trigger item.

Also see Visual workflow builder.