Actions15
Overview
The node provides functionality to update a Todo item in a calendar or task collection using the CalDAV protocol. It is useful for managing tasks by modifying their details such as title, description, priority, status, due date, completion date, and progress percentage. Typical use cases include updating task information in personal or shared calendars, syncing task updates across applications, or automating task management workflows.
For example, you can update a task's status to "Completed" and set its completion date when finishing a project milestone, or adjust the priority and due date of a task based on changing requirements.
Properties
| Name | Meaning |
|---|---|
| Calendar URL | The URL path of the calendar or task collection where the todo resides (e.g., /calendars/user@example.com/tasks/). |
| Todo UID | The unique identifier of the todo item to update (e.g., todo-12345@example.com). |
| Summary (Title) | The title or summary of the todo item (e.g., "Complete project documentation"). |
| Description | A detailed description of the todo item. |
| Priority | The priority level of the todo. Options: High (1), Medium (5), Low (9). |
| Status | The current status of the todo. Options: Needs Action, In Progress, Completed, Cancelled. |
| Due Date | The date and time when the todo is due. |
| Completed Date | The date and time when the todo was completed. Only applicable if status is "Completed". |
| Progress Percentage | The completion percentage of the todo, from 0 to 100. |
Output
The node outputs JSON data representing the updated todo item. This typically includes all the properties of the todo after the update, reflecting the new state such as updated summary, status, dates, and progress. If the node supports binary data output (not indicated here), it would represent attachments or related files, but this node focuses on JSON task data.
Dependencies
- Requires access to a CalDAV-compatible calendar or task server.
- Needs an API key or authentication token configured in n8n to authorize requests to the CalDAV service.
- The
Calendar URLmust be correctly specified to point to the target calendar/task collection.
Troubleshooting
- Invalid Calendar URL: Ensure the calendar URL is correct and accessible; otherwise, the update will fail.
- Todo UID Not Found: If the specified todo UID does not exist, the node will error out. Verify the UID before updating.
- Authentication Errors: Check that the API credentials are valid and have sufficient permissions to modify todos.
- Status and Completed Date Mismatch: Setting a completed date without marking status as "Completed" may cause inconsistencies.
- Date Format Issues: Ensure date/time inputs follow the expected format to avoid parsing errors.
Links and References
- CalDAV Protocol Specification
- iCalendar (RFC 5545) Specification
- General CalDAV client libraries and tools documentation for further integration details.
