fpFLOWPATCHn8n × HubSpot Error DeskFind your error →
Guides / Integrations / n8n Core
Integration desk

n8n Core Error Desk

Fixes for n8n itself — the failures that stop a workflow regardless of which app it talks to.

Debugging

HTTP debugging flow showing n8n request authentication, headers, upstream gateway, status codes, retries, and response body.
Debugging•12 min

HTTP 401/403/500 Debugging

Debug n8n HTTP Request 401, 403, and 500 errors by exposing the real response body, fixing auth and payload shape, then retrying only transient failures.

Open fix →

Error Handling

Diagram showing a production workflow failure flowing into an n8n Error Trigger, alert branch, and optional Stop And Error node.
Error Handling•12 min

Error Workflow Not Firing

Fix n8n Error Workflows that never fire by testing production runs, assigning the handler correctly, avoiding swallowed errors, and validating trigger payloads.

Open fix →

Platform Differences

Comparison diagram of n8n Cloud and self-hosted execution environments, community nodes, storage, payload limits, URLs, and versions.
Platform Differences•13 min

Cloud vs Self-Hosted Errors

Find why an n8n workflow works on Cloud but fails self-hosted by comparing node availability, binary storage, payload limits, environment URLs, memory, and versions.

Open fix →

Reliability

Diagram of an n8n execution moving through running, waiting, sub-workflow, worker, timeout, and stop states.
Reliability•13 min

Execution Stuck Running

Diagnose n8n executions stuck Running or timing out by separating Wait states, sub-workflows, worker failures, timeout settings, and stale execution state.

Open fix →

Triggers & Webhooks

Diagram showing n8n test and production webhook paths, activation state, reverse proxy, and response modes.
Triggers & Webhooks•12 min

Webhook Test vs Production

Fix n8n webhooks that return 404 or never fire by checking test vs production URLs, publish state, HTTP method, reverse-proxy path, and response mode.

Open fix →