Actions7
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. The "Get Many Schedules" operation allows users to fetch multiple schedules with optional filtering by title or metadata, and control over how many results to return.
Typical use cases include:
- Automating schedule management workflows.
- Retrieving lists of schedules for reporting or monitoring.
- Filtering schedules based on specific criteria like title keywords or metadata attributes.
For example, a user might retrieve all schedules whose titles contain "backup" and limit the results to 10 entries, enabling automated oversight of backup-related scheduled tasks.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all matching schedules or limit the number of results returned. |
| Limit | Maximum number of schedules to return when "Return All" is false. Minimum value is 1. |
| Filter by Title | Case-insensitive substring filter applied to schedule titles to narrow down results. |
| Filter by Metadata | JSON object used to filter schedules by matching key-value pairs in their metadata field. |
Output
The output is an array of items where each item's json property contains a schedule object retrieved from the Kronos API. Each schedule object includes fields such as its ID, title, description, recurrence settings, timing details, URL, and metadata.
No binary data 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 responses.
- Timezone conversion helper methods are included but not directly relevant to the "Get Many Schedules" operation.
Troubleshooting
- API Errors: If the Kronos API returns errors (e.g., authentication failure, invalid parameters), the node logs the error response. Ensure the API key credential is valid and has sufficient permissions.
- Filtering Issues: Incorrectly formatted JSON in the "Filter by Metadata" property can cause parsing errors. Make sure the JSON is valid.
- Limit Ignored: If "Return All" is set to true, the "Limit" property is ignored; users expecting limited results should disable "Return All".
- Empty Results: Filters that do not match any schedules will result in empty output arrays.
Links and References
- Kronos API Documentation (for timezone info and general API reference)
- n8n Expressions Documentation (for using expressions in properties like timezone)