AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node performs a POST request to an external scanning endpoint, allowing users to initiate or trigger scans on an external system. It is useful in scenarios where automated security scans, data discovery, or compliance checks need to be integrated into workflows. For example, a user might use this node to start a vulnerability scan on a newly deployed server or to trigger a data discovery process on a cloud resource.

Properties

Name Meaning
X USER ID User identifier sent as a custom HTTP header (X-USER-ID). Required for authentication or tracking purposes.
Additional Body Fields Optional additional fields to include in the JSON body of the POST request:
- Company Id Numeric company identifier to associate the scan with a specific company.
- Discovery Settings JSON object containing configuration settings for the discovery process.

Output

The node outputs the JSON response returned by the external scan endpoint in the json field of the output data. This typically contains information about the scan initiation status, identifiers, or any metadata returned by the external service.

No binary data output is indicated.

Dependencies

  • Requires an API key credential (or similar) configured in n8n to authenticate requests to the external scanning service.
  • The base URL and authentication details must be set up in the node credentials.
  • The node sends HTTP headers and JSON body data according to the input properties.

Troubleshooting

  • Missing or invalid X USER ID header: The external service may reject requests without this required header. Ensure it is provided and correctly mapped.
  • Malformed JSON in Discovery Settings: Since this property expects a JSON string parsed before sending, invalid JSON will cause errors. Validate JSON syntax before input.
  • API authentication errors: Verify that the API key or authentication token is correctly configured in the node credentials.
  • Unexpected response structure: If the external service changes its response format, downstream nodes expecting certain fields may fail. Check the service documentation for updates.

Links and References

  • Refer to the external scanning service's API documentation for details on required headers, body parameters, and response formats.
  • n8n documentation on HTTP Request node and custom node development for understanding routing and property definitions.

Discussion