Kronos

Overview

This node integrates with the Kronos API to manage schedules programmatically. It supports operations such as creating, deleting, retrieving, pausing, resuming, and triggering schedules. This is useful for automating time-based workflows where external systems or processes need to be triggered on a schedule defined in Kronos.

Typical use cases include:

• Automatically triggering webhooks at specified times or recurring intervals.
• Managing schedules dynamically based on workflow logic.
• Pausing or resuming scheduled tasks without manual intervention.
• Retrieving schedule details or lists for monitoring or reporting purposes.

For example, you could create a recurring schedule that triggers a webhook every day at 9 AM, or trigger a one-time schedule immediately via this node.

Properties

Note: The provided properties JSON only includes "Schedule ID" relevant for operations other than creation and listing. The node also supports other properties (not listed here) for creating schedules, such as Title, Description, Cron Expression, URL, etc., but they are outside the scope of the requested Resource-Operation.

Output

The node outputs JSON data representing the response from the Kronos API for the performed operation:

• For trigger schedule, the output JSON contains the result of triggering the specified schedule, typically confirmation or status information returned by the API.
• For other operations (create, get, delete, pause, resume), the output JSON corresponds to the respective API response, such as schedule details or success messages.
• If multiple items are processed, each input item’s output is paired accordingly.
• No binary data output is produced by this node.

Dependencies

• Requires an active connection to the Kronos API via an API key credential configured in n8n.
• The base URL for the Kronos API is obtained from the credentials.
• Uses HTTP requests with JSON payloads and expects JSON responses.
• Timezone conversions rely on an external time API (timeapi.io) to convert date-times to UTC when creating schedules (not directly relevant for the trigger operation).

Troubleshooting

• Common issues:
  • Invalid or missing Schedule ID will cause API errors.
  • Network connectivity problems or incorrect API credentials will prevent successful requests.
  • Triggering a non-existent or already inactive schedule may return errors.
• Error messages:
  • API error responses are logged and included in the node output if "Continue On Fail" is enabled.
  • Typical errors include authentication failures, invalid parameters, or resource not found.
• Resolution tips:
  • Verify the Schedule ID is correct and exists in Kronos.
  • Ensure API credentials are valid and have necessary permissions.
  • Check network access to the Kronos API endpoint.
  • Use the node’s debug logs to inspect request and response details.

Links and References

• Kronos API Documentation (general reference, actual link depends on your Kronos environment)
• Cron Expression Guide (useful for defining recurring schedules)
• n8n Expressions Documentation (for dynamic property values like timezone)