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. Specifically, for the Virtual Chassis - Delete operation, it deletes a virtual chassis record identified by its ID within the DCIM domain of NetBox.
Typical use cases include:
- Automating cleanup of virtual chassis configurations in network infrastructure management.
- Integrating NetBox virtual chassis lifecycle management into broader automation workflows.
- Removing obsolete or decommissioned virtual chassis entries programmatically.
Example: Automatically deleting a virtual chassis after decommissioning all associated devices to keep the inventory up-to-date.
Properties
| Name | Meaning |
|---|---|
| Domain | The domain of the NetBox API to target. For this operation, must be DCIM. |
| Virtual Chassis ID | The numeric ID of the virtual chassis to delete. This uniquely identifies the record. |
Output
The node outputs JSON data representing the result of the delete operation. Typically, this will be an empty object or confirmation that the deletion succeeded. If an error occurs, the output JSON will contain an error field with the error message.
No binary data is produced by this operation.
Dependencies
- Requires an active connection to a NetBox instance via its REST API.
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- The node depends on a helper function (
executeOperation) to perform the actual HTTP request to NetBox.
Troubleshooting
Common issues:
- Invalid or missing Virtual Chassis ID: Ensure the ID provided exists and is correct.
- Authentication failures: Verify the API key or token is valid and has sufficient permissions.
- Network connectivity problems: Confirm that n8n can reach the NetBox server endpoint.
Error messages:
"404 Not Found": The specified virtual chassis ID does not exist."401 Unauthorized"or"403 Forbidden": Authentication failed or insufficient permissions.- Timeout or connection errors: Check network settings and NetBox availability.
Resolution tips:
- Double-check input parameters for correctness.
- Validate API credentials and permissions.
- Test connectivity to the NetBox API outside n8n to isolate network issues.