Actions18
- Attachment Actions
- Comment Actions
- Dartboard Actions
- Doc Actions
- Folder Actions
- Help Center Article Actions
- Skill Actions
- Task Actions
- View Actions
Overview
The node integrates with the Dart project management platform to update an existing task. It allows users to modify various aspects of a task such as assignees, tags, custom properties, and relationships with other tasks. This is useful for automating updates in project workflows, ensuring task details stay current without manual intervention.
Practical examples include:
- Automatically updating task status or priority based on external triggers.
- Adding or removing assignees when team members change.
- Adjusting custom fields like due dates or labels programmatically.
- Managing task dependencies by updating related subtasks or blockers.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the task to update. This is required to specify which task will be modified. |
| Item | A JSON object representing the updated task data. It includes: - assignees: List of users assigned to the task.- tags: List of tags associated with the task.- customProperties: Various custom fields such as checkboxes, dates, multi-selects, numbers (with formats like percentage or currency), select options, status, text notes, and user references.- taskRelationships: Defines relationships with other tasks including subtasks, blockers, blocking tasks, duplicates, and related tasks. |
Output
The node outputs the updated task data in the json field of the output item. This JSON reflects the current state of the task after the update operation, including all standard and custom properties as well as relationship links.
If the node supports binary data output, it would typically represent attachments or files related to the task, but this is not indicated in the provided code or properties.
Dependencies
- Requires an API key credential for authenticating with the Dart service.
- Needs the Dart API base URL configured in the credentials.
- The node sends requests with JSON content type and expects JSON responses.
Troubleshooting
Common issues:
- Invalid or missing task ID will cause the update to fail.
- Malformed JSON in the
Itemproperty can lead to request errors. - Insufficient permissions or invalid API credentials may result in authentication errors.
- Updating non-existent custom properties or relationships might cause API rejections.
Error messages:
- "Task not found" indicates the specified ID does not exist.
- "Unauthorized" or "Authentication failed" suggests problems with the API key or credentials.
- "Invalid request body" points to JSON formatting issues in the
Iteminput.
To resolve these, verify the task ID, ensure the JSON structure matches expected schema, and confirm that API credentials are valid and have necessary permissions.
Links and References
- Dart Project Management API Documentation (Replace with actual URL if available)
- n8n documentation on Creating Custom Nodes
- JSON formatting guide for complex objects in n8n inputs