Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the Connect Secure API to retrieve scheduled cron jobs related to assets. It is useful for workflows that need to monitor, audit, or process scheduled tasks defined in an asset management system. For example, you might use this node to fetch all cron jobs for a specific user, filter them by certain conditions, or paginate through large sets of scheduled jobs.

Properties

Name Meaning
X USER ID The User Id header value to identify the user making the request.
Condition A query string to filter the cron jobs based on specific criteria (e.g., status, type).
Skip Number of records to skip, useful for pagination.
Limit Maximum number of records to return.
Order By Field name(s) to order the results by (e.g., creation date, name).

Output

The node outputs JSON data representing the retrieved cron jobs. Each item corresponds to a cron job record fetched from the Connect Secure API, including details such as schedule, status, and associated asset information. If binary data were involved, it would be summarized here, but this node focuses on JSON output only.

Dependencies

  • Requires an API key credential for authenticating with the Connect Secure API.
  • The node depends on the external Connect Secure service being accessible.
  • No additional environment variables are explicitly required beyond the API authentication setup.

Troubleshooting

  • Common issues:

    • Missing or invalid API credentials will cause authentication failures.
    • Incorrect or missing "X USER ID" header may result in authorization errors or empty responses.
    • Improperly formatted query conditions can lead to API errors or no results.
    • Pagination parameters ("Skip" and "Limit") set incorrectly might cause unexpected subsets of data.
  • Error messages:

    • Authentication errors typically indicate invalid or missing API keys; verify credentials.
    • Authorization errors suggest the "X USER ID" does not have permission; check user ID correctness.
    • Query parameter errors mean the condition or other query fields are malformed; review syntax.

Resolving these usually involves verifying credentials, ensuring correct header values, and validating query parameters.

Links and References

Discussion