Documentation

@baramundi/n8n-nodes-baramundi-management-suite

Automate your baramundi Management Suite (bMS) from n8n workflows. This community node connects n8n to your bMS via the bConnect REST API β€” manage endpoints, run jobs, deploy software, check compliance, and more.

[!WARNING]
πŸ§ͺ This project is currently in Technical Preview.

We're actively refining this project and welcome early feedback.
Features, APIs, and behavior may change over time.

Please perform thorough testing before deployment and use at your own risk. It is not recommended for production use.

When working with AI services, carefully review permissions, data access, and information shared with models.
Avoid using sensitive, confidential, or personal data unless you have verified that your security, privacy, and compliance requirements are met.

Keep an eye on AI token usage, especially during testing, as costs can add up quickly depending on the model and workload.

Screenshot 2026-11-02 144904

236 operations across 6 nodes, compatible with baramundi Management Suite 2025 R2, 2026 R1 and 2026 R2.


What You Need

  • An n8n instance (version 2.9.0 or later) β€” install n8n
  • A baramundi Management Suite (2025 R2, 2026 R1 or 2026 R2) with bConnect API enabled
  • Your bMS server address (e.g. https://bms.company.com:444/bconnect)
  • A bMS user account with API access, or an API key
    (generate one in the baramundi management console under Server Management > API Keys)

Network Requirements

  • Port 444 (HTTPS) must be open between your n8n server and your bMS server

Getting Started

Step 1: Install the Node

In n8n, open Settings > Community Nodes, click Install, enter
@baramundi/n8n-nodes-baramundi-management-suite, and confirm. The six baramundi nodes then appear in the nodes panel.

Without access to the npm registry, install the release file instead:

  1. Download baramundi-n8n-nodes-baramundi-management-suite-<version>.tgz and its .sha256 file from the
    latest GitHub release.
  2. On your n8n server, check the file and install it into n8n's nodes folder:
sha256sum -c baramundi-n8n-nodes-baramundi-management-suite-0.12.0.tgz.sha256
mkdir -p ~/.n8n/nodes && cd ~/.n8n/nodes
npm install /path/to/baramundi-n8n-nodes-baramundi-management-suite-0.12.0.tgz
  1. Restart n8n.

For Docker, see Docker Installation below.

Step 2: Add Your bMS Credentials

  1. In n8n, go to Credentials > Add Credential
  2. Search for baramundi bConnect API
  3. Fill in:
Field What to enter Example
Server URL Your bMS bConnect URL https://bms.company.com:444/bconnect
Authentication Method Basic Auth or API Key API Key
API Key Your bConnect API key 2D34AB0B...
  1. Click Test Credential β€” you should see a green checkmark

Step 3: Create Your First Workflow

  1. Click "+ Create new workflow" > "Add first step"
  2. Add a Manual Trigger
  3. Click "+" after the trigger > search "baramundi" > add it
  4. In the baramundi node:
    • Credential: select your baramundi credential
    • bMS Version: select 26R2, 26R1 or 25R2 (matching your server)
    • Resource: Endpoint
    • Operation: Get Many
    • Return All: on
  5. Click "Test workflow"

You should see your managed endpoints appear as JSON output.

Step 4: What's Next

Try these common workflows:

  • List all Windows endpoints β€” Endpoint > Get Many > Filter by endpoint type
  • Run a job β€” Job > Execute > select a job instance
  • Check compliance β€” Security > List Detected Vulnerabilities (26R1 and later)
  • Software inventory β€” Software > Get Installed Software > by endpoint

See the example workflows for ready-to-use templates.


Docker Installation

If running n8n in Docker, build a custom image with the release file next to your Dockerfile:

FROM n8nio/n8n:latest
USER root
COPY baramundi-n8n-nodes-baramundi-management-suite-0.12.0.tgz /tmp/package.tgz
RUN mkdir -p /home/node/.n8n/nodes && \
    cd /home/node/.n8n/nodes && \
    npm init -y && \
    npm install --ignore-scripts /tmp/package.tgz && \
    rm /tmp/package.tgz && \
    chown -R node:node /home/node/.n8n/nodes
USER node

See INSTALLATION.md for details, Docker Compose, upgrades and troubleshooting.


Credentials Configuration

Authentication Methods

Method When to use
API Key (recommended) Generate in bMS console under Server Management > API Keys. Simpler, no password rotation needed.
Basic Auth Uses a Windows/AD username and password. Works with any existing bMS admin account.

How to Find Your bMS Server URL

  1. Open the baramundi Management Center on your bMS server
  2. The server address is the machine name or IP where bMS is installed
  3. bConnect listens on port 444 by default (HTTPS)
  4. Your URL will be: https://<server-name>:444/bconnect

How to Generate an API Key

  1. Open the baramundi Management Center
  2. Go to Server Management > API Keys
  3. Click Create New API Key
  4. Give it a descriptive name (e.g. "n8n Connector")
  5. Copy the generated key β€” you won't see it again

SSL / TLS Certificates

If your bMS server uses a self-signed or internal CA certificate:

Quick fix (test only): Enable Ignore SSL Issues in the credential form.

Production (recommended): Set the CA certificate path before starting n8n:

NODE_EXTRA_CA_CERTS=/path/to/your-internal-ca.pem

For Docker, mount the certificate and add the environment variable:

environment:
  - NODE_EXTRA_CA_CERTS=/certs/internal-ca.pem
volumes:
  - ./internal-ca.pem:/certs/internal-ca.pem:ro

bMS Version Targeting

Every baramundi node has a bMS Version dropdown as its first parameter. Selecting your version filters operations to only what your server supports.

Setting Shows
26 R2 227 operations: those of 26 R1 without Get Cloud Connectors, which 26 R2 removed, plus Universal Dynamic Group thresholds, API key management, Intune remote actions on Windows endpoints and Get Entra ID Data by endpoint
26 R1 (default) 211 operations, including compliance, Universal Dynamic Groups and software bundles
25 R2 171 operations, including industrial endpoints and Replace (PUT) maintenance windows, which exist in 25 R2 only

Available Nodes

Node Operations What it does
baramundi Admin 47 Active Directory, server management, microservices, OS config
baramundi Endpoint 49 Endpoints (all types), Intune remote actions, logical groups, endpoints by static/dynamic group, maintenance windows
baramundi Software 47 Software inventory, bundles, updates, variables, Universal Dynamic Groups and their thresholds
baramundi Job 34 Job definitions (read and execute), instances, folders, kiosk releases
baramundi Security 33 Compliance, BitLocker, Defender, local admin accounts
baramundi Asset 26 Asset inventory, asset types, stock/type folders

Counts are the operations each node offers across all bMS versions; the editor shows only those your selected version supports.

Use with AI agents

All six nodes can be attached to n8n's AI Agent node as tools, so an agent can look up endpoints, jobs or vulnerabilities on its own. On self-hosted n8n, community nodes are only offered as tools when the environment variable N8N_COMMUNITY_PACKAGES_ALLOW_TOOL_USAGE=true is set.

Each tool runs exactly the resource and operation you configure on it. Give an agent read operations unless it really should change your bMS: a tool set to Delete or Execute does that whenever the agent decides to call it.


Troubleshooting

Problem Solution
SSL certificate error Enable "Ignore SSL Issues" in credential (test only), or set NODE_EXTRA_CA_CERTS (production)
Authentication failed Verify credentials. Check the user/API key has bConnect API permissions in bMS.
Connection timeout Check network connectivity and firewall rules. bConnect default port is 444.
Empty results Check API user permissions. Try enabling "Return All" to get more than one page.
Dropdowns not loading Test your credential first. Use "Enter Custom GUID" as fallback.
Operation not visible Check the bMS Version dropdown matches your server (25R2, 26R1 or 26R2).

Example Workflows

Ready-to-use workflow templates in the example-workflows/ directory:

Workflow Description
Patch Cycle Report List endpoints with pending Windows updates
Job Failure Alert Monitor job instances and alert on failures
Critical CVEs Find endpoints with critical vulnerabilities (26R1)
Stale Endpoint Report Find endpoints not seen in the last 30 days

Import any workflow via n8n > Workflows > Import from File.


Security

Runtime package has zero known vulnerabilities. npm audit may report issues from build tools (@n8n/node-cli, vitest) and peer dependencies (n8n-workflow) β€” these are not present in the published dist/ package.

Report security issues to bernd.wiedemann@baramundi.de (not via public GitHub issues).


Compatibility

Component Version
n8n 2.9.0+
Node.js (to run n8n) 22.23.4+, 24.22.1+ or 26.12.1+
baramundi bConnect API V2.0
baramundi bMS 25R2, 26R1, 26R2

Development

git clone https://github.com/baramundisoftware/n8n-bConnect-connector.git
cd n8n-bConnect-connector
npm install
./start-n8n-dev.sh        # builds + starts n8n on http://localhost:5678
npm run build              # compile TypeScript
npm test                   # run unit tests (1072 tests)
npm run test:coverage      # with coverage report
npm run lint               # ESLint

Contributing

  1. Fork the repository
  2. Create a feature branch
  3. Write tests for new functionality
  4. Run npm run lint and npm test before submitting
  5. Open a pull request

License

MIT

Resources

Discussion