npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

n8n-nodes-workflow-load-balancer-ha

v0.1.0

Published

n8n community node that routes executions across target workflows with automatic failover, retries and a circuit breaker

Readme

n8n-nodes-workflow-load-balancer

An n8n community node that routes each incoming item to one of several target workflows, with automatic failover, retries, and a circuit breaker — so you don't hand-build IF + Error Trigger chains.

What it does

Drop the node between a trigger and a set of target workflows. For each item it picks a target by the chosen routing mode, runs it via executeWorkflow, and on failure/timeout automatically retries then fails over to the next target. First success wins and flows out the success output. If every target fails, the failure strategy decides what happens.

Outputs: success (0) and allFailed (1). Each item carries a __lb metadata object (correlation id, winner, which targets it failed over from) unless you turn it off.

Routing modes

| Works from in-process signals | Notes | |---|---| | Round Robin, Weighted, Priority, Random | no signals needed | | Least Running | tracks concurrent runs in this node process | | Latency, Health Score | EWMA of past executions in this process | | Sticky Session | same key → same target (5-min affinity) | | Least Queue / CPU / Memory | fall back to the fallback mode + flag __lb.fallbackUsed |

Why the last row falls back: a community node runs inside execute() and cannot read Redis/BullMQ queue depth or per-worker CPU/RAM — those are n8n platform internals. The node degrades honestly instead of faking a signal. The full distributed design (Redis-shared state, worker heartbeats, dashboard, REST APIs) is in TRD-Workflow-Load-Balancer.md; it requires a core/Enterprise fork, not a community node.

Reliability

  • Retry per target with none / fixed / exponential+jitter backoff.
  • Circuit breaker per target: opens after N consecutive failures, half-opens after a cooldown, closes after successful probes. State is per node process (ponytail: global lock — back with Redis for multi-worker sharing).
  • Failure strategy when all targets fail: error (throws) · deadLetter (route item to a DLQ workflow, continue) · fallbackPayload (emit a static payload, continue).

Scope / honest limits

  • Failover is at-least-once. If a target had side effects before failing, they aren't rolled back — make targets idempotent using the injected __lb.correlationId.
  • Breaker/affinity/round-robin state is per process (see above).
  • Streaming targets aren't failed over mid-stream.

Develop

npm install
npm test          # runnable router self-check (no framework)
npm run build     # compiles to dist/ + copies icon

Then link into your n8n install per the community node docs (~/.n8n/custom or npm link).

Layout

  • nodes/WorkflowLoadBalancer/router.ts — pure routing/failover/breaker logic (no n8n imports, unit-tested).
  • nodes/WorkflowLoadBalancer/WorkflowLoadBalancer.node.ts — n8n node; wires the router to executeWorkflow.
  • nodes/WorkflowLoadBalancer/router.test.ts — 8-invariant self-check.