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 API to manage tasks and their assignments. Specifically, for the "Remove an Assigned User From a Task" operation, it removes a user assignment from a specified task. This is useful in scenarios where task responsibilities change or need to be updated dynamically within a project management workflow.
Practical examples include:
- Unassigning a team member who is no longer responsible for a task.
- Automating cleanup of task assignments when users leave a project.
- Adjusting workload distribution by removing users from tasks programmatically.
Properties
| Name | Meaning |
|---|---|
| Task ID | The unique identifier of the task from which the user will be unassigned. |
| User ID | The unique identifier of the user to remove from the task's assigned users. |
Output
The node outputs JSON data representing the result of the unassignment operation. Typically, this includes confirmation that the user was successfully removed from the task. The exact structure depends on the Vikunja API response but generally contains status information and possibly the updated task details.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Vikunja API.
- Needs an API authentication token configured in the node credentials to authorize requests.
- The base URL for the Vikunja instance must be set correctly in the credentials.
Troubleshooting
Common issues:
- Invalid or missing Task ID or User ID can cause the operation to fail.
- Network connectivity problems or incorrect API URL configuration may prevent communication with the Vikunja server.
- Insufficient permissions for the API token might block user unassignment actions.
Error messages:
- "Task not found" indicates the provided Task ID does not exist; verify the ID.
- "User not assigned to task" means the specified user is not currently assigned; check user-task association.
- Authentication errors suggest invalid or expired API credentials; update or reauthenticate as needed.