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 Platform resource under the Delete operation, it deletes a platform record identified by its ID within the selected domain (here, "dcim"). This is useful in scenarios where you need to programmatically remove platform entries from your NetBox instance, such as cleaning up deprecated hardware platforms or automating lifecycle management of device platforms.
Practical examples:
- Automatically deleting a platform after decommissioning all devices using it.
- Cleaning up test or temporary platform records created during automation workflows.
Properties
| Name | Meaning |
|---|---|
| Domain | The domain of the NetBox API to target. Options include: DCIM, IPAM, Tenancy, Extras, Virtualization, Circuits, Core, Users, Plugins, VPN, Wireless, Status. For this operation, "dcim" is relevant. |
| Platform ID | The unique identifier (ID) of the platform record to delete within the DCIM domain. |
Output
The node outputs JSON data representing the result of the delete operation. Typically, this will be an empty response or confirmation that the platform was deleted successfully. If an error occurs, the output JSON will contain an error field with the error message.
No binary data output is involved.
Dependencies
- Requires 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) which handles the actual API call logic.
Troubleshooting
Common issues:
- Invalid or missing Platform ID: The node requires a valid platform ID; otherwise, the API will return an error.
- Authentication failures: Ensure the API key credential is correctly set and has sufficient permissions.
- Network connectivity problems to the NetBox server.
Error messages:
- Errors returned from the NetBox API (e.g., 404 Not Found if the platform ID does not exist).
- Node execution errors are logged and, if "Continue on Fail" is enabled, returned as part of the output JSON under an
errorproperty.
To resolve errors:
- Verify the platform ID exists in NetBox.
- Check API credentials and permissions.
- Confirm network access to the NetBox API endpoint.