AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node operation allows users to create a new attack surface domain by sending a POST request with specified user identification and optional additional data fields. It is useful in scenarios where security teams or automated workflows need to register or track domains related to an organization's attack surface for monitoring, analysis, or remediation purposes.

For example, a security analyst might use this node to programmatically add a newly discovered domain to their attack surface inventory, including metadata such as scan scheduling preferences.

Properties

Name Meaning
X USER ID The user identifier required for the request header to authenticate or associate the action with a specific user.
Additional Body Fields Optional JSON fields that can be added to the request body. Currently supports a data field which accepts JSON input (e.g., { "scanlater": true }). This allows customization of the payload sent when creating the attack surface domain.

Output

The node outputs JSON data representing the response from the API after creating the attack surface domain. This typically includes details about the created domain resource, confirmation status, or any relevant metadata returned by the service.

No binary data output is indicated.

Dependencies

  • Requires an API key credential or similar authentication token configured in n8n to authorize requests.
  • Depends on the external AvantGuard ConnectSecure API endpoint, with the base URL provided via credentials.
  • The node uses the @avantguardllc/n8n-openapi-node package and an OpenAPI specification (openapi.json) bundled internally to build its properties and handle requests.

Troubleshooting

  • Missing or invalid X USER ID: Since the X USER ID header is required, omitting it or providing an incorrect value will likely cause authentication or authorization errors. Ensure this property is correctly set.
  • Malformed JSON in Additional Body Fields: The data field expects valid JSON. Invalid JSON syntax will cause parsing errors before the request is sent.
  • API connectivity issues: Verify that the base URL and credentials are correctly configured and that the external API is reachable.
  • Unexpected API responses: Check the API documentation for error codes and messages if the node returns errors or unexpected results.

Links and References

Discussion