Overview
This node integrates with the Kaizen app to automate event management within a calendar. Specifically, for the Event - Create operation, it allows users to create new calendar events by specifying essential details such as title, start and end times, and whether the event lasts all day. Additional optional fields like color tags, location, notes, priority, reminders, and tags can also be set to enrich the event data.
Common scenarios where this node is beneficial include:
- Automatically scheduling meetings or appointments based on triggers from other apps.
- Creating reminders or events from form submissions or CRM updates.
- Syncing events from external sources into the Kaizen calendar.
Practical example: After receiving a booking confirmation via email, this node can create a corresponding event in the Kaizen calendar with all relevant details, including location and reminder time.
Properties
| Name | Meaning |
|---|---|
| Title | The name or title of the event to be created. |
| Start Time | The starting date and time of the event. |
| End Time | The ending date and time of the event. |
| All Day | Boolean flag indicating if the event lasts the entire day (true) or has specific times (false). |
| Optional Fields | A collection of additional optional properties: |
| - Color Tag | A color code/tag to categorize or highlight the event visually. |
| - Location | The physical or virtual location where the event will take place. |
| - Notes | Any additional notes or description related to the event. |
| - Priority | Numeric priority level assigned to the event. |
| - Reminder | DateTime value specifying when a reminder should trigger before the event. |
| - Tags (Comma Separated) | Comma-separated list of tags to label or group the event. |
Output
The node outputs an array of JSON objects representing the created event(s). Each object contains the full details of the event as returned by the Kaizen API, including all submitted fields and any additional metadata generated by the service.
No binary data output is involved.
Example output structure (simplified):
[
{
"id": "event_id_string",
"title": "Event Title",
"startTime": "2024-06-01T09:00:00.000Z",
"endTime": "2024-06-01T10:00:00.000Z",
"isAllDay": false,
"colorTag": "#ff0000",
"location": "Conference Room A",
"notes": "Discuss project milestones",
"priority": 1,
"reminder": "2024-06-01T08:45:00.000Z",
"tags": ["meeting", "project"]
}
]
Dependencies
- Requires an authenticated connection to the Kaizen API using OAuth2 credentials.
- The node uses the Kaizen cloud API endpoint at
https://us-central1-kaizen-a1281.cloudfunctions.net/api. - The node depends on the
luxonlibrary internally for date-time parsing and formatting according to the workflow's timezone.
Troubleshooting
- Invalid Date/Time Format: If the start or end time is not in ISO format or invalid, the API may reject the request. Ensure date/time inputs are correctly formatted and valid.
- Missing Required Fields: The node requires
Title,Start Time, andEnd Time. Omitting these will cause errors. - Authentication Errors: Failure to authenticate with the Kaizen API will result in authorization errors. Verify that the OAuth2 credentials are correctly configured and valid.
- API Rate Limits or Network Issues: Temporary network failures or rate limiting by the Kaizen API could cause request failures. Retry or check API usage limits.
- Tags Parsing: Tags must be provided as a comma-separated string; improper formatting may lead to empty or incorrect tag arrays.
Links and References
- Kaizen App Official Website
- Kaizen API Documentation (Assumed, please verify actual URL)
- Luxon Date-Time Library