Actions7
Overview
The Kronos node allows users to interact with the Kronos API to manage schedules programmatically. It supports operations such as creating, deleting, retrieving, pausing, resuming, and triggering schedules. This node is useful in automation workflows where scheduling tasks or notifications based on time is required.
For example, you can use this node to:
- Create recurring or one-time schedules that trigger webhooks at specified times.
- Pause or resume existing schedules dynamically.
- Retrieve details of specific schedules or list multiple schedules with filtering options.
- Trigger a schedule manually outside its normal timing.
This flexibility makes it ideal for integrating time-based triggers into complex automation pipelines.
Properties
| Name | Meaning |
|---|---|
| Schedule ID | The unique identifier of the schedule to operate on. Required for delete, get, pause, resume, and trigger operations. |
| Operation | The action to perform on schedules: Create Schedule, Delete Schedule, Get Many Schedules, Get Schedule, Pause Schedule, Resume Schedule, Trigger Schedule. |
| Title | The name of the schedule (must be unique). Used when creating a schedule. |
| Description | Optional description of the schedule. |
| Is Recurring | Boolean indicating if the schedule repeats (true) or is one-time (false). |
| Cron Expression | Cron syntax string defining the recurrence pattern for recurring schedules. |
| URL | Webhook endpoint URL to notify when the schedule triggers. |
| Run At | DateTime for when a non-recurring schedule should run. |
| Start At | UTC start date/time for recurring schedules. |
| End At | UTC end date/time for recurring schedules. |
| Timezone | Timezone for the schedule's timing, selectable from a list of valid timezones. |
| Metadata File | Optional JSON metadata sent when triggering the webhook. |
| Return All | Boolean to return all schedules or limit results when listing many schedules. |
| Limit | Maximum number of schedules to return when not returning all. |
| Filter by Title | Case-insensitive filter string to match schedule titles when listing schedules. |
| Filter by Metadata | JSON object to filter schedules by matching metadata key-value pairs. |
Output
The node outputs JSON data representing the response from the Kronos API for the requested operation:
- For single schedule operations (get, create, delete, pause, resume, trigger), the output JSON contains the schedule details or confirmation response.
- For "Get Many Schedules," the output is an array of schedule objects, optionally filtered by title or metadata and limited by count.
- Each output item is paired with the corresponding input item index.
No binary data is produced by this node.
Dependencies
- Requires an API authentication credential configured in n8n to access the Kronos API.
- Uses the Kronos API base URL from the credential configuration.
- Relies on external HTTP requests to the Kronos API endpoints.
- Supports dynamic loading of timezone options via an external time API.
Troubleshooting
Common issues:
- Invalid or missing Schedule ID when performing operations that require it.
- Incorrect cron expression format for recurring schedules.
- Timezone values not properly set or unsupported.
- Network or authentication errors connecting to the Kronos API.
Error messages:
"The operation \"<operation>\" is not supported!"indicates an invalid operation parameter.- API error responses are logged and included in the node output if "Continue On Fail" is enabled.
- Authentication failures due to missing or invalid API credentials.
Resolutions:
- Ensure all required parameters are provided and correctly formatted.
- Validate cron expressions using external tools before input.
- Confirm API credentials are correctly configured and have necessary permissions.
- Check network connectivity and API endpoint availability.
Links and References
- Cron Expression Tutorial
- Kronos API Documentation (for timezone and time conversion references)
- n8n Expressions Documentation (for dynamic property values)