Description
@redanthrax/n8n-nodes-tacticalrmm
An n8n community node for integrating with the Tactical RMM API.
Tactical RMM is a remote monitoring and management tool, built with Django and Vue.
Development
This repo uses pnpm with a committed lockfile and supply-chain controls in pnpm-workspace.yaml (see SECURITY.md). After clone:
corepack enable && corepack prepare pnpm@10.19.0 --activate
pnpm install --frozen-lockfile
pnpm run audit:supply-chain
pnpm run build
Use pnpm only for installs in this repo. With Corepack enabled, npm install and yarn install are rejected. Do not commit package-lock.json or yarn.lock (see SECURITY.md).
API spec and catalog
The OpenAPI spec lives at docs/swagger.yaml. Regenerate the endpoint catalog:
pnpm run generate
See docs/api-catalog.md for every automation-facing endpoint. Use the Custom API resource for endpoints not covered by curated operations.
Live preview with n8n-node dev
n8n-node dev
Requires Node.js 22.22.3+.
Installation
Follow the installation guide in the n8n community nodes documentation.
npm install @redanthrax/n8n-nodes-tacticalrmm
Prerequisites
- Tactical RMM instance with API access
- Your Tactical RMM base URL (e.g.
https://api.example.com) - A dedicated integration user, integration role, and API key (see setup below)
- Agent (27 operations)
- Alert
- Alert Template
- API Key
- Automation
- Check
- Client
- Core
- Deployment
- Log
- Reporting
- Role
- Script
- Service
- Site
- Software
- Task
- User
- Windows Update
- Tactical RMM API documentation
- n8n documentation
- Repository
- n8n 0.199.0+
- Tactical RMM 0.15.2+ (OpenAPI spec version 1.4.0 in
docs/swagger.yaml)
Setup
API access in Tactical RMM (recommended)
Do not reuse a personal admin account for n8n. Create a dedicated integration setup with least privilege:
1. Integration role — In Tactical RMM, create a role scoped only to the clients, sites, and actions your workflows need (read-only where possible).
2. Integration user — Create a service/integration user account and assign only that role.
3. API key — In Settings → Global Settings → API Keys, create a key for the integration user (not a day-to-day admin account).
Rotate or revoke the API key if the n8n credential is exposed. Tighten the role if you add workflows later.
Configuring credentials in n8n
| Field | Example | Notes |
|——-|———|——-|
| Base API URL | https://api.example.com | Your Tactical RMM server URL |
| API Key | (from API Keys settings) | Key for the integration user; sent as X-API-KEY |
Supported operations
129+ operations across 20 resources (including Custom API for any path in the OpenAPI spec):
Resource groups
| Group | Resources |
|——-|———–|
| Agents | Agent, Check, Service, Software, Task, Windows Update |
| Organization | Client, Site, Deployment |
| Monitoring | Alert, Alert Template |
| Automation | Automation Policy, Script |
| Administration | API Key, Core, Log, Role, User |
| Reporting | Reporting |
| Advanced | Custom API |
Curated resources
Custom API
Call any documented REST endpoint (method, path, query, body). Full path list: docs/api-catalog.md.
Resources
Compatibility
License
MIT