Actions80
- Card Tables Actions
- Forwards Actions
- Events Actions
- Recordings Actions
- Projects Actions
- People Actions
- Chatbots Actions
- Webhooks Actions
- Attachments Actions
- Templates Actions
- Uploads Actions
- Documents Actions
- Lineup Markers Actions
- Subscriptions Actions
- Schedules Actions
- Schedule Entries Actions
- Todo Sets Actions
- Todo Lists Actions
- Todos Actions
Overview
This node updates an existing schedule entry in a specified bucket within a scheduling system. It is useful for modifying details of calendar events or appointments, such as changing the time, description, participants, or marking it as an all-day event. Practical examples include updating meeting times, adding participants to an event, or correcting event descriptions.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | The identifier of the bucket (calendar or schedule container) where the entry exists. |
| Entry Id | The identifier of the specific schedule entry to update. |
| Summary | A brief title or summary describing what the schedule entry is about. |
| Starts At | The start date and time of the schedule entry in ISO 8601 format. |
| Ends At | The end date and time of the schedule entry in ISO 8601 format. |
| Description | Additional information about the schedule entry; supports HTML formatting. |
| Participant Ids | A JSON array of participant IDs who will be involved in the schedule entry. |
| All Day | Boolean flag indicating whether the event lasts all day (true) or has specific times. |
Output
The node outputs JSON data representing the updated schedule entry as returned by the API. This typically includes the updated fields such as summary, start and end times, description, participants, and all-day status. There is no binary output.
Dependencies
- Requires an API key credential for authenticating with the external scheduling service.
- Needs the base URL configured dynamically based on the user's account or workspace ID.
- Depends on the external scheduling API to perform the update operation.
Troubleshooting
- Invalid Bucket Id or Entry Id: If these identifiers are incorrect or do not exist, the API will likely return an error indicating the resource was not found. Verify the IDs before running the node.
- Malformed Dates: The
Starts AtandEnds Atproperties must be valid ISO 8601 strings. Invalid formats may cause errors or unexpected behavior. - Participant Ids Format: The participant IDs must be provided as a valid JSON array. Improper JSON syntax will cause parsing errors.
- Authentication Errors: Ensure that the API key or authentication token is correctly set up and has sufficient permissions to update schedule entries.
- All Day Flag Conflicts: Setting
All Dayto true while providing specific start and end times might cause conflicts depending on the API's handling of these fields.
Links and References
- Refer to the external scheduling service’s API documentation for detailed information on schedule entry fields and update operations.
- ISO 8601 date format specification: https://en.wikipedia.org/wiki/ISO_8601