Actions10
Overview
This node integrates with the Dragon Family API to manage and retrieve family-related tasks and todos, specifically focusing on children’s task assignments and progress tracking. The "Member" resource with the "List Todos" operation allows users to fetch a filtered list of todo tasks assigned to a specific child (assignee) on a particular date.
Practical scenarios include:
- Retrieving daily tasks assigned to a child for monitoring or reporting.
- Filtering todos by date to track completed or pending tasks.
- Integrating with other workflow steps to automate reminders or rewards based on task completion.
Example: A parent or educator can use this node to pull all tasks assigned to a child on a given day and then send notifications or update dashboards accordingly.
Properties
| Name | Meaning |
|---|---|
| Base URL | The base URL of the Dragon Family API. Default is https://api.dragonfamily.com. |
| User Token | Your API access token used for authentication; sent as a Bearer token in the Authorization header. |
| Assignee | The ID of the child (executor) whose todos you want to list. |
| Date | The date to filter todos by, formatted as YYYY-MM-DD. |
Output
The output JSON contains the list of todos filtered by the specified assignee and date. Each item in the output represents a todo task with its associated details as returned by the Dragon Family API. The exact structure depends on the API response but typically includes fields such as task title, description, status, due date, and related metadata.
No binary data output is indicated for this operation.
Dependencies
- Requires an active internet connection to reach the Dragon Family API endpoint.
- Needs a valid API access token (User Token) for authorization.
- The node uses HTTP requests with JSON payloads and expects JSON responses.
- No additional external libraries beyond n8n's built-in HTTP request helper are required.
Troubleshooting
- Invalid or missing API token: If the token is incorrect or absent, the API will likely return an authorization error. Ensure the token is valid and correctly entered.
- Incorrect Assignee ID: Providing an invalid or non-existent assignee ID may result in empty results or errors. Verify the assignee ID corresponds to a valid child in the system.
- Date format issues: The date must be in
YYYY-MM-DDformat. Incorrect formatting may cause the API to reject the request or return no data. - Network or connectivity problems: Ensure that the base URL is reachable and there are no firewall or network restrictions blocking the request.
- API changes or downtime: If the Dragon Family API changes or is temporarily unavailable, the node may fail. Check the API status and update the base URL or token if necessary.
Links and References
- Dragon Family API Documentation (Assumed URL for reference)
- n8n HTTP Request Node Documentation
- Date Format Reference - ISO 8601