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-connector-engine

v1.0.1

Published

Universal Connector Engine node for n8n - schema-driven, backend-driven capabilities

Readme

n8n-nodes-connector-engine

Universal Connector Engine node for n8n. Connects to your ERP Integration Execution API and runs connector capabilities (resources and operations) with schema-driven input fields.

Requirements

  • Node.js 18+ (for building the package)
  • n8n instance (cloud or self-hosted)
  • Connector Engine API (base URL + API key from your ERP Integration app)

Build (required before install from path)

From the package directory:

npm install
npm run build

This produces the dist/ folder that n8n loads.

Install in n8n

Option A: From zip (no build, ready to install)

Use the pre-built zip so you don’t need Node 18 or to run npm run build.

  1. Get n8n-nodes-connector-engine.zip (from the repo or run npm run zip in the package folder to create it).
  2. Unzip it into a folder, e.g.:
    mkdir -p n8n-nodes-connector-engine
    cd n8n-nodes-connector-engine
    unzip /path/to/n8n-nodes-connector-engine.zip
    You should see package.json, README.md, and dist/ in that folder.
  3. On the machine where n8n runs, install from that folder:
    mkdir -p ~/.n8n/nodes
    cd ~/.n8n/nodes
    npm install /path/to/n8n-nodes-connector-engine
  4. Restart n8n. The Connector Engine node and Connector Engine API credential will be available.

Option B: From n8n UI (if published to npm)

  1. In n8n: SettingsCommunity nodesInstall.
  2. Enter: n8n-nodes-connector-engine.
  3. Install and restart if prompted.

Option C: Install from local path (self-hosted)

  1. Build the package (see above) so dist/ exists.
  2. On the machine where n8n runs, install the package into n8n’s nodes directory:
mkdir -p ~/.n8n/nodes
cd ~/.n8n/nodes
npm install /path/to/n8n-nodes-connector-engine
  1. Restart n8n.

Option D: Docker / queue mode

  1. Build the package locally (Node 18+) so dist/ exists.
  2. Copy the built package (or the repo) into the container and install:
docker exec -it n8n sh
mkdir -p ~/.n8n/nodes
cd ~/.n8n/nodes
npm install /path/to/n8n-nodes-connector-engine
  1. Restart the n8n container.

Usage

  1. Add a Connector Engine node to your workflow.
  2. Create a Connector Engine API credential:
    • Base URL: your Execution API base URL (e.g. https://your-app.com/api or http://localhost/api).
    • API Key: an API key from your ERP Integration app (API Keys page).
  3. In the node, choose ConnectorResourceOperation (loaded from your API).
  4. Add Fields (key/value) as required by the operation; keys come from the capability schema.
  5. Run the workflow; the node calls POST /execute and returns the result data.

Credentials

  • Name: Connector Engine API
  • Fields: Base URL (required), API Key (required, password).

License

MIT