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 relations between tasks. Specifically, the "Remove a Relation" operation under the "Task" resource allows users to delete an existing relationship 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.
- Deleting a "duplicate" relation if two tasks were mistakenly linked as duplicates.
- Clearing a "subtask" relation when a subtask is no longer relevant to its parent task.
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 API key credential for authenticating with the Vikunja API.
- Needs the base URL of the Vikunja instance configured in the node credentials.
- The node sends HTTP requests to the Vikunja API endpoints to perform operations.
Troubleshooting
Common Issues:
- Invalid or missing Task IDs can cause the API to return errors indicating the task or relation does not exist.
- Incorrect relation kind values may lead to failure in identifying the correct relation to remove.
- Network or authentication issues with the Vikunja API can prevent successful execution.
Error Messages:
- "Relation not found" — Verify that the specified relation exists between the given tasks.
- "Unauthorized" or "Authentication failed" — Check that the API key credential is correctly set up and valid.
- "Invalid Task ID" — Ensure that both Task ID and Other Task ID are correct and correspond to existing tasks.
Resolving these typically involves verifying input parameters, ensuring proper API credentials, and confirming network connectivity.
Links and References
- Vikunja API Documentation (for detailed API endpoint info)
- n8n Documentation on Creating Custom Nodes