AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node allows users to create a new Discovery Setting by sending a POST request to an external API. It is useful in scenarios where automated network or system discovery configurations need to be created programmatically, such as setting up scanning parameters or excluding certain ports or hosts from scans. For example, a user might use this node to define which ports should be ignored during a network scan or to mark certain devices as excluded from discovery.

Properties

Name Meaning
X USER ID The user identifier required for the API call, sent as a custom header X-USER-ID.
Additional Body Fields Optional JSON fields to include in the request body under the data property. This includes:
- ignore_ports: An array of ports to ignore (default empty array).
- scan_later: Boolean flag indicating if the scan should be deferred.
- is_excluded: Boolean flag indicating if the target is excluded from discovery.

Output

The node outputs JSON data representing the response from the API after creating the Discovery Setting. The exact structure depends on the API but typically includes details of the newly created setting such as its ID, status, and configuration parameters. There is no indication that binary data is output by this node.

Dependencies

  • Requires an API key credential for authentication with the external AvantGuard ConnectSecure service.
  • Needs the base URL of the API configured in the credentials.
  • The node uses the @avantguardllc/n8n-openapi-node package and an OpenAPI specification (openapi.json) bundled within the node for request building.

Troubleshooting

  • Missing or invalid X USER ID header: The API requires this header; ensure it is provided and correctly set.
  • Invalid JSON in Additional Body Fields: The data field expects valid JSON. Malformed JSON will cause errors.
  • Authentication errors: Verify that the API key credential is correctly configured and has necessary permissions.
  • Network or API endpoint issues: Check the base URL and network connectivity to the API server.
  • Unexpected API responses: Review the API documentation for required fields and correct usage.

Links and References

Discussion