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 operation, Retrieve Asset Compliance Report Card, is designed to fetch compliance report card data related to assets from an external API. It allows users to query asset compliance information with customizable filtering, pagination, and sorting options. This can be particularly useful in scenarios where organizations need to monitor asset compliance status, generate reports for audits, or integrate compliance data into workflows for further processing or alerting.
Practical examples include:
- Retrieving a filtered list of asset compliance records based on specific conditions.
- Paginating through large sets of compliance data by skipping and limiting the number of records returned.
- Sorting the compliance report cards by specified fields to prioritize or organize the output.
Properties
| Name | Meaning |
|---|---|
| X USER ID | User identifier required for authentication or tracking purposes; sent as a request header X-USER-ID. |
| Condition | Query condition string to filter the compliance report cards based on specific criteria. |
| Skip | Number of records to skip, used for pagination to offset the starting point of results. |
| Limit | Maximum number of records to return, controlling the size of the result set. |
| Order By | Field(s) by which to order the results, allowing sorting of the compliance report cards. |
Output
The node outputs JSON data representing the retrieved asset compliance report cards. Each item in the output corresponds to a compliance record matching the query parameters. The structure typically includes details about the asset's compliance status, relevant metadata, and any other fields provided by the API response.
If binary data were involved (e.g., file attachments), it would be included in a separate binary property, but this operation focuses on JSON data retrieval only.
Dependencies
- Requires an API key credential or similar authentication token configured in n8n to authorize requests to the Connect Secure API.
- Depends on the external Connect Secure API endpoint that provides asset compliance report card data.
- No additional environment variables are explicitly required beyond standard API authentication setup.
Troubleshooting
- Missing or invalid X USER ID: Since the user ID is sent as a header and marked required, omitting it or providing an incorrect value will likely cause authentication or authorization errors. Ensure the correct user ID is supplied.
- Invalid query conditions: Malformed or unsupported query strings in the "Condition" property may lead to API errors or empty results. Validate the syntax and semantics of the query condition.
- Pagination issues: Setting "Skip" or "Limit" to inappropriate values (e.g., negative numbers) might cause unexpected behavior or errors. Use non-negative integers.
- Ordering errors: Specifying invalid fields in "Order By" could result in API errors or default ordering. Confirm valid sortable fields with the API documentation.
- API connectivity problems: Network issues or incorrect API credentials will prevent successful data retrieval. Verify network access and credential correctness.
Links and References
- Connect Secure API Documentation (Replace with actual URL)
- n8n Documentation on HTTP Request Node for understanding how headers and query parameters are handled.
- General guidance on Pagination and Filtering in APIs