AvantGuard - WebhookSite icon

AvantGuard - WebhookSite

AvantGuard - WebhookSite

Actions100

Overview

This node operation retrieves IP address records from a system, allowing users to filter the results based on various criteria such as network ID, specific IP address, status, associated asset or company IDs, and creation or update timestamps. It is useful in scenarios where you need to query and analyze IP address data within a network or asset management context, for example:

  • Fetching all IP addresses assigned to a particular network.
  • Filtering IP addresses by their current status (e.g., active, inactive).
  • Retrieving IP addresses created or updated within a specific time range.
  • Searching for IP addresses linked to a certain asset or company.

Such functionality helps automate inventory audits, network monitoring, or compliance reporting workflows.

Properties

Name Meaning
Additional Query Parameters Optional filters to refine the IP addresses retrieved. These include:
Network Id: Filter by network ID (number).
Address: Filter by exact IP address (string).
Status: Filter by IP address status (string).
Fqdn: Filter by fully qualified domain name (string).
Asset Id: Filter by asset ID (number).
Company Id: Filter by company ID (number).
Created At: Filter IPs created at or within a date/time range (ISO 8601 string).
Updated At: Filter IPs updated at or within a date/time range (ISO 8601 string).

The date/time filters accept either an exact timestamp or a range formatted as 'start_datetime,end_datetime'. If one end of the range is omitted, it defaults to open-ended filtering (from start date until now, or from past until end date).

Output

The node outputs JSON data representing the list of IP addresses matching the specified filters. Each item in the output typically contains details about an IP address record, such as its address, status, associated network, asset, company, FQDN, and timestamps for creation and updates.

If binary data were involved (not indicated here), it would be summarized accordingly, but this operation deals solely with JSON data.

Dependencies

  • Requires an API key or authentication token configured in the node credentials to access the external service providing IP address data.
  • The base URL for the API is set via credentials.
  • No additional external dependencies are indicated in the provided source code snippet.

Troubleshooting

  • No results returned: Check that the filter parameters are correctly set and match existing data. For example, ensure date formats follow ISO 8601 and ranges are properly formatted.
  • Authentication errors: Verify that the API key or authentication token is valid and has sufficient permissions.
  • Invalid parameter errors: Confirm that numeric fields receive numbers and strings are properly formatted.
  • Timeouts or connectivity issues: Ensure network connectivity to the API endpoint and that the base URL is correct.

Links and References

  • Refer to the API documentation of the IP address management system for detailed descriptions of query parameters and response structure.
  • ISO 8601 date format reference: https://en.wikipedia.org/wiki/ISO_8601

Discussion