ASC Self-Healing (n8n custom node)

This directory is a standard n8n community node package. TypeScript sources live in src/; n8n loads compiled files from dist/, which you must generate before install.

Build (maintainers / from Git)

From this folder, with Node.js 18+:

npm install
npm run build

This runs tsc and copies *.svg and *.node.json into dist/. The dist/ directory is not committed; npm run prepublishOnly runs the same build when publishing to npm.

Publish to npm (for client installs from the registry)

Anyone with an npmjs.com account and publish rights can ship this package so the client runs npm install n8n-nodes-asc-self-healing inside n8n’s nodes folder (see Manual installation) or installs it from the n8n UI community nodes list once it is public.

1. One-time: create an npm account, enable 2FA if required by your org, then npm login.
2. From n8n-nodes-asc-self-healing/ (this folder, not the monorepo root):

npm install
npm publish --dry-run
npm publish --access public

Use --dry-run first to confirm the packed tarball only contains dist/ (and package.json, README.md, LICENSE if present).

prepublishOnly runs npm run build automatically before publish, so dist/ is included per the "files": ["dist"] field.

Scoped name (optional): If you prefer @your-org/n8n-nodes-asc-self-healing, rename name in package.json, add "publishConfig": { "access": "public" }, and tell clients to install that full scoped name.

After publish: bump version in package.json (semver) for each release, then npm publish again.

Install on the n8n server

Requirements: same machine (or image) as n8n, Node.js 18+, and network access from n8n to itself for retries if you use relative webhook paths.

1. Copy the entire n8n-nodes-asc-self-healing folder to the server (for example next to your n8n data directory).
2. Install dependencies (devDependencies are required on the machine that runs the TypeScript build):

npm install

3. Compile and copy static assets:

npm run build

4. Optional — drop build-only packages while keeping dist/:

npm prune --omit=dev

(n8n-workflow is a peer dependency; n8n already ships a compatible version at runtime.)

5. Register the package with n8n using one of the methods described in the official docs: Install community nodes (local package / N8N_COMMUNITY_PACKAGES / custom extensions directory, depending on how you host n8n).

6. Restart n8n. In the editor, search for ASC Self-Healing: Report Error.

Client / Ops handoff (no n8n admin UI)

If the client will not use the n8n UI to install community nodes, they can still load this package from the same machine or container that runs n8n using npm link (symlink) or npm install from a tarball. This needs shell access to the n8n host (or docker exec), not n8n “admin” in the browser.

Package name (from package.json, used with npm link): n8n-nodes-asc-self-healing

Source: clone the delivery repo and use this folder, e.g.
https://github.com/optimu16/ascv3.git → directory n8n-nodes-asc-self-healing/.

Option A — npm link (what they asked for)

Official reference: Run your node locally (same pattern on a server).

1. On a shell that can reach the n8n data directory, clone or copy the repo, then:

cd n8n-nodes-asc-self-healing
npm install
npm run build
npm link

2. Inside the environment where n8n runs, use n8n’s custom nodes directory (create it if missing). Typical paths:

   • Bare install: ~/.n8n/custom
   • Official Docker image (user node): /home/node/.n8n/custom

   If custom does not exist, create it and initialize once:

mkdir -p ~/.n8n/custom
cd ~/.n8n/custom
npm init -y

3. Link the global package into that directory (name must match package.json):

npm link n8n-nodes-asc-self-healing

4. Restart n8n. In the editor, search for ASC Self-Healing: Report Error (search by node display name, not the long package name).

Docker example (adjust container name):

docker exec -it n8n sh
cd /home/node/.n8n/custom && npm link n8n-nodes-asc-self-healing

Note: npm link registers a global symlink on that machine. The account that runs npm link in the package directory must be the same environment where npm link n8n-nodes-asc-self-healing runs inside custom, or use a single CI-built image that bakes in the built dist/ and runs step 2–3 in the image layer.

Option B — Tarball (no global link)

Good when you must not use global npm links.

cd n8n-nodes-asc-self-healing
npm install && npm run build && npm pack

Send the generated n8n-nodes-asc-self-healing-1.0.0.tgz. On the server, from n8n’s nodes folder (see Manual installation):

mkdir -p ~/.n8n/nodes
cd ~/.n8n/nodes
npm install /path/to/n8n-nodes-asc-self-healing-1.0.0.tgz

Then restart n8n.

Use in a workflow

1. On a risky node: On Error → Continue (using error output).
2. Connect the red output to ASC Self-Healing: Report Error.
3. Handler URL = full URL of your imported Generalized Error Handler webhook (example: https://YOUR-N8N-HOST/webhook/error-handler).
4. Trigger Node Name = exact name of the node whose JSON contains the business payload (e.g. your Webhook node name).

Optional: Retry Webhook Path, healing metadata, and ASC Self-Healing Handler API credential if the handler URL is protected with Bearer auth.

Contract

The node sends the same JSON shape as the legacy snippet (contract_version: error-handler-snippet-v3; contract_source: asc_self_healing_node).