Running n8n?

n8n workflows or workers falling behind? We fix it.

Self-hosted n8n is a great deal right up until the point your workflows outgrow a single instance. Queue mode arrives, Redis gets angry, workers die quietly, and nobody remembers which node version a given workflow was built against. We put the workers, the Postgres, the queue and the credentials on a foundation that will not fall over at 3am.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

n8n-worker.log

still broken

What it is

n8n at a glance

n8n is an open-core workflow automation tool, self-hostable and licensed under its own Sustainable Use License. It covers the same ground as Zapier and Make, with a node-based visual editor on top of a worker process you run yourself, usually in Docker or on Kubernetes.

The attractive part is that executions do not cost per-operation; you pay for the compute and the operational time. At low scale a single Docker container runs everything, including the webhook listener, the editor, the workers and the SQLite database. At higher scale you split into queue mode with a Postgres database, Redis for the Bull queue, and separate worker containers that scale horizontally.

Type
Self-hostable workflow automation
First released
2019
License
Sustainable Use License (source-available), Enterprise license available
Maintained by
n8n GmbH
Typically used for
App integrations, data syncs, webhook handlers, internal automation

The honest version

n8n pros and cons

No technology is all upside. This is where n8n earns its place and where it tends to cause trouble.

Where n8n is strong

  • No per-operation billYou pay for compute and for your own time. At the volumes where Zapier and Make start to hurt, n8n usually costs a small fraction and will run inside your own network.
  • Over 400 built-in nodesMost SaaS integrations are covered out of the box, and the catalog grows every release, which removes most need for custom HTTP node plumbing.
  • Custom nodes in TypeScriptWhen you do need to build an integration, writing a node is straightforward TypeScript against a documented interface, not reverse engineering a closed platform.
  • Self-hosted means data stays homeFor regulated workflows the processing happens in your VPC, your database, your logging stack, which is often the reason enterprise teams pick it over hosted rivals.
  • Queue mode scales horizontallyWith Redis and Postgres behind it, n8n can run a webhook front end on one container and many worker containers behind, which is more than enough for serious production load.

Where n8n bites

  • You own the operationsNobody is going to upgrade your Postgres, rotate your encryption key, or wake up when a worker crashes. Self-hosting means self-operating, with everything that implies.
  • The Sustainable Use License is not OSI open sourceIt restricts commercial resale and some embedding cases. Enterprise features sit behind a separate paid license, which surprises teams that assumed n8n was fully free.
  • Encryption key loss is terminalIf the N8N_ENCRYPTION_KEY env changes or is lost, every stored credential becomes unreadable, and recovery means re-entering every credential by hand.
  • Queue mode is not optional at scalePast a few hundred executions per hour, the single-process mode becomes unstable, and the move to queue mode requires Redis, Postgres and operational discipline all at once.
  • Upgrade churn can break nodesMinor releases occasionally change node behavior, deprecate parameters or move modules. Workflows built on older versions sometimes need patching after an upgrade.
  • Observability is basic out of the boxExecution history exists in the database, but real metrics, log aggregation and alerting have to be bolted on with Prometheus, Loki or something similar.

Sound familiar?

Common n8n problems we fix

The n8n problems that bring people to us, and what you have once each one is fixed.

Redis ECONNREFUSED

Queue mode falls behind and nothing runs

Redis unreachable, the Bull queue backing up, and workers sitting idle because they cannot pick up jobs. Webhooks still accept but nothing moves.

Queue healthy, workers consuming

Credentials could not be decrypted

After a redeploy, credentials are unreadable

The N8N_ENCRYPTION_KEY env changed between deploys, or the container was recreated without preserving the key, and every stored credential is now unusable.

Encryption key restored or credentials rebuilt

Postgres pool exhausted

Database connections run out

Many workers each opening connections, a long-running workflow holding one, and the Postgres pool at its max, which freezes new executions until something releases.

Connection pool tuned for the worker count

worker stalled heartbeat missed

Workers die quietly

A worker process that OOMs on a heavy workflow, Kubernetes restarts it, but the in-flight job sits as stalled in Bull until the stall interval kicks in.

Workers sized and health-checked properly

node type not loaded

Custom nodes vanish after upgrade

A custom community node pinned to a version that no longer loads cleanly on the new n8n release, and any workflow that uses it fails on load.

Custom nodes rebuilt and pinned

Workflow could not be activated

Workflows will not activate

A webhook trigger without a path, a schedule trigger with an invalid cron, or a dependency node whose credentials are no longer valid, blocking the whole workflow from going live.

Triggers validated, workflows activating cleanly

ECONNRESET on HTTP Request

Upstream connections drop mid-run

A long HTTP call to a partner API that terminates partway through, and a workflow that does not distinguish retryable from fatal errors so it just stops.

Retries and timeouts set per node

execution data pruned 42,110 rows

Execution history disappears too fast

Default pruning settings remove execution data quickly on a busy instance, so debugging a workflow that failed last Tuesday is suddenly impossible.

Retention policy aligned with your ops needs

What we do

n8n help, from install to scale

Call us for one stuck workflow, or let us run the whole n8n stack for you.

Rescue
Workers stalled, credentials unreadable, or queue mode in meltdown. We stabilize the instance first, then write up what caused it so it does not come back.
Production setup
Postgres, Redis, workers, webhook front end, TLS, backups, encryption key handling and alerting set up the way an on-call engineer actually wants them.
Queue mode migration
Moving from single-process n8n onto queue mode with scalable workers, without losing executions or breaking active webhooks during the cutover.
Custom nodes
TypeScript nodes for internal services, with tests, so your team gets the same drag-and-drop experience for the APIs that matter most.
Upgrades
Minor-version upgrades rehearsed on a staging instance, deprecated nodes patched, and credentials verified before the live cutover.
Managed Tech
A standing retainer that covers backups, upgrades, worker health, metric dashboards and a human responder when a workflow starts misbehaving at odd hours.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running n8n alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

n8n questions

Something else? Call+1 737 727 7327

Should we self-host n8n or use the cloud offering?

If your workflows handle regulated data or you have the operations capacity, self-hosting is usually cheaper at non-trivial volume. If you mostly want the editor and a few workflows and nobody on the team wants to run Redis and Postgres, the hosted plan is often the pragmatic choice. We do the math either way before recommending.

Our n8n encryption key is gone, can we recover credentials?

Honestly, no. The encryption key is the only thing that decrypts stored credentials, and without it every password, token and API key in the instance is just ciphertext. The recovery path is to rotate every credential in every upstream system, re-enter them in n8n with a new key, and update your deployment process so the key is managed as a secret rather than a hardcoded env value.

When do we need n8n queue mode?

Once a single process starts missing webhooks under load, or the execution queue in the database is visibly growing, you have outgrown the simple deployment. Queue mode with Redis, Postgres and separate workers is the supported way to scale, and it is worth planning before you need it rather than during an outage.

How do we handle n8n upgrades safely?

Pin the version, keep a staging instance that mirrors production, run every active workflow in staging after the upgrade, patch any deprecated nodes, and only then cut production over. We also back up the Postgres database right before the cutover so a rollback is a database restore rather than a reinstall.

Can you migrate our Zapier or Make workflows to n8n?

Yes, by rebuilding rather than importing. The data models and node semantics differ between platforms, so we go through each workflow, document its business rules, and implement it in n8n with the same inputs and outputs and tests to prove it. Some workflows turn out to be cheaper as a custom microservice than any iPaaS tool.

How much does n8n help cost?

The estimate is free. Describe the instance and what you need and we come back with a price before any work starts.

Free estimate

n8n giving you trouble?

Tell us how the instance is deployed and what is going wrong and we come back with a plan and a price.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.