Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node allows users to create a new domain within an "Attack Surface" resource by sending relevant data to an external API. It is useful in scenarios where security teams or automated workflows need to register or track domains as part of their attack surface management process. For example, a security analyst might use this node to programmatically add a domain for later vulnerability scanning or monitoring.

Properties

Name Meaning
X USER ID The user identifier required for the API request header to authenticate or identify the user making the request.
Data JSON-formatted data representing the domain details to be created. By default, it includes a property "scanlater": true. This can be customized with additional domain-specific information as needed.

Output

The node outputs JSON data representing the response from the API after creating the attack surface domain. This typically includes confirmation details such as the created domain's ID, status, and any metadata returned by the service. There is no indication that binary data is output by this node.

Dependencies

  • Requires an API key credential or similar authentication token configured in n8n to authorize requests to the external Attack Surface API.
  • Depends on the external Attack Surface service being available and reachable via network.
  • Uses HTTP headers (specifically X-USER-ID) to pass user identification information.
  • The node relies on JSON payloads for sending domain creation data.

Troubleshooting

  • Missing or invalid X USER ID header: The API may reject requests if the user ID header is missing or incorrect. Ensure the property is set correctly.
  • Malformed JSON in Data property: Since the Data field expects valid JSON, errors will occur if the input is not properly formatted. Validate JSON syntax before execution.
  • API connectivity issues: Network problems or incorrect API credentials can cause failures. Verify API endpoint accessibility and credential validity.
  • Unexpected API responses: If the API changes or returns errors, check the response message for clues and update the node configuration accordingly.

Links and References

  • No direct links are provided in the source code. Users should refer to the official documentation of the Attack Surface API they are integrating with for detailed API usage and schema.

Discussion