Actions222
- Application Baseline Actions
- Attack Surface Actions
- Backup Software Actions
- EDR Actions
- Tags Actions
- PII Actions
- External Scan Actions
- Settings Actions
- Compliance Assessment Actions
- Reports Actions
- Compliance Actions
- Jobs Actions
- Active Directory Actions
- Retrieve Ad Roles
- Retrieve Ad User Licenses
- Retrieve Azure Licenses
- Retrieve Azure Ad Logs
- Retrieve Azure Secure Score
- Retrieve Ad Password Policies
- Retrieve Ad Groups View
- Retrieve Ad Ous View
- Retrieve Ad Gpos View
- Retrieve Ad Computers View
- Retrieve Ad Users View
- Retrieve Ad Domain Details
- Retrieve Ad Gpos Details
- Retrieve Get Ous Details
- Retrieve Get Groups Details
- Retrieve Ad Group Users
- Retrieve Ad Group Computers
- Retrieve Get User Details
- Retrieve Get Computer Details
- Retrieve Ad Roles Details
- Retrieve Ad Roles Member
- Retrieve Ad Basic Info
- Audit Log Actions
- Ad Audit Actions
- Asset Data Actions
- Retrieve Bios Info
- Retrieve Bio Info
- Retrieve Browser Extensions
- Retrieve Browser Extension
- Retrieve Ciphers View
- Retrieve Cipher View
- Retrieve Windows Protection Status
- Retrieve Window Protection Status
- Retrieve Asset Compliance Report Card
- Retrieve Asset Firewall Policy
- Retrieve Asset Installed Drivers
- Retrieve Asset Installed Driver
- Retrieve Asset Interface
- Retrieve Asset Msdt
- Retrieve Asset Ports
- Retrieve Asset Port
- Retrieve Asset Security Report Data
- Retrieve Asset Security Report Datum
- Retrieve Asset Shares
- Retrieve Asset Share
- Retrieve Asset Storages
- Retrieve Asset Storage
- Retrieve Asset Unqouted Services
- Retrieve Asset Unqouted Service
- Retrieve Asset User Shares
- Retrieve Asset User Share
- Retrieve Asset Video Info
- Retrieve Asset Windows Reboot Required
- Retrieve Asset Window Reboot Required
- Vulnerabilities Actions
- Firewall Actions
- Integration Actions
- Retrieve Integration Credentials
- Retrieve Integration Credential
- Create Integration Credential
- Update Integration Credential
- Delete Integration Credential
- Retrieve Integration Rules
- Retrieve Integration Rule
- Create Integration Rule
- Update Integration Rule
- Delete Integration Rule
- Retrieve Company Mappings
- Retrieve Company Mapping
- Create Company Mapping
- Update Company Mapping
- Delete Company Mapping
- Event Set Actions
- Ticket Template Actions
- Scheduler Actions
- Credentials Actions
- Asset Actions
- Retrieve Records
- Retrieve Assets
- Retrieve Asset
- Create Asset
- Update Asset
- Delete Asset
- Retrieve Asset Stats
- Retrieve Asset Stat
- Retrieve Asset View
- Retrieve Cron Jobs
- Retrieve Kernel Modules
- Retrieve Suid Permissions
- Retrieve Ufw Firewall Rules
- Retrieve Selinux Settings
- Retrieve Asset Iptables Rules
- Retrieve Asset Users
- Retrieve Asset Processes Running
- Retrieve Asset Services
- Retrieve Asset Patches Info
- Retrieve Asset Firewall Rules
- Retrieve Asset Registry Misconfiguration
- Retrieve Asset Open Ports
- Retrieve Notification Tickets View
- Retrieve System Events View
- Discovery Settings Actions
- Retrieve Discovery Settings
- Retrieve Discovery Setting
- Create Discovery Setting
- Update Discovery Setting
- Delete Discovery Setting
- Retrieve Agent Discoverysettings Mapping
- Retrieve Agent Discoverysetting Mapping
- Create Agent Discoverysetting Mapping
- Update Agent Discoverysetting Mapping
- Delete Agent Discoverysetting Mapping
- Auth Actions
- Company Actions
- Agent Actions
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 IDheader; ensure it is provided and correctly formatted. - Malformed JSON in Data property: The
datainput 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
- Connect Secure API Documentation (Replace with actual URL)
- n8n HTTP Request Node Documentation (For understanding routing and request configuration)