Actions7
Overview
The node interacts with the Kronos API to manage schedules. It supports operations such as creating, deleting, retrieving, pausing, resuming, and triggering schedules. This node is useful for automating time-based workflows where you need to control scheduled tasks programmatically.
Practical examples include:
- Creating a recurring schedule that triggers a webhook at specified intervals.
- Pausing or resuming an existing schedule based on external conditions.
- Triggering a schedule manually outside its normal timing.
- Retrieving details of one or many schedules for monitoring or reporting.
Properties
| Name | Meaning |
|---|---|
| Schedule ID | The unique identifier of the schedule to operate on (required for pause, resume, get, delete, trigger operations). |
Output
The node outputs JSON data representing the response from the Kronos API for the requested operation. For example:
- When pausing a schedule, it returns confirmation or status information about the paused schedule.
- When retrieving schedules, it returns schedule objects with their properties.
- When triggering a schedule, it returns the result of the trigger action.
The output is always structured as JSON under the json field. There is no binary data output.
Dependencies
- Requires an API key credential for authenticating with the Kronos API.
- The base URL for the Kronos API is obtained from the credentials.
- Uses HTTP requests to communicate with the Kronos REST endpoints.
Troubleshooting
- Common issues:
- Invalid or missing Schedule ID when required will cause errors.
- Network or authentication failures with the Kronos API.
- Incorrect cron expressions or date/time formats when creating schedules.
- Error messages:
- If the operation is not supported, the node throws an error indicating the unsupported operation.
- API errors return detailed messages from the Kronos service; these are logged and can be inspected in the node's execution logs.
- Resolutions:
- Ensure all required parameters like Schedule ID are provided.
- Verify API credentials and network connectivity.
- Validate cron expressions and date/time inputs before running the node.
Links and References
- Kronos API Documentation (for timezone and scheduling API references)
- Cron Expression Tutorial (helpful for creating valid cron expressions)