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
- Team Actions
- Task 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. This functionality is useful for project management workflows where task dependencies and relationships need to be clearly defined and tracked.
Practical examples include:
- Linking a task that must be completed before another can start (using "Blocked" or "Blocking").
- Organizing subtasks under a main task ("Sub Task" or "Parent Task").
- Marking duplicate tasks to avoid redundant work.
- Establishing general relatedness between tasks for better context.
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 kind of relation between tasks. Options: Blocked, Blocking, Coped 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 or the updated task state. There is no binary data output.
Dependencies
- Requires an API key credential for authenticating with the Vikunja API.
- Needs the base URL of the Vikunja instance configured in the credentials.
- The node sends HTTP requests to the Vikunja API endpoints.
Troubleshooting
Common issues:
- Invalid or missing Task IDs may cause errors; ensure both Task ID and Other Task ID are valid numbers corresponding to existing tasks.
- Incorrect API URL or authentication failures will prevent the node from connecting to Vikunja.
- Using unsupported relation kinds or malformed request bodies could lead to API errors.
Error messages:
- Authentication errors usually indicate invalid or missing API credentials.
- 404 errors suggest that one or both task IDs do not exist.
- Validation errors may occur if required properties are missing or incorrectly formatted.
To resolve these, verify all input parameters, check API credentials, and confirm the existence of referenced tasks in Vikunja.