KronosInstall

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. This is useful for automating time-based workflows, notifications, or any process that requires scheduled execution.

For example, you can use this node to:

• Create a recurring schedule that triggers a webhook at specified intervals.
• Delete an obsolete schedule by its ID.
• Pause or resume schedules dynamically based on external conditions.
• Trigger a schedule manually outside its normal timing.

The "Delete Schedule" operation specifically removes a schedule identified by its unique Schedule ID from the Kronos system.

Properties

Output

The node outputs JSON data representing the response from the Kronos API for the requested operation.

• For the "Delete Schedule" operation, the output JSON typically contains confirmation of deletion or relevant status information returned by the API.
• For other operations, the output JSON includes schedule details or lists of schedules.
• No binary data output is produced by this node.

Each output item is paired with the corresponding input item for traceability.

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 expects JSON responses.
• Timezone conversions are handled internally using the timeapi.io service to convert date-time values to UTC when creating schedules.

Troubleshooting

• Common issues:

  • Invalid or missing Schedule ID when performing delete or other schedule-specific operations will cause errors.
  • Incorrect API credentials or network issues may result in authentication failures or request timeouts.
  • Malformed JSON in metadata fields can cause parsing errors.
  • Timezone conversion failures if invalid timezone strings are provided.

• Error messages:

  • "The operation \"<operation>\" is not supported!": Indicates an unsupported operation was selected; verify the operation name.
  • API error responses include detailed messages logged by the node; check these logs for specific causes.
  • JSON parsing errors for metadata indicate invalid JSON syntax; ensure proper formatting.

• Resolutions:

  • Double-check the Schedule ID and ensure it exists in Kronos before attempting deletion.
  • Verify API credentials and network connectivity.
  • Validate JSON inputs using online validators.
  • Use valid timezone names as per the loaded options from the node.

Links and References

• Kronos API Documentation (for timezone and scheduling API references)
• Cron Expression Tutorial (helpful for creating cron expressions used in recurring schedules)
• n8n Expressions Documentation (for dynamic property values)