Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the Connect Secure API to update PII (Personally Identifiable Information) scan settings. It allows users to modify configurations related to scanning for sensitive data, such as which scan settings to apply, path settings, allowed file extensions, and associated agent IDs. This is useful in scenarios where organizations need to manage or customize their data privacy scans dynamically, ensuring compliance with data protection regulations.

Practical examples include:

  • Updating scan parameters to include new file types or directories.
  • Adjusting agent assignments responsible for scanning specific data sets.
  • Modifying allowed extensions to control which files are scanned for PII.

Properties

Name Meaning
X USER ID User identifier required for authentication or tracking of the request.
Data JSON object containing the scan configuration details: scan_settings, path_settings, allowed_extension_types, and agent_ids. Each is expected to be an array encoded as a JSON string.
Id Numeric identifier representing the specific PII scan setting record to update.

Output

The node outputs JSON data reflecting the response from the Connect Secure API after updating the PII scan settings. The exact structure depends on the API's response but typically includes confirmation of the updated settings or error information if the update failed.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating with the Connect Secure API.
  • The node uses the Connect Secure API endpoint defined in its internal OpenAPI specification.
  • Proper configuration of the API credentials within n8n is necessary for successful operation.

Troubleshooting

  • Common issues:

    • Missing or invalid X USER ID header may cause authentication failures.
    • Malformed JSON in the Data property can lead to request errors.
    • Providing an incorrect or non-existent Id may result in "not found" or update failure responses.
  • Error messages:

    • Authentication errors typically indicate missing or invalid user identification or API credentials.
    • Validation errors may arise if the JSON structure in Data does not conform to expected schema.
    • API errors related to the Id usually mean the specified scan setting does not exist.

To resolve these:

  • Ensure the X USER ID is correctly set and valid.
  • Validate the JSON format and content of the Data property before execution.
  • Confirm that the Id corresponds to an existing scan setting.

Links and References

  • Connect Secure API documentation (refer to your organization's API docs for detailed endpoints and schemas).
  • n8n documentation on using HTTP Request nodes and handling JSON data.

Discussion