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 add a relation between two tasks. It allows users to define how one task is related to another, such as marking one task as blocking another, setting parent-child relationships, or indicating duplicates.
Common scenarios include:
- Structuring tasks by defining dependencies (e.g., "Task A blocks Task B").
- Organizing subtasks under a main task.
- Linking duplicate tasks for better tracking.
- Establishing task sequences like "follows" or "precedes".
Practical example: You have two tasks in your project, and you want to indicate that Task 123 is blocked by Task 456. Using this node, you specify these task IDs and set the relation kind to "Blocked" to create this dependency in Vikunja.
Properties
| Name | Meaning |
|---|---|
| Task ID | The ID of the primary task to which you want to add a relation. |
| Other Task ID | The ID of the other task you want to relate the current one with. |
| Relation Kind | The type of relation between the two tasks. Options: 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 API call to add the relation. This typically includes confirmation details about the created relation, such as the involved task IDs and the relation kind.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Vikunja API via an API key credential.
- The base URL for the Vikunja API must be configured in the node credentials.
- The node sends authenticated HTTP requests to the Vikunja server to manage task relations.
Troubleshooting
- Invalid Task IDs: If either Task ID does not exist or is incorrect, the API will return an error. Verify that both task IDs are valid and accessible.
- Permission Issues: Insufficient permissions on the Vikunja server may cause authorization errors. Ensure the API key has rights to modify tasks.
- Relation Kind Errors: Providing an unsupported relation kind value will cause the request to fail. Use one of the predefined options.
- Network/Connection Problems: Check network connectivity and the correctness of the API base URL if requests time out or fail.
Links and References
- Vikunja API Documentation – Official API reference for task relations and other operations.
- Vikunja Project Website – General information about Vikunja task management system.