Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

The "Retrieve Scheduler" operation in the Scheduler resource allows users to query and retrieve scheduler records from an external service. This node is useful for workflows that need to fetch scheduled tasks, jobs, or events based on specific criteria such as filtering conditions, pagination, and sorting order.

Typical use cases include:

  • Fetching a list of scheduled jobs for monitoring or reporting.
  • Retrieving scheduler entries filtered by certain conditions (e.g., status, date range).
  • Paginating through large sets of scheduler data.
  • Sorting scheduler results by specified fields.

Properties

Name Meaning
X USER ID User identifier header required for authentication or scoping the request.
Condition Query condition string to filter scheduler records based on custom criteria.
Skip Number of records to skip for pagination purposes.
Limit Maximum number of records to return.
Order By Field(s) to order the returned scheduler records by.

Output

The node outputs JSON data representing the retrieved scheduler records. The structure typically includes an array of scheduler objects matching the query parameters. Each object contains details about individual scheduled items as provided by the external API.

If the external API supports binary data related to scheduler entries (e.g., attachments), the node would handle it accordingly, but this operation primarily focuses on JSON data retrieval.

Dependencies

  • Requires an API key credential for authenticating with the external Connect Secure API.
  • The node depends on the external Connect Secure API endpoint that exposes scheduler data.
  • Proper configuration of the API credentials within n8n is necessary for successful requests.

Troubleshooting

  • Missing or invalid X USER ID: The API requires the X USER ID header; ensure it is provided and correct.
  • Invalid query conditions: Malformed or unsupported query strings in the Condition property may cause errors or empty results.
  • Pagination issues: Setting Skip or Limit incorrectly might result in no data or incomplete data sets.
  • API authentication failures: Verify that the API key credential is valid and has sufficient permissions.
  • Network or connectivity errors: Ensure that n8n can reach the external API endpoint without firewall or proxy issues.

Common error messages will generally relate to authentication failure, invalid query parameters, or rate limiting by the external API. Reviewing the API documentation and logs can help resolve these.

Links and References

Discussion