ContactBook a call

Fix broken n8n

Fix an n8n workflow that has stopped, fails without warning or broke after an upgrade

We read your executions, find why workflows fail or never start, and fix them on n8n Cloud or your own server. Then we add an error workflow so a person hears about the next failure, and write down what each workflow does.

Start with
The $500 Automation Audit
We read
Executions, settings and hosting
Access
Member access, never your password

In short

n8n records each run in the executions list, and an error workflow, started by an Error Trigger node, runs when an execution fails. Many workflows we see have no error workflow set, so failures sit in the list unread. On self-hosted n8n there is more to go wrong: a webhook URL that is wrong behind a reverse proxy, queue mode routing, and major version upgrades with breaking changes. We find the cause, fix it in your instance and set up alerts.

What we hear about n8n

  • The workflow stopped and nobody noticed until a customer did.
  • Webhooks work in testing but not in production.
  • Things broke after we upgraded n8n.
  • A credential expired and every run since has failed.
  • The AI agent node loops or stops calling its tools.

Why n8n workflows fail, and where to look

The platform behaviour below comes from the n8n docs, listed under sources.

SymptomWhat n8n doesWhat we change
Failures nobody seesFailed runs appear in the executions list. An error workflow, set per workflow in its settings and started by an Error Trigger node, runs when an execution fails.Add one error workflow that alerts a named person with the workflow, node and a link to the execution.
Conditions that should failThe Stop and Error node can force an execution to fail under conditions you choose, which then starts the error workflow.Fail loudly on bad data, such as a missing email or an order with no total.
Webhooks behind a proxyBehind a reverse proxy, n8n runs on port 5678 internally but is reached on 443, so the public webhook URL has to be set by environment variable.Set the webhook URL and proxy settings, then re-register webhooks with the sending apps.
Queue mode routingIn queue mode, production webhook paths should route to webhook processors, and test webhooks to the main process.Check the load balancer rules, workers and Redis, and the order upgrades are applied in.
Broken after an upgraden8n publishes breaking changes and migration guides for each major version.Read the guide for your jump, test on a copy, then upgrade with a rollback plan.
CredentialsA credential that expires or is revoked at the other app makes every node that uses it fail.Move credentials to accounts the business owns, and alert on authentication errors.

How we fix an n8n instance

How we work in your account

What it costs

Every engagement starts with the audit, so you know what is broken and what it costs to fix before you commit to anything else. Payment by Stripe, PayPal, Wise, Razorpay, Infinity or bank transfer.

Full pricing · The audit · Care plans

Automation Audit
$500Credited in full to the fixes or the build. We read the run history, list every fault by risk and give you a fixed price in writing.
Fixes or rebuild
From $1,000Workflow builds and repairs start here. The statement of work fixes the price and the currency before we start.
Care plan
From $50 a monthMonitoring, error alerts, a monthly look at failed runs and small changes, after the fixes are live.
Automation team
$999 a monthFor a steady queue of smaller requests across several platforms and workflows.

Related pages

Questions buyers ask

Before anything changes, the Automation Audit gives you the fix list and a fixed price.

My n8n workflow stopped working. What should I check first?

Open the executions list and look at the last failed execution and the node that failed. If nothing is running at all, check the workflow is active, the trigger and its credentials, and on self-hosted n8n whether the webhook URL is right.

How do I get alerted when an n8n workflow fails?

Create an error workflow that starts with an Error Trigger node and sends a message, then set it as the error workflow in each workflow’s settings. One error workflow can serve many workflows.

Why do my n8n webhooks work in testing but not in production?

Test and production webhooks use different URLs, and the workflow has to be active for the production URL to respond. Behind a reverse proxy, the public webhook URL also has to be set by environment variable, or n8n shows its internal address.

Our n8n upgrade broke workflows. Can you help?

Yes. n8n publishes breaking changes for each major version. We check your workflows against them on a copy of your instance, fix what breaks, and then upgrade production with a rollback plan.

Do you fix self-hosted n8n as well as n8n Cloud?

Both. On self-hosted n8n we also look at the server, the database, queue mode and Redis if used, backups and the reverse proxy.

Why does my n8n AI agent stop due to max iterations or not call its tools?

Usually the prompt, the tool descriptions or the model choice. The agent runs out of steps before it finishes, or does not see a tool as relevant. We test the agent on real inputs and fix the set-up.

How much does it cost to fix an n8n workflow?

The $500 Automation Audit comes first and is credited in full to the fixes. You get a fixed price per fix in writing. Workflow builds and repairs start from $1,000.

Do you need my n8n password or server login?

For n8n we ask you to invite us as a member. For a self-hosted server we ask for our own user, which you can remove when we finish. We never ask for your own logins.

Can you take over n8n workflows someone else built?

Yes. We document each workflow, fix what is broken and hand over a runbook.

Platform behaviour changes with new releases. Checked against the official help pages on 16 November 2026. Sources:

Show us what is failing

On a triage call you show us the workflows that are failing and what they cost you, and we explain what the audit would cover. The call is free.

Book a triage call

Cookie preferences

Choose what this site may use on your device. You can change this at any time from “Cookie settings” in the footer.

Strictly necessary

Keep the site working and remember the choices you make here. These cannot be switched off, and none of them track you.

Always on
What this includes (4)
NameProvider PurposeDuration
sbd-consentThis site Remembers your cookie choices12 months
Vercel Web AnalyticsVercel Inc. Counts page views in aggregate. Sets no cookie and stores nothing on your deviceNone
ticker-dismissed, sbd-note-offThis site Remembers that you closed a notice or language tipUntil the tab closes
sbd-voice-resume, sbd-voice-prefillThis site Carries a voice conversation across pages, only if you start oneUntil the tab closes

Analytics

Tell us which pages are read and where visitors leave, so we can improve them. IP addresses are anonymised and nothing is used for advertising.

What this includes (2)
NameProvider PurposeDuration
_gaGoogle Analytics (Google LLC) Distinguishes visitors with a random ID13 months
_ga_FPXDMQPRV1Google Analytics (Google LLC) Keeps the session state for this site13 months

Functional

Embedded services that set their own cookies. Without them the site still works; you get a link to open the service instead.

What this includes (1)
NameProvider PurposeDuration
Booking calendarCal.com Inc. Shows live availability and books the call on the booking pageSet by Cal.com

Advertising

Not used. This site has no advertising, retargeting or social media tracking, and we never sell data.

Not used

Questions about your data: hello@smallbaydigital.com