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 Patches Info, is designed to fetch information about patches related to assets from the Connect Secure API. It allows users to query asset patch data with flexible filtering, pagination, and sorting options. This can be particularly useful in scenarios where you need to monitor or audit patch statuses on various assets within an IT environment, track compliance, or generate reports on patch deployments.
Practical examples include:
- Retrieving all patches applied to a specific set of assets filtered by certain conditions.
- Paginating through large sets of patch records to process them in batches.
- Sorting patch information by date or severity to prioritize remediation efforts.
Properties
| Name | Meaning |
|---|---|
| X USER ID | User identifier required for authentication or tracking purposes in the API request header. |
| Condition | Query condition string to filter the asset patches info based on specified 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 returned patch records, e.g., by date or priority. |
Output
The node outputs JSON data containing the retrieved asset patch information. The structure typically includes details about each patch such as patch identifiers, status, associated asset information, timestamps, and other metadata as provided by the Connect Secure API.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Connect Secure API.
- The node depends on the Connect Secure API being accessible and properly configured.
- No additional external services are explicitly required beyond the API access.
Troubleshooting
- Missing or invalid X USER ID: Since the
X USER IDheader is mandatory, omitting it or providing an incorrect value will likely cause authentication or authorization errors. Ensure the user ID is correct and included. - Invalid query conditions: Malformed or unsupported query strings in the
Conditionproperty may lead to API errors or empty results. Validate the syntax and semantics of the query condition. - Pagination issues: Setting
SkiporLimitincorrectly (e.g., negative numbers) might cause unexpected behavior or errors. Use non-negative integers. - Ordering errors: Providing invalid fields in
Order Bycould result in API errors or default ordering. Confirm that the field names match those supported by the API. - API connectivity problems: Network issues or incorrect API credentials will prevent successful data retrieval. Verify network access and credential validity.
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 sent.
- General best practices for API pagination and filtering.
Note: The above summary is based solely on static analysis of the provided source code and property definitions.