Actions7
Overview
The Kronos node allows users to interact with the Kronos scheduling API, primarily to manage schedules that trigger webhook notifications. The "Create Schedule" operation enables creating either recurring or one-time schedules with detailed configuration such as timing, recurrence pattern, and metadata.
This node is beneficial in automation workflows where timed triggers are needed, for example:
- Scheduling periodic data syncs or reports using cron expressions.
- Setting up one-off reminders or notifications at a specific date and time.
- Triggering webhooks to external systems based on custom schedules.
Practical example: Create a recurring schedule that triggers a webhook every Monday at 9 AM UTC to start a weekly report generation process.
Properties
| Name | Meaning |
|---|---|
| Title | The unique name of your schedule. |
| Description | Optional description providing additional details about the schedule. |
| Is Recurring | Boolean indicating if the schedule repeats (true) or is a one-time event (false). |
| Cron Expression | Cron syntax string defining the recurrence pattern; required if "Is Recurring" is true. |
| URL | Webhook endpoint URL that will be called when the schedule triggers. |
| Run At | DateTime specifying the exact trigger time for non-recurring schedules. |
| Start At | UTC start date/time for recurring schedules indicating when the schedule becomes active. |
| End At | UTC end date/time for recurring schedules indicating when the schedule stops being active. |
| Timezone | Timezone context for the schedule's timing, selectable from a list or via expression. |
| Metadata File | Optional JSON object containing metadata sent along with the webhook trigger notification. |
Output
The node outputs JSON data representing the response from the Kronos API for the created schedule. This typically includes all details of the newly created schedule such as its ID, title, timing settings, URL, and metadata.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Kronos API.
- The node makes HTTP requests to the Kronos API endpoints.
- Uses an external timezone API to load available timezones and convert dates between timezones.
Troubleshooting
- Invalid Cron Expression: If the cron expression is malformed, the API may reject the request. Verify the cron syntax before submitting.
- Timezone Conversion Errors: Incorrect or unsupported timezone values can cause failures in date conversion. Use the provided timezone options or valid IANA timezone strings.
- Unique Title Constraint: The schedule title must be unique. Attempting to create a schedule with a duplicate title may result in an error.
- API Authentication Failures: Ensure the API key credential is correctly configured and has necessary permissions.
- Malformed Metadata JSON: The metadata property expects valid JSON. Invalid JSON will cause parsing errors.
- Network or API Errors: The node logs detailed request and response information which can help diagnose connectivity or server-side issues.
Links and References
- Cron Expression Tutorial
- IANA Time Zone Database
- n8n Expressions Documentation (for dynamic timezone input)