Overview
This node, named "Create IP Object," is designed to create an IP object in a firewall or network management system via an API. It takes an IP address or subnet as input and sends a request to the configured firewall API to register this IP object. This can be useful for automating network security configurations, such as defining IP addresses or ranges for firewall rules, access control lists, or monitoring.
Practical examples:
- Automatically adding new devices' IP addresses to a firewall's allowed list.
- Creating IP objects for subnets to simplify rule management in a firewall.
- Integrating with dynamic IP management workflows where IPs are frequently updated or added.
Properties
| Name | Meaning |
|---|---|
| IP Address | The IP address or subnet (e.g., 192.168.1.100 or 192.168.1.0/24) to create an object for. |
Output
The node outputs an array of JSON objects, each corresponding to an input item processed. Each output JSON contains:
success: Boolean indicating if the IP object creation was successful.id: The unique identifier of the created IP object (present only on success).ip: The IP address or subnet that was processed.response: The full response from the API call, including details about the created object.error: Present only if the operation failed; contains the error message.statusCode: HTTP status code returned by the API on failure.response(on failure): Contains the response body or data from the API error.
If the node is configured to continue on failure, it will output failure information per item instead of stopping execution.
Dependencies
- Requires connection to a firewall API service, authenticated via an API key or token credential.
- The node expects the API base URL to be provided through credentials.
- The API endpoint used is
/api/pt/ipon the configured firewall API server. - The node sends HTTP POST requests with JSON payloads.
- The node sets the
Accept-Languageheader to Vietnamese (vi), which may affect API responses.
Troubleshooting
Common issues:
- Invalid or malformed IP address input will cause the API to reject the request.
- Network connectivity problems or incorrect API URL configuration will result in request failures.
- Authentication errors if the API key/token is missing or invalid.
- API rate limits or firewall restrictions might block requests.
Error messages:
- Errors include detailed messages, HTTP status codes, and API response bodies.
- If the node fails to create an IP object, it throws an error with the message:
Failed to create IP object: <error message>. Status: <status code>. Response: <API response>. URL: <API URL>. IP: <input IP> - To resolve, verify the IP format, check API credentials, ensure the API URL is correct, and review the API response for specific error details.
Links and References
- Refer to your firewall or network management system's API documentation for details on the
/api/pt/ipendpoint. - General IP addressing and subnetting guides for valid input formats.
- n8n documentation on creating custom nodes and handling HTTP requests.