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 scheduling system. It allows users to modify details such as the time, description, participants, and whether the event lasts all day. This is useful for workflows that need to programmatically adjust calendar events or appointments, for example, updating meeting times or adding participants based on external triggers.
Practical examples:
- Automatically rescheduling meetings when a related project deadline changes.
- Adding or removing participants from an event based on user input or other workflow data.
- Updating event descriptions with additional information gathered during a workflow.
Properties
| Name | Meaning |
|---|---|
| Bucket Id | Numeric identifier of the bucket (calendar or project container) where the entry exists. |
| Entry Id | Numeric identifier of the specific schedule entry to update. |
| Summary | Text summary or title describing what the schedule entry is about. |
| Starts At | ISO 8601 timestamp indicating when the schedule entry begins. |
| Ends At | ISO 8601 timestamp indicating when the schedule entry ends. |
| Description | Detailed information about the schedule entry; supports HTML formatting. |
| Participant Ids | JSON array of numeric IDs representing people who will participate in the event. |
| All Day | Boolean flag indicating if the event lasts the entire day (true) or not (false). |
Output
The node outputs JSON data representing the updated schedule entry. This typically includes the updated fields such as summary, start and end times, description, participant list, and all-day status. The output can be used downstream in workflows to confirm the update or trigger further actions.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the scheduling service.
- Needs configuration of the base URL including the account or workspace ID.
- Depends on the external scheduling API to perform the update operation.
Troubleshooting
- Invalid IDs: Errors may occur if the provided Bucket Id or Entry Id do not exist or are incorrect. Verify these IDs before running the node.
- Date format issues: Ensure that "Starts At" and "Ends At" use valid ISO 8601 date-time strings to avoid parsing errors.
- Participant Ids format: The participant IDs must be a valid JSON array of numbers; malformed JSON or invalid IDs can cause failures.
- Authentication errors: If the API key or authentication token is missing or invalid, the node will fail to connect to the service.
- Permission errors: The authenticated user must have permission to update schedule entries in the specified bucket.
Links and References
- ISO 8601 Date Format
- Documentation for the scheduling API (not provided here, but typically available from the service provider)