Actions16
- Conversation Actions
- Todo Actions
- Fact Actions
- Location Actions
Overview
The node interacts with the BeeAI API to manage "Todo" items. Specifically, the "Update Todo" operation allows users to modify existing todo entries by specifying their ID and updating fields such as the text description, an optional alarm time, and completion status.
This node is useful in automation workflows where task management needs to be integrated, for example:
- Updating a task's details based on user input from a form.
- Marking tasks as completed automatically after certain triggers.
- Adjusting reminders or alarms for tasks dynamically.
Properties
| Name | Meaning |
|---|---|
| Todo ID | The unique identifier of the todo item to update. |
| Text | The updated text content or description of the todo item. |
| Alarm At (Optional) | An optional timestamp string indicating when an alarm/reminder should trigger for the todo. |
| Completed | A boolean flag indicating whether the todo item is marked as completed (true) or not (false). |
Output
The node outputs JSON data representing the updated todo item as returned by the BeeAI API. This typically includes the todo's ID, updated text, alarm time if set, completion status, and possibly other metadata related to the todo.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the BeeAI API.
- The node sends requests to the base URL
https://api.bee.computer. - Proper configuration of the API key credential within n8n is necessary for successful communication.
Troubleshooting
- Invalid Todo ID: If the provided Todo ID does not exist, the API may return an error indicating the resource was not found. Verify the ID before running the node.
- Missing Required Fields: The "Text" and "Completed" properties are required for update operations. Omitting these may cause validation errors.
- Authentication Errors: Ensure the API key credential is correctly configured and has sufficient permissions.
- Incorrect Date Format for Alarm: The "Alarm At" field expects a valid date-time string. Invalid formats might lead to request failures.
- API Rate Limits: Frequent updates may hit rate limits imposed by the BeeAI API; handle such errors by implementing retries or backoff strategies.
Links and References
- BeeAI API Documentation (hypothetical link for reference)
- n8n Documentation on Creating Custom Nodes