Actions88
- Module Actions
- Platform Actions
- Device Actions
- Device Bay Actions
- Device Bay Template Actions
- Device Role Actions
- Device Type Actions
- Interface Actions
- Manufacturer Actions
- Module Bay Actions
- Module Bay Template Actions
- Module Type Actions
- Region Actions
- Site Actions
- Virtual Chassis Actions
- Virtual Device Context Actions
Overview
This node interacts with the NetBox API, a popular infrastructure resource modeling tool used for managing IP addresses, devices, virtual chassis, and other network-related resources. Specifically, the "Virtual Chassis" resource's "Get" operation allows users to retrieve detailed information about a particular virtual chassis by its ID.
Typical use cases include:
- Fetching configuration or status details of a virtual chassis in a data center.
- Integrating NetBox virtual chassis data into automation workflows for network management.
- Auditing or reporting on virtual chassis setups programmatically.
For example, a user might want to automatically pull virtual chassis details to verify configurations before deploying changes or to synchronize inventory data with other systems.
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". |
| Virtual Chassis ID | The numeric identifier of the virtual chassis to retrieve. This is required to specify which virtual chassis record to get. |
Output
The output is a JSON object representing the retrieved virtual chassis record from NetBox. It typically includes all attributes of the virtual chassis such as its ID, name, member devices, master device, and other metadata defined by the NetBox API schema.
No binary data output is expected from this operation.
Example output structure (simplified):
{
"id": 123,
"name": "Chassis-1",
"master": {
"id": 10,
"name": "Device-A"
},
"members": [
{
"id": 11,
"name": "Device-B"
},
{
"id": 12,
"name": "Device-C"
}
],
"status": "active",
...
}
Dependencies
- Requires an active connection to a NetBox instance via an API key credential configured in n8n.
- The node depends on the NetBox API being accessible and the provided credentials having permission to read virtual chassis data.
- No additional external libraries beyond those bundled with the node are required.
Troubleshooting
Common issues:
- Invalid or missing Virtual Chassis ID will cause the API call to fail.
- Incorrect domain selection (anything other than "DCIM") will not allow access to the virtual chassis resource.
- Network connectivity problems or incorrect API credentials will result in authentication or connection errors.
Error messages:
"404 Not Found": The specified virtual chassis ID does not exist."401 Unauthorized"or"403 Forbidden": API key is invalid or lacks permissions."Network Error": Unable to reach the NetBox server; check URL and network settings.
Resolutions:
- Verify the Virtual Chassis ID is correct and exists in NetBox.
- Confirm the domain is set to "DCIM" for virtual chassis operations.
- Ensure API credentials are valid and have sufficient permissions.
- Check network connectivity and endpoint URL configuration.