n8n RMM integration · 12 minute read
Build a read-only n8n RMM workflow before automating action.
Start with tenant-scoped customer, site, endpoint, and alert data. This guide shows the current Nizlo community node boundary, a least-privilege setup, and two workflows that can be proven without changing an endpoint.
Last reviewed November 17, 2026 · Maintainer disclosure below
Current integration boundary
Query four operational resources without granting write access.
The open-source n8n-nodes-nizlo package is a deliberately read-only adapter for the Nizlo management API. Nizlo maintains the package. Initial implementation and documentation were AI-assisted and human-reviewed. It is not an endorsement by n8n, and it should be reviewed like any other third-party community node.
Customers
Get one customer or list tenant-scoped customers with search and lifecycle filters.
Sites
Get one site or list sites by customer, search term, and lifecycle state.
Endpoints
Get one endpoint or list endpoints by customer, site, tag, status, platform, kind, attention state, favorite, or lifecycle.
Alerts
List alerts by status, severity, assignment, source, customer, site, device, or search term.
Least-privilege setup
Six steps from question to controlled workflow
1. Choose one read-only question
Start with a bounded operational question, such as which active critical alerts are unresolved or which active Windows endpoints are currently offline. Define the expected result before connecting credentials.
2. Create the narrowest Nizlo token
Create a personal access token in Admin → API Access. Use devices.view for customer, site, and endpoint reads; add alerts.view only when the workflow needs alerts. The token cannot exceed the active technician's role.
3. Install and review the community node
Use a self-hosted n8n instance with community nodes enabled. Review the repository, current revision, dependencies, license, and n8n's community-node guidance before installing it in a production environment.
4. Store the token as an n8n credential
Paste the token into a Nizlo API credential—not a node field, code block, environment screenshot, or workflow export. The credential test performs a read-only request to the current technician identity endpoint.
5. Run manually with a small limit
Use Get Many with server-side filters and a bounded limit. Inspect the returned items, empty results, permission failures, and pagination behavior before scheduling or connecting another system.
6. Add delivery only after the read is trusted
If another node sends a notification or creates work elsewhere, make that side effect explicit, deduplicate it, suppress secrets, and record ownership. The Nizlo node itself remains read-only.
Install from reviewed source
The npm registry release is not yet public.
Do not assume the package is available through n8n's community node search yet. For an authorized self-hosted evaluation, review the public repository and its current release, then use n8n's documented manual installation path. A direct GitHub install is currently documented by the repository:
cd ~/.n8n/nodes
npm install github:izikipizi/n8n-nodes-nizloTwo bounded starter workflows
Prove the data before adding a destination.
Alert review
List active critical alerts
- Resource: Alert
- Operation: Get Many
- Status: Active
- Severity: Critical
- Limit: 50
Proof before scheduling: Verify every result is still unresolved and critical, then decide whether a separate, approved downstream step should notify anyone.
Fleet review
List offline Windows endpoints
- Resource: Endpoint
- Operation: Get Many
- Lifecycle: Active
- Platform: Windows
- Status: Offline
- Limit: 100
Proof before scheduling: Verify the endpoint, customer, site, and last-seen context before treating an offline result as an incident or service obligation.
Security and operating boundaries
Frequently asked questions
Can n8n connect to Nizlo RMM?
Yes. Nizlo maintains an open-source n8n community node for tenant-scoped, read-only access to customers, sites, endpoints, and alerts. The public source can currently be reviewed and installed from GitHub on a self-hosted n8n instance with community nodes enabled.
Can the Nizlo n8n node patch or reboot endpoints?
No. The current node does not create, update, delete, execute, patch, reboot, or remotely access anything. It intentionally starts with read-only operations.
Which permissions does the n8n workflow need?
Customer, site, and endpoint reads require devices.view. Alert reads require alerts.view. Give the personal access token only the permissions needed by the workflow; the technician's role remains an additional boundary.
Is the Nizlo n8n node an independent endorsement?
No. Nizlo maintains the node and this guide. They document a functional integration and its current boundaries, not an independent endorsement by n8n or another directory.
Test with your own tenant
Start a 14-day Nizlo trial without a credit card.
Connect one authorized endpoint and prove one read-only workflow.
Start the no-card trial
