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 "Jobs" resource of an API to retrieve detailed views of job records. It is designed to fetch job data based on user-specific criteria and supports filtering, pagination, and sorting. This node is useful in scenarios where you need to programmatically access job listings or details for reporting, monitoring, or integration with other systems.
For example, you might use this node to:
- Retrieve a filtered list of jobs assigned to a particular user.
- Paginate through large sets of job records by skipping and limiting results.
- Sort job records by specific fields such as date or status.
Properties
| Name | Meaning |
|---|---|
| X USER ID | User Id header value to identify the user making the request. |
| Condition | Query condition string to filter the job records returned by the API. |
| Skip | Number of records to skip (for pagination). |
| Limit | Maximum number of records to return (for pagination). |
| Order By | Field(s) by which to order the returned job records. |
Output
The node outputs JSON data representing the retrieved job details view. The structure corresponds to the API's response for job records filtered and sorted according to the input parameters. Each item in the output typically contains detailed information about a job, such as identifiers, status, timestamps, and other relevant metadata.
No binary data output is indicated by the source code.
Dependencies
- Requires an API key credential for authenticating requests to the Connect Secure API.
- The node depends on the external Connect Secure API service to fetch job data.
- Proper configuration of the API credentials within n8n is necessary for successful operation.
Troubleshooting
- Missing or invalid X USER ID: Since the user ID is required in the request header, omitting it or providing an incorrect value will likely cause authentication or authorization errors.
- Invalid query conditions: Malformed or unsupported query strings in the "Condition" property may result in API errors or empty responses.
- Pagination issues: Setting "Skip" or "Limit" to inappropriate values (e.g., negative numbers) could lead to unexpected results or errors.
- API connectivity problems: Network issues or incorrect API credentials can cause failures in retrieving job data.
To resolve these issues:
- Ensure the "X USER ID" is correctly set and valid.
- Validate query conditions against the API documentation.
- Use sensible numeric values for pagination properties.
- Verify API credentials and network connectivity.
Links and References
- Refer to the Connect Secure API documentation for details on supported query conditions, response formats, and authentication requirements.
- n8n documentation on setting up API credentials and using HTTP request nodes may provide additional context for troubleshooting.