NetBox icon

NetBox

Consume NetBox API

Overview

This node integrates with the NetBox API, a popular infrastructure resource modeling tool used for managing IP addresses, devices, and other network resources. Specifically, the "Interface" resource with the "Get" operation allows users to retrieve detailed information about a specific network interface by its ID within the DCIM domain.

Common scenarios where this node is beneficial include:

  • Automating retrieval of interface details for network inventory or auditing.
  • Integrating interface data into workflows for monitoring or configuration management.
  • Fetching interface metadata to correlate with other network management systems.

For example, a user can input an Interface ID to fetch its properties such as name, status, MAC address, and connected device information, enabling automated documentation or validation processes.

Properties

Name Meaning
Domain The domain of the NetBox API to target. Options: DCIM, IPAM, Tenancy, Extras, Virtualization, Circuits, Core, Users, Plugins, VPN, Wireless, Status. For this operation, must be "dcim".
Interface ID The unique identifier of the interface record to retrieve. Required when Domain is "dcim", Resource is "interfaces", and Operation is "get".

Output

The output is a JSON object representing the retrieved interface record from NetBox. It typically includes fields such as interface name, description, MAC address, enabled status, associated device, and other metadata defined by the NetBox API for interfaces.

If the node encounters an error and "Continue on Fail" is enabled, it outputs a JSON object with an error field containing the error message.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to a NetBox instance via its REST API.
  • Requires an API authentication token credential configured in n8n to authorize requests.
  • The node depends on an internal helper function (executeOperation) to perform the actual API call based on selected parameters.

Troubleshooting

  • Common issues:

    • Invalid or missing Interface ID will cause the API call to fail.
    • Incorrect Domain or Resource selection may result in no matching endpoint.
    • Network connectivity or authentication failures will prevent successful API calls.
  • Error messages:

    • Errors thrown during execution are logged and, if "Continue on Fail" is enabled, returned as part of the output JSON under the error key.
    • Typical errors include HTTP 404 (not found) if the Interface ID does not exist, or 401/403 for authentication issues.
  • Resolutions:

    • Verify the Interface ID is correct and exists in NetBox.
    • Ensure the API token credential is valid and has sufficient permissions.
    • Confirm the Domain is set to "dcim" and Resource to "interfaces" for this operation.

Links and References

Discussion