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 integrates with the NetBox API to manage network infrastructure data. Specifically, for the Virtual Chassis - Create operation, it allows users to create a new virtual chassis entity within the DCIM domain of NetBox. A virtual chassis is a grouping of multiple physical devices that operate as a single logical device, commonly used in network environments to simplify management and increase redundancy.
Typical use cases include:
- Automating the creation of virtual chassis configurations during network provisioning.
- Integrating NetBox inventory updates into CI/CD pipelines or network automation workflows.
- Managing complex device groupings programmatically without manual UI interaction.
For example, a network engineer can use this node to create a virtual chassis named "CoreSwitchStack1" with a specified master device and descriptive metadata, streamlining device deployment processes.
Properties
| Name | Meaning |
|---|---|
| Domain | The NetBox API domain to target. Options: DCIM, IPAM, Tenancy, Extras, Virtualization, Circuits, Core, Users, Plugins, VPN, Wireless, Status. For this operation, must be "DCIM". |
| Virtual Chassis Name | The name assigned to the new virtual chassis (required). |
| Additional Fields | Optional extra fields to provide more details about the virtual chassis: |
| - Domain | Domain name string (max 30 characters) |
| - Master Device ID | Numeric ID of the master device in the virtual chassis |
| - Description | Text description of the virtual chassis |
| - Comments | Additional comments about the virtual chassis |
| - Tags | Comma-separated list of tag IDs associated with the virtual chassis |
| - Custom Fields | JSON string representing custom fields for the virtual chassis |
Output
The node outputs a JSON object representing the created virtual chassis resource as returned by the NetBox API. This typically includes all properties of the virtual chassis such as its ID, name, master device, description, tags, and any other metadata set during creation.
No binary data output is involved in this operation.
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 properly authenticated.
- No additional external services are required beyond the NetBox API.
Troubleshooting
Common Issues:
- Authentication failures due to invalid or missing API credentials.
- Validation errors if required fields like "Virtual Chassis Name" are missing or malformed.
- Network connectivity issues preventing access to the NetBox API endpoint.
- Incorrect domain or resource selections causing unsupported operations.
Error Messages:
- Errors from the NetBox API will be surfaced, such as HTTP 400 for bad requests or 401 for unauthorized access.
- If the node encounters an error during execution, it logs the error and either throws it or returns it as output if "Continue on Fail" is enabled.
Resolutions:
- Verify API credentials and permissions.
- Ensure all required input properties are correctly filled.
- Confirm the NetBox server URL and network accessibility.
- Use the "Additional Fields" carefully, ensuring correct data types and formats.