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 interacts with the Connect Secure API to retrieve settings related to Personally Identifiable Information (PII) scans. Specifically, the "Retrieve Pii Scan Setting" operation fetches configuration details for a given PII scan setting by its unique identifier. This is useful in scenarios where users need to programmatically access or audit PII scan configurations within their Connect Secure environment, such as verifying scan parameters or integrating scan settings into automated workflows.
Practical examples include:
- Automatically retrieving and displaying PII scan settings in a dashboard.
- Using the retrieved settings to trigger conditional logic in data processing pipelines.
- Auditing or backing up PII scan configurations as part of compliance workflows.
Properties
| Name | Meaning |
|---|---|
| X USER ID | The user identifier required for authentication or context when making the API request. |
| Id | The numeric identifier of the specific PII scan setting to retrieve. |
Output
The node outputs JSON data representing the details of the requested PII scan setting. This typically includes all configuration fields associated with that scan setting as returned by the Connect Secure API. The exact structure depends on the API response but generally contains metadata and parameters defining the PII scan.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Connect Secure API.
- The node depends on the Connect Secure API being accessible and properly configured.
- The bundled code uses the
@devlikeapro/n8n-openapi-nodepackage and lodash for internal operations. - The node expects the user to provide the "X USER ID" header value and the scan setting "Id" as inputs.
Troubleshooting
- Missing or invalid "X USER ID": The API may reject requests without a valid user ID header. Ensure this property is correctly set.
- Invalid or non-existent "Id": Providing an incorrect scan setting ID will likely result in an error or empty response. Verify the ID before use.
- Authentication errors: If the API key credential is missing or invalid, the node will fail to authenticate.
- Network issues: Connectivity problems to the Connect Secure API endpoint can cause timeouts or failures.
- API changes: Updates to the Connect Secure API might affect the response format or available operations; keep the node and credentials updated accordingly.
Links and References
- Connect Secure API Documentation (Replace with actual URL)
- n8n OpenAPI Node Package
- Lodash Documentation