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, allowing users to manage various network-related resources. Specifically, for the Locations - Update operation, it enables updating details of a location within LibreNMS. This is useful in scenarios where physical or logical location data needs correction or enhancement, such as adjusting geographic coordinates after site surveys or relocating equipment.
Practical examples include:
- Updating the latitude and longitude of a data center location.
- Marking whether the coordinates are fixed or can be dynamically updated by devices.
Properties
| Name | Meaning |
|---|---|
| Location | The name or ID of the location to update. |
| Coordinates | A collection of coordinate properties: |
| Latitude | Latitude coordinate of the location (e.g., "37.4220041"). |
| Longitude | Longitude coordinate of the location (e.g., "-122.0862462"). |
| Fixed Coordinates | Boolean indicating if the coordinates are fixed (true) or can be updated (false). |
Output
The node outputs JSON data representing the updated location object as returned by the LibreNMS API. This typically includes the location's ID, name, updated coordinates, and other metadata managed by LibreNMS.
If binary data were involved (not applicable here), it would represent files or media related to the location, but this operation deals solely with JSON data.
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 and SSL certificate validation settings must be properly set in the node credentials.
Troubleshooting
- Invalid Location ID or Name: If the specified location does not exist, the API will return an error. Verify the location identifier before running the node.
- Authentication Errors: Ensure the API key credential is valid and has sufficient permissions to update locations.
- Coordinate Format Issues: Latitude and longitude should be valid decimal strings. Invalid formats may cause request failures.
- Network Connectivity: Confirm that the LibreNMS server is reachable from the n8n environment and that no firewall blocks the API calls.
Links and References
- LibreNMS API Documentation
- n8n Documentation on HTTP Request Nodes (for understanding API integrations)