AvantGuard - WebhookSite icon

AvantGuard - WebhookSite

AvantGuard - WebhookSite

Actions100

Overview

This node operation allows you to create a new IP address record in the target system. It is useful for network administrators or IT professionals who need to programmatically add IP addresses with associated metadata such as status, description, and ownership details. For example, you might use this node to automate the provisioning of IP addresses when setting up new devices or services within a company’s network infrastructure.

Properties

Name Meaning
Additional Body Fields Optional fields to specify details about the IP address:
- Address The IP address itself (string).
- Status The status of the IP address. Allowed values: unassigned, assigned, reserved, deprecated, dhcp, slaac.
- Fqdn Fully Qualified Domain Name associated with the IP address (string).
- Description A brief description of the IP address (string).
- Comments Additional comments about the IP address (string).
- Asset Id Numeric identifier of the asset linked to this IP address.
- Network Id Numeric identifier of the network to which this IP address belongs.
- Company Id Numeric identifier of the company owning this IP address.

These fields are optional and can be used to provide additional context or metadata when creating the IP address.

Output

The node outputs JSON data representing the newly created IP address record as returned by the API. This typically includes all the properties sent plus any additional information generated by the system, such as unique identifiers or timestamps.

If the node supports binary data output, it would represent related files or attachments, but based on the provided code and properties, this node focuses on JSON data only.

Dependencies

  • Requires an API key or authentication token configured in n8n credentials to authorize requests to the external IP address management service.
  • The node depends on the external API endpoint that manages IP addresses; thus, network connectivity and valid credentials are necessary.
  • No other external libraries or environment variables are explicitly required beyond standard HTTP request capabilities.

Troubleshooting

  • Invalid Status Value: If the status field contains a value outside the allowed set (unassigned, assigned, reserved, deprecated, dhcp, slaac), the API may reject the request. Ensure the status is one of these exact strings.
  • Missing Required Fields: Although most fields are optional, the IP address itself is critical. Omitting it may cause errors.
  • Authentication Errors: Failure to provide valid API credentials will result in authorization errors. Verify that the API key or token is correctly configured.
  • Network Issues: Connectivity problems to the API endpoint will cause request failures. Check network access and endpoint URLs.
  • Data Type Mismatches: Numeric fields like Asset Id, Network Id, and Company Id must be numbers. Providing strings or invalid types may cause errors.

Links and References

  • Refer to your IP address management system’s API documentation for detailed descriptions of each field and their constraints.
  • Consult n8n documentation on how to configure API credentials and handle HTTP request nodes for further customization.

Discussion