AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node allows users to update discovery settings by sending a PATCH request to an external API. It is useful in scenarios where you need to modify specific configuration parameters related to network or system discovery processes, such as ignoring certain ports, scheduling scans, or excluding items from discovery.

For example, a user might want to update the discovery setting to ignore scanning on certain ports or mark a discovery task to be scanned later. This node facilitates such updates by allowing partial modifications through a PATCH operation.

Properties

Name Meaning
X USER ID The user identifier required for authentication or tracking purposes, sent as a header.
Additional Body Fields Optional fields to include in the request body:
- Data JSON object specifying discovery settings details like ignore_ports (array), scan_later (boolean), and is_excluded (boolean).
- Id Numeric identifier of the discovery setting to update.

Output

The node outputs the JSON response returned by the API after the PATCH request. This typically contains the updated discovery setting object reflecting the changes made.

No binary data output is involved.

Dependencies

  • Requires an API key credential for authenticating requests to the external AvantGuard ConnectSecure service.
  • Needs the base URL of the API configured in the credentials.
  • Uses the @avantguardllc/n8n-openapi-node package internally to build and send requests based on the OpenAPI specification.

Troubleshooting

  • Missing or invalid X USER ID header: Ensure that the "X USER ID" property is provided and correctly set; otherwise, the API may reject the request.
  • Invalid JSON in Data field: The "Data" field must be valid JSON. Invalid JSON will cause parsing errors before sending the request.
  • Incorrect Id value: The "Id" must correspond to an existing discovery setting; otherwise, the API may return a not found or validation error.
  • Authentication errors: Verify that the API key credential is properly configured and has sufficient permissions.
  • Network or API errors: Check connectivity and API availability if requests fail unexpectedly.

Links and References

Discussion