Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node integrates with the Connect Secure API to create a PII (Personally Identifiable Information) scan setting. It allows users to configure scanning parameters for identifying sensitive data within their systems. This is useful in scenarios where organizations need to enforce data privacy policies, comply with regulations like GDPR or CCPA, or monitor data access and usage.

For example, a security team could use this node to define scan settings that specify which file paths to scan, what types of files to include, and which agents should perform the scans. This helps automate the detection of sensitive information across an enterprise environment.

Properties

Name Meaning
X USER ID The user identifier required by the API to authenticate or associate the request with a user.
Data JSON object containing the scan configuration details:
- scan_settings: Array of scan setting configurations.
- path_settings: Array defining which paths to include or exclude in the scan.
- allowed_extension_types: Array of file extensions to be scanned.
- agent_ids: Array of agent identifiers that will execute the scan.

The Data property must be provided as a JSON string and is parsed before sending in the request body.

Output

The node outputs the response from the Connect Secure API after creating the PII scan setting. The output is structured as JSON under the json field and typically contains details about the created scan setting such as its ID, status, and configuration summary.

If the API returns binary data (not indicated here), it would be included accordingly, but based on the code and properties, the output is expected to be JSON only.

Dependencies

  • Requires an API key credential for authenticating with the Connect Secure API.
  • The node depends on the external Connect Secure service being accessible.
  • No additional environment variables are explicitly required beyond the API authentication setup.

Troubleshooting

  • Invalid or missing X USER ID: The API requires the X USER ID header; ensure it is provided and correctly formatted.
  • Malformed JSON in Data property: The data input must be valid JSON. Errors parsing this will cause the request to fail.
  • API authentication errors: Verify that the API key credential is valid and has sufficient permissions.
  • Network or connectivity issues: Ensure the Connect Secure API endpoint is reachable from the n8n instance.
  • Unexpected API responses: Check the API documentation for error codes and messages returned by the Connect Secure service.

Links and References

Discussion