Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node integrates with an external scanning service's API to create a custom profile. It allows users to send structured JSON data representing the profile configuration along with a user identifier header. This is useful in scenarios where you want to programmatically define or update scanning profiles for specific users, such as automating security scans or compliance checks tailored to individual user settings.

Practical examples include:

  • Automatically creating scan profiles based on user roles or preferences.
  • Integrating with CI/CD pipelines to generate scan configurations dynamically.
  • Managing multiple user-specific scan profiles from a centralized workflow.

Properties

Name Meaning
X USER ID The User Id sent as a header (X-USER-ID) to identify the user for whom the profile is created. This is a required string.
Data JSON object containing the custom profile data to be sent in the request body. Typical fields include nse_scripts (an array of scripts) and is_global (a boolean indicating if the profile is global).

Output

The node outputs the response from the external scan service after creating the custom profile. The output is available in the json field and contains the server's response data, which typically includes details about the newly created profile such as its ID, status, and any metadata returned by the API.

There is no indication that the node handles binary data output.

Dependencies

  • Requires an API key credential for authenticating with the external scan service.
  • The node depends on the external scan service's API being accessible and properly configured.
  • No additional environment variables are explicitly required beyond the API authentication setup.

Troubleshooting

  • Missing or invalid X USER ID header: The API requires this header; ensure it is provided and correctly formatted.
  • Malformed JSON in Data property: Since the data property expects valid JSON, errors can occur if the input is not well-formed. Validate JSON syntax before execution.
  • API authentication failures: Verify that the API key or token used is valid and has sufficient permissions.
  • Network or connectivity issues: Ensure the external scan service endpoint is reachable from the n8n instance.
  • Unexpected API responses: Check the API documentation for error codes and messages returned by the service to diagnose issues.

Links and References

  • Refer to the external scan service API documentation for detailed information on the custom profile creation endpoint and expected payload structure.
  • n8n documentation on HTTP Request nodes and JSON handling may help in preparing the Data property correctly.

Discussion