Actions57
- Label Actions
- Project Actions
- Add a Team
- Add a User
- Create
- Create a Kanban Bucket
- Create a Link Share
- Create a Project View
- Delete
- Delete a Kanban Bucket
- Delete a Link Share
- Delete a Project View
- Duplicate
- Get
- Get All Link Shares
- Get All Project Views
- Get All Teams
- Get All Users
- Remove a Team From a Project
- Remove a User From a Project
- Update
- Update a Kanban Bucket
- Update a Project View
- Update a Team's Rights on a Project
- Update a User's Rights on a Project
- Task Actions
- Team Actions
- Webhook Actions
Overview
This node integrates with the Vikunja task management API to manage relationships between tasks. Specifically, the "Remove a Relation" operation under the "Task" resource allows users to delete an existing relation between two tasks. This is useful in scenarios where task dependencies or associations have changed and need to be updated to reflect the current workflow.
Practical examples include:
- Removing a "blocked" relation when a blocking issue has been resolved.
- Detaching subtasks from a parent task if they are no longer relevant.
- Clearing duplicate or copied task links that were created by mistake.
Properties
| Name | Meaning |
|---|---|
| Task ID | The unique identifier of the primary task from which the relation will be removed. |
| Other Task ID | The unique identifier of the other task involved in the relation to be removed. |
| Relation Kind | The type of relation between the two tasks. Options include: Blocked, Blocking, Copied To, Copied From, Duplicate Of, Duplicates, Follows, Parent Task, Precedes, Related Task, Sub Task. |
Output
The node outputs JSON data representing the result of the remove relation operation. Typically, this would confirm whether the relation was successfully deleted or provide details about the updated task state. There is no indication that binary data is output by this node.
Dependencies
- Requires an active connection to the Vikunja API via an API key credential.
- The base URL for the API must be configured in the node credentials.
- The node sends HTTP requests with JSON payloads to interact with the Vikunja backend.
Troubleshooting
Common Issues:
- Invalid or missing Task IDs can cause errors; ensure both Task ID and Other Task ID are correct and exist.
- Incorrect Relation Kind values may lead to failed requests; use one of the predefined options.
- Network or authentication failures if the API URL or credentials are misconfigured.
Error Messages:
- Authorization errors typically indicate invalid or expired API credentials.
- Not found errors suggest that one or both task IDs do not exist.
- Validation errors may occur if required properties are missing or malformed.
To resolve these issues, verify all input parameters, check API credentials, and ensure network connectivity to the Vikunja server.