AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node interacts with the AvantGuard ConnectSecure API to retrieve cron job information related to assets. Specifically, the "Get Retrieve Cron Jobs" operation fetches a list of scheduled cron jobs for a given user context. This is useful in scenarios where you need to monitor, audit, or manage automated tasks configured within the AvantGuard system.

Practical examples include:

  • Fetching all cron jobs assigned to a specific user to display in a dashboard.
  • Filtering cron jobs based on conditions such as status or schedule time.
  • Paginating through large sets of cron jobs using skip and limit parameters.

Properties

Name Meaning
X USER ID The User Id header value to specify the user context for which cron jobs are retrieved.
Additional Query Parameters Optional query parameters to refine the request:
- Condition: Query condition string to filter results.
- Skip: Number of records to skip (for pagination).
- Limit: Maximum number of records to return.
- Order By: Field name to order the results by.

Output

The node outputs JSON data representing the retrieved cron jobs. Each item in the output corresponds to a cron job record fetched from the API, including details such as schedule, status, and associated asset information.

If the API supports binary data for any field (not evident here), it would be included accordingly, but this operation primarily returns structured JSON data.

Dependencies

  • Requires an API key credential for authenticating with the AvantGuard ConnectSecure API.
  • The base URL for the API must be configured in the node credentials.
  • The node depends on the @avantguardllc/n8n-openapi-node package and an OpenAPI specification (openapi.json) bundled internally for request building.

Troubleshooting

  • Missing or invalid X USER ID: The API requires the X-USER-ID header; ensure it is provided and valid. Missing this will likely cause authentication or authorization errors.
  • Invalid query parameters: Providing malformed or unsupported query conditions may result in API errors. Validate the syntax and supported fields for filtering.
  • API connectivity issues: Check network access and correct base URL configuration if requests fail to reach the API.
  • Pagination misconfiguration: Using skip and limit incorrectly might lead to empty results or repeated data; verify these values carefully.

Links and References

Discussion