Actions243
- Cable Actions
- Cable Termination Actions
- Connected Device Actions
- Console Port Actions
- Console Port Template Actions
- Console Server Port Actions
- Console Server Port Template Actions
- Device Actions
- Device Bay Actions
- Device Bay Template Actions
- Device Role Actions
- Device Type Actions
- Front Port Actions
- Front Port Template Actions
- Interface Actions
- Interface Template Actions
- Inventory Item Actions
- Inventory Item Role Actions
- Inventory Item Template Actions
- Location Actions
- MAC Address Actions
- Manufacturer Actions
- Module Actions
- Module Bay Actions
- Module Bay Template Actions
- Module Type Actions
- Module Type Profile Actions
- Platform Actions
- Power Feed Actions
- Power Outlet Actions
- Power Outlet Template Actions
- Power Panel Actions
- Power Port Actions
- Power Port Template Actions
- Rack Actions
- Rack Reservation Actions
- Rack Role Actions
- Rack Type Actions
- Rear Port Actions
- Rear Port Template Actions
- Region Actions
- Site Actions
- Site Group Actions
- Virtual Chassis Actions
- Virtual Device Context Actions
- Virtual Link Actions
Device Type → Delete
AI-generatedOverview
This node interacts with the NetBox API to delete a specific device type record within the DCIM domain. It is useful in scenarios where you need to programmatically remove device type entries from your NetBox inventory, such as cleaning up obsolete or incorrect device types.
Use Case Examples
- Deleting a device type by specifying its ID to maintain an up-to-date inventory in NetBox.
- Automating the removal of device types as part of a network infrastructure cleanup process.
Properties
| Name | Meaning |
|---|---|
| Domain | Specifies the domain of the NetBox API to target, here it is set to 'dcim' for device-related resources. |
| Device Type ID | The unique identifier of the device type to be deleted. |
Output
JSON
id- The ID of the deleted device type record.status- Status of the delete operation, typically indicating success or failure.
Dependencies
- Requires an API key credential for authenticating with the NetBox API.
Troubleshooting
- Common issues include providing an invalid or non-existent device type ID, which will result in an error from the NetBox API indicating the record was not found.
- Authentication errors due to missing or incorrect API credentials will prevent the node from executing successfully.
- Network connectivity issues to the NetBox server can cause timeouts or failures.
Links
- NetBox API Documentation for Device Types - Official documentation for managing device types via the NetBox API, including delete operations.