Actions83
- Bills Actions
- Alerts Actions
- Alert Rules Actions
- ARP Actions
- Devices Actions
- Device Groups Actions
- Inventory Actions
- Locations Actions
- Logs Actions
- Poller Groups Actions
- Ports Actions
- Port Groups Actions
- Routing Actions
- Services Actions
- Switching Actions
Overview
The node integrates with the LibreNMS network monitoring system, specifically allowing users to update service entries within LibreNMS. This operation is useful for managing the status and behavior of monitored services, such as enabling or disabling a service or marking it to be ignored by the monitoring system.
Typical use cases include:
- Automatically disabling a service when maintenance is scheduled.
- Ignoring certain services temporarily during troubleshooting.
- Updating service metadata based on external triggers or automation workflows.
Properties
| Name | Meaning |
|---|---|
| Service ID | The unique identifier of the service to update. |
| Update Fields | Collection of fields to update for the service: |
| - Service Disabled: Boolean flag indicating whether the service should be disabled. | |
| - Service Ignore: Boolean flag indicating whether the service should be ignored. |
Output
The node outputs JSON data representing the updated service object as returned by the LibreNMS API. This typically includes the current state of the service after the update, reflecting any changes made (e.g., disabled status or ignore flag).
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to a LibreNMS instance via its REST API.
- Needs an API authentication token credential configured in n8n to authorize requests.
- The base URL of the LibreNMS API must be set in the credentials.
- SSL certificate validation can be optionally skipped based on credential settings.
Troubleshooting
- Invalid Service ID: If the provided Service ID does not exist, the API will likely return an error. Verify the ID is correct and corresponds to an existing service.
- Authentication Errors: Ensure the API key or token is valid and has sufficient permissions to update services.
- Network Issues: Connection failures may occur if the LibreNMS server is unreachable or the base URL is incorrect.
- Field Validation: Only the specified update fields (
service_disabled,service_ignore) are accepted; providing unsupported fields may cause errors. - SSL Certificate Issues: If using self-signed certificates, enable the option to skip SSL validation in credentials to avoid connection errors.