n8n · error message

n8n: The resource you are requesting could not be found

ConfigurationHTTP 404Errors from external services

Last verified

The exact message
The resource you are requesting could not be found

What it means

n8n shows this when the service returned HTTP 404. The n8n docs attribute it in the HTTP Request node to an invalid endpoint URL, either through a typo or because the API version is deprecated. In app nodes, it often means an ID refers to a record that does not exist or is not visible to the credential.

It also appears during workflow activation when a trigger tries to register or look up something the service cannot find, which surfaces as a failed activation.

What is not wrong: authentication. With a bad credential the service would usually return 401 or 403.

What it looks like

The resource you are requesting could not be found
GET https://api.example.com/v1/contacts/{{ $json.id }}   <- check the id resolves

Why it happens

  • A typo or wrong version in the endpoint URL.
  • The API endpoint was deprecated or moved.
  • An expression produced an empty or wrong ID, so the URL points to nothing.
  • The record exists but is not shared with the connected account.

How to fix it

  1. Copy the final URL from the error details and compare it with the API documentation.
  2. Check that ID expressions resolve correctly for the failing item.
  3. Update the endpoint to the current API version.
  4. Confirm the connected account can see the record in the service's own interface.

How to stop it recurring

Pin API versions deliberately, validate IDs before lookup nodes, and subscribe to the API's deprecation notices. When a lookup is expected to miss sometimes, enable the node's continue-on-error setting or route the error output to a branch that handles the not-found case, so a missing record does not stop the whole execution.

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 "The resource you are requesting could not be found" mean in n8n?

n8n shows this when the service returned HTTP 404. The n8n docs attribute it in the HTTP Request node to an invalid endpoint URL, either through a typo or because the API version is deprecated. In app nodes, it often means an ID refers to a record that does not exist or is not visible to the credential.

How do I fix "The resource you are requesting could not be found"?

1. Copy the final URL from the error details and compare it with the API documentation. 2. Check that ID expressions resolve correctly for the failing item. 3. Update the endpoint to the current API version. 4. Confirm the connected account can see the record in the service's own interface.

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.