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 API to manage projects and their users. Specifically, the "Remove a User From a Project" operation allows you to remove a specified user from a given project by providing the project identifier and the user's ID. This is useful in scenarios where you need to manage team membership dynamically, such as revoking access when a team member leaves or changes roles.
Practical examples:
- Automatically removing a user from a project when they are no longer assigned tasks within that project.
- Managing project team composition programmatically based on external HR systems or workflows.
- Cleaning up project memberships during project archival or restructuring.
Properties
| Name | Meaning |
|---|---|
| Project Title or ID | The target project to operate on. You can select a project from a searchable list or specify its ID directly. |
| User ID | The numeric ID of the user to be removed from the selected project. |
Output
The node outputs JSON data representing the result of the removal operation. Typically, this will include confirmation of the user being removed or an error message if the operation failed. The exact structure depends on the Vikunja API response but generally confirms success or failure.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Vikunja API.
- The node expects the base URL of the Vikunja instance to be configured in the credentials.
- Network connectivity to the Vikunja server is necessary.
Troubleshooting
Common issues:
- Providing an invalid project ID or user ID will cause the operation to fail.
- Insufficient permissions for the API key may prevent user removal.
- Network errors or incorrect API URL configuration can cause connection failures.
Error messages:
- "User not found in project" — The specified user ID does not belong to the project.
- "Project not found" — The project ID does not exist or is inaccessible.
- Authentication errors — Check that the API key credential is valid and has required permissions.
To resolve these, verify IDs, ensure correct API credentials, and confirm network access.