Actions7
Overview
This node integrates with the Kronos API to manage schedules programmatically. It supports operations such as creating, retrieving, deleting, pausing, resuming, and triggering schedules. This is useful for automating time-based workflows, notifications, or task executions that depend on scheduled events.
Practical examples include:
- Creating a recurring schedule to trigger a webhook every day at a specific time.
- Retrieving details of an existing schedule by its ID.
- Pausing or resuming schedules based on external conditions.
- Triggering a schedule manually outside its normal timing.
Properties
| Name | Meaning |
|---|---|
| Schedule ID | The unique identifier of the schedule to operate on (required for get, delete, pause, resume, trigger operations). |
Output
The node outputs JSON data representing the response from the Kronos API for the requested operation:
- For Get Schedule, it returns the detailed information of the specified schedule.
- For Get Many Schedules, it returns an array of schedule objects, optionally filtered by title or metadata.
- For Create Schedule, it returns the created schedule's details.
- For Delete Schedule, Pause Schedule, Resume Schedule, and Trigger Schedule, it returns the API response confirming the action.
The output JSON structure corresponds directly to the Kronos API responses and includes fields like schedule ID, title, description, recurrence settings, cron expression, start/end times, timezone, URL, and metadata.
No binary data output is produced by this node.
Dependencies
- Requires an active Kronos API credential configured in n8n with appropriate permissions.
- Uses the Kronos API base URL from the credential.
- Makes HTTP requests to the Kronos API endpoints.
- Converts date/time values to UTC ISO strings using helper functions before sending to the API.
- Loads available timezones dynamically from an external time API service.
Troubleshooting
- Invalid Schedule ID: If the provided Schedule ID does not exist or is malformed, the API will return an error. Verify the ID is correct.
- Authentication Errors: Ensure the Kronos API credential is valid and has necessary access rights.
- Date/Time Conversion Issues: Incorrect timezone or date formats may cause scheduling errors. Use the provided timezone options and ensure dates are valid.
- API Rate Limits or Network Issues: Network failures or rate limiting by the Kronos API can cause request failures. Check connectivity and API usage limits.
- JSON Parsing Errors: When providing metadata filters or metadata JSON, ensure the JSON syntax is correct to avoid parsing errors.
If the node encounters an error and "Continue On Fail" is enabled, it will output an error object instead of stopping execution.
Links and References
- Kronos API Documentation (for timezone and conversion APIs used)
- Cron Expression Tutorial (helpful for creating cron expressions)
- n8n Expressions Documentation (for dynamic property values)