Actions10
Overview
This node integrates with the Dragon Family API to create and manage tasks (todos) for members. Specifically, the "Create Single Todo" operation allows users to create a one-time task assigned to one or more profiles on a specified date. This is useful for task management scenarios where you want to assign specific responsibilities or goals to members of a group or family, track rewards, and optionally use predefined templates.
Practical examples:
- Assigning a chore or responsibility to children in a family on a particular day.
- Creating a custom task with a reward system for team members.
- Using a template to quickly generate common tasks with preset details.
Properties
| Name | Meaning |
|---|---|
| Base URL | The base URL for the Dragon Family API (default: https://api.dragonfamily.com). |
| User Token | Your API access token, sent as a Bearer token in the Authorization header. |
| Assignees | Comma-separated list of profile IDs to assign the todo to (e.g., "1001,1002"). |
| Template ID | Optional ID of a todo template to create the task from. If provided, other fields may be ignored. |
| Title | Title of the todo task; required if no template is specified. |
| Date | Task date in YYYY-MM-DD format; required for single todo creation. |
| Dragons | Optional reward amount associated with the task; if omitted, may come from the template. |
| Description | Optional description text for the todo. |
| Image ID | Optional image identifier associated with the todo. |
Output
The node outputs a JSON object representing the created todo item as returned by the Dragon Family API. This typically includes details such as the todo's ID, title, date, assignees, reward information, and any other metadata the API provides.
If the API supports binary data related to todos (e.g., images), this node does not explicitly handle binary output in this operation.
Dependencies
- Requires access to the Dragon Family API endpoint.
- Needs a valid API access token to authenticate requests via the Authorization header using Bearer token scheme.
- The node uses HTTP POST requests to the
/scheduler/v3/todo/create/endpoint of the Dragon Family API. - No additional external dependencies beyond standard HTTP request capabilities.
Troubleshooting
- Missing or invalid token: If the API token is missing or incorrect, the API will likely return an authentication error. Ensure the token is correctly set and has appropriate permissions.
- Invalid date format: The
dateproperty must be inYYYY-MM-DDformat. Incorrect formats may cause API errors. - Empty or invalid assignees: Assignees should be comma-separated numeric profile IDs. Invalid formatting or non-numeric values may cause failures.
- Template vs Title conflict: If both a template ID and a title are provided, the template takes precedence. Omitting both will cause the API to reject the request.
- API endpoint unreachable: Verify the base URL is correct and accessible from your environment.
- Unexpected API response: Check the API documentation for changes or additional required fields if the request fails.
Links and References
- Dragon Family API Documentation (Assumed URL based on base URL; replace with actual if available)
- n8n HTTP Request Node documentation for understanding how HTTP calls are made within n8n workflows.