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 operation deletes a specific IP address record identified by its unique ID. It is useful in scenarios where you need to programmatically remove IP addresses from a system or service, such as cleaning up outdated entries, managing access control lists, or automating network configuration updates.
For example, if you maintain a list of allowed IP addresses for firewall rules or API access, this node can be used to delete an IP address that is no longer authorized.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier (ID) of the IP address to delete |
Output
The output JSON will typically contain the result of the deletion operation. This may include confirmation of success or details about the deleted IP address. Since the source code does not explicitly show the output structure, it is expected to return a standard response indicating whether the deletion was successful.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authentication with the external AvantGuard service.
- The node uses a base URL configured via credentials to connect to the AvantGuard API.
- Depends on the
@avantguardllc/n8n-openapi-nodepackage and an OpenAPI specification (openapi.json) for request building.
Troubleshooting
Common issues:
- Providing an invalid or non-existent IP address ID will likely result in an error from the API.
- Missing or incorrect API credentials will cause authentication failures.
- Network connectivity issues to the configured base URL can prevent the node from reaching the API.
Error messages:
- Authentication errors usually indicate problems with the API key or token; verify credentials are correctly set.
- "Not Found" or similar errors suggest the specified IP address ID does not exist.
- Timeout or connection errors imply network or endpoint availability problems.
Resolving these typically involves verifying input parameters, checking credentials, and ensuring network access to the API endpoint.
Links and References
- AvantGuard API Documentation (hypothetical link)
- n8n Documentation on Creating Custom Nodes