Skip to content
New: a free website for your business, live in 48 to 72 hoursWorkflow automation on n8n and Claude, built for your businessFixed price, agreed before we start · Live in 5 to 10 business days30-day money-back guarantee on every planProfessional firms · Agencies · E-commerceYou own every workflow, in your own n8nClaude API: your data is not used for trainingHuman approval on every sensitive stepFree automation audit, no obligation
PURIST
30 days
Money-back window
14 h/wk
Modeled time saved
99.97%
Uptime SLA
< 7 days
Deploy time
PURIST AI
Claude Opus 4.7 · n8n v1.71 · <80ms
What type of business are you running? I'll show you exactly which processes we'd automate first and your estimated ROI.
Powered by n8n + Claude Opus 4.7 Get my free automation plan →

Free Tools /Development

HTTP Status Code Explainer for Automations

Type an error code from a failed workflow: see what it means, what to change, and whether to retry.

  • Free, no signup
  • Runs in your browser
  • Nothing stored
Inputs
Result Updates as you type · runs in your browser

Calculating…

Who uses it, and for what

n8n builder

A node failed with 422: find out it is a validation error and which field to check.

Ops

Decide which errors to retry automatically and which should alert a person.

Beginner

Understand API errors without reading the HTTP specification.

How this tool works

01

Plain-language meaning

Each code is explained in terms of what went wrong in your workflow.

02

A concrete fix

What to change in the node, the credential or the data.

03

Retry or not

Temporary errors (408, 429, 5xx) should be retried with backoff; others need a fix first.

Guide

What do the HTTP status code families mean?

1xx codes are informational, 2xx mean success (200 OK, 201 Created, 204 No Content), 3xx are redirects (301 moved permanently, 302 and 307 temporary, 304 not modified), 4xx mean the request was wrong or not allowed, and 5xx mean the server failed. The first digit tells you whose problem it is: 4xx is usually yours to fix, 5xx is the server’s.

Which errors should a workflow retry?

Retry 429 Too Many Requests (after the delay given in the Retry-After header if there is one), 502, 503 and 504, and network timeouts: they are usually temporary. Do not retry 400, 401, 403, 404 or 422 without changing something, because the same request will fail the same way. A 401 usually means an expired or missing token; a 403 means the credentials are valid but lack permission.

What is the difference between 400 and 422?

400 Bad Request means the server could not read the request (invalid JSON, wrong content type). 422 Unprocessable Content means it read it but the data failed validation, such as a missing required field or an invalid email. The response body usually says which field.

Frequently asked questions

Should I retry every failed request?

No. Retrying a 400 or 401 repeats the same failure. Retry only timeouts, rate limits and server errors, with increasing delays.

What is the difference between 401 and 403?

401: the API does not know who you are (missing or expired credentials). 403: it knows you, but you are not allowed to do this.

Where is the real error message?

In the response body. In n8n, enable "Include response headers and status" or "Never error" to inspect it.

What does 429 Too Many Requests mean?

You hit the API’s rate limit. Wait, ideally for the time in the Retry-After header, then retry, and spread requests out with batching or a delay between calls.

Is a 3xx redirect an error?

No, but some HTTP clients do not follow redirects by default, so a workflow may receive the 301 or 302 instead of the final page. Enable redirect following or call the final URL directly.

Done for you

Want this running inside your business, automatically?

We build the workflow behind tools like this one, wired to your CRM, inbox and apps, and keep it running. Fixed price, from $390 a month.