Actions16
- Conversation Actions
- Todo Actions
- Fact Actions
- Location Actions
Overview
The node interacts with the BeeAI API to perform operations on various resources, including Todos. Specifically, the "Get Todo" operation retrieves a single todo item by its ID. This is useful in scenarios where you need to fetch details of a specific task or reminder stored in the BeeAI system.
Practical examples include:
- Fetching a todo item to display its details in a workflow.
- Retrieving a todo before updating or deleting it.
- Using the todo data as input for further processing or notifications.
Properties
| Name | Meaning |
|---|---|
| Todo ID | The unique identifier of the todo item to get. This is required and must be provided as a string. |
Output
The output contains a JSON object representing the retrieved todo item from the BeeAI API. The structure typically includes all properties of the todo such as its ID, title, description, status, creation date, and any other metadata provided by the API.
If the node supports binary data output (not indicated here), it would represent associated files or attachments related to the todo, but this is not evident from the provided code.
Dependencies
- Requires an API key credential for authenticating with the BeeAI API.
- The base URL for API requests is
https://api.bee.computer. - Proper configuration of the API key credential within n8n is necessary for successful requests.
Troubleshooting
- Missing or invalid Todo ID: The node requires a valid todo ID. Ensure that the ID is correctly provided and corresponds to an existing todo.
- Authentication errors: Verify that the API key credential is correctly set up and has the necessary permissions.
- Network issues or API downtime: Check connectivity to
https://api.bee.computerand confirm the BeeAI service status. - Unexpected API responses: If the todo ID does not exist, the API may return an error or empty response. Handle such cases gracefully in your workflow.
Links and References
- BeeAI API Documentation (assumed, based on base URL)
- n8n documentation on API credentials