Overview
This node deletes an IP object identified by its unique ID from a remote service via an HTTP DELETE request. It is useful in scenarios where you need to programmatically remove IP objects from a security or threat intelligence platform, such as cleaning up outdated or invalid IP entries.
For example, if you maintain a list of suspicious IP addresses and want to automate the removal of certain IP objects based on specific criteria, this node can be integrated into your workflow to delete those IP objects by their IDs.
Properties
Name | Meaning |
---|---|
IP Object ID | The unique identifier of the IP object to delete. Example: "ip-object-123" |
Output
The node outputs JSON data for each input item processed. Each output item contains:
success
: Boolean indicating whether the deletion was successful.message
: A message returned from the API or a default success message.id
: The ID of the IP object that was attempted to be deleted.response
: The full response object from the API call.
If the deletion fails and the node is set to continue on failure, the output will include:
success
: falseerror
: The error message describing what went wrong.statusCode
: HTTP status code returned by the API.response
: The response body or text from the failed request.id
: The IP object ID related to the failure.
The node does not output binary data.
Dependencies
- Requires an API key credential to authenticate with the external service.
- The node expects a base API URL configured in the credentials.
- The external service must support HTTP DELETE requests at the endpoint
/api/pt/ip/{id}
to delete IP objects.
Troubleshooting
Common issues:
- Invalid or missing IP Object ID: Ensure the ID provided exists and is correctly formatted.
- Authentication failures: Verify that the API key credential is valid and has sufficient permissions.
- Network or connectivity errors: Check network access to the API endpoint.
- API errors such as 404 (Not Found) if the IP object does not exist.
Error messages:
- Errors include detailed information such as HTTP status code and response body.
- If the node is not set to continue on failure, it throws an error with details including the URL, status, and response content.
- To resolve errors, verify the IP object ID, check API credentials, and ensure the API endpoint is reachable.
Links and References
- Refer to your external service's API documentation for details on deleting IP objects via HTTP DELETE requests.
- n8n documentation on HTTP Request node for understanding how HTTP calls are made within nodes.