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, projects, labels, teams, and webhooks. Specifically, for the "Remove an Assigned User From a Task" operation under the "Task" resource, it allows users to unassign a user from a given task by specifying the task ID and the user ID. This is useful in scenarios where task responsibilities need to be updated dynamically, such as when a team member is no longer responsible for a particular task or when reassigning workload.
Practical examples include:
- Removing a user who has completed their part of a task.
- Adjusting task assignments after team changes.
- Automating cleanup of task assignments based on project status updates.
Properties
| Name | Meaning |
|---|---|
| Task ID | The unique identifier of the task from which a user will be removed. |
| User ID | The unique identifier of the user to be unassigned from the specified task. |
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 or details about the updated task state. If the API supports it, the output may contain the updated task object without the specified user in its assigned users list.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Vikunja API via an API key credential.
- The node expects the base URL of the Vikunja instance to be configured in the credentials.
- Proper permissions on the Vikunja API are necessary to modify task assignments.
Troubleshooting
Common Issues:
- Invalid or missing Task ID or User ID can cause the operation to fail.
- Insufficient permissions or invalid API credentials will prevent successful unassignment.
- Network connectivity issues to the Vikunja API endpoint.
Error Messages:
- "Task not found": Verify that the Task ID exists and is correct.
- "User not assigned to task": The specified user is not currently assigned to the task.
- "Unauthorized" or "Forbidden": Check API credentials and permissions.
- "Invalid input": Ensure Task ID and User ID are numbers and properly provided.
Resolving these typically involves verifying input values, checking API credentials, and ensuring network access to the Vikunja server.