Actions100
- Activity Logs Actions
- Articles Actions
- Asset Layouts Actions
- Asset Passwords Actions
- Assets Actions
- Get Assets
- Get Companies Company Id Assets
- Post Companies Company Id Assets
- Get Companies Company Id Assets Id
- Put Companies Company Id Assets Id
- Delete Companies Company Id Assets Id
- Put Companies Company Id Assets Id Archive
- Put Companies Company Id Assets Id Unarchive
- Put Companies Company Id Assets Id Move Layout
- Cards Actions
- Companies Actions
- Expirations Actions
- Exports Actions
- Folders Actions
- IP Addresses Actions
- Lists Actions
- Magic Dash Actions
- Matchers Actions
- Networks Actions
- Password Folders Actions
- Procedure Tasks Actions
- Procedures Actions
- Public Photos Actions
- Rack Storage Items Actions
- Rack Storages Actions
- Relations Actions
- Uploads Actions
Overview
This node is designed to delete a specific network by its unique identifier. It is useful in scenarios where you need to programmatically remove network configurations or clean up unused networks within an infrastructure managed via the connected API. For example, if you have a list of networks and want to automate the removal of certain ones based on criteria such as inactivity or deprecation, this node can be integrated into your workflow to perform those deletions efficiently.
Properties
| Name | Meaning |
|---|---|
| Id | The unique numeric identifier of the network to be deleted. This is a required property. |
Output
The node outputs JSON data representing the result of the delete operation. Typically, this will include confirmation that the network was successfully deleted or details about any error encountered. There is no indication that the node outputs binary data.
Dependencies
- Requires an API key credential for authentication with the external service managing the networks.
- The base URL for the API must be configured in the node credentials.
- Depends on the
@avantguardllc/n8n-openapi-nodepackage and an OpenAPI specification (openapi.json) bundled with the node for request building.
Troubleshooting
Common issues:
- Providing an invalid or non-existent network ID will likely result in an error response from the API.
- Missing or incorrect API credentials will cause authentication failures.
- Network connectivity issues may prevent the node from reaching the API endpoint.
Error messages:
- Errors related to authorization typically indicate problems with the API key or credential setup.
- "Network not found" or similar errors suggest the provided network ID does not exist.
Resolutions:
- Verify the network ID is correct and exists.
- Ensure API credentials are properly configured and valid.
- Check network connectivity and API endpoint availability.
Links and References
- Refer to the API documentation of the network management service for detailed information on the delete network endpoint.
- n8n documentation on creating and using custom nodes with API credentials.