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
Module → Delete
AI-generatedOverview
This node interacts with the NetBox API to delete a specific module record within the selected domain. It is useful for automating the removal of module entries in NetBox, such as when cleaning up or managing infrastructure data programmatically. For example, a user can delete a module by specifying its ID and the domain it belongs to, streamlining maintenance tasks in network management.
Use Case Examples
- Deleting a module from the DCIM domain by providing the module ID to remove outdated or incorrect module data.
- Automating cleanup of modules in bulk by iterating over module IDs and deleting them via this node.
Properties
| Name | Meaning |
|---|---|
| Domain | Specifies the domain of the NetBox API to target, such as DCIM, IPAM, Tenancy, etc. |
| Module ID | The ID of the module to delete. This is required to identify the specific module record to be removed. |
Output
JSON
json- The JSON output contains the result of the delete operation, typically confirmation of deletion or error details if the operation fails.
Dependencies
- Requires an API key credential for authenticating with the NetBox API.
Troubleshooting
- Common issues include providing an invalid or non-existent Module 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 successfully deleting the module.
- Network connectivity issues to the NetBox API endpoint can cause timeouts or failures in the delete operation.
Links
- NetBox API Documentation - Official documentation for the NetBox API, useful for understanding the endpoints and data structures involved in module deletion.