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 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 update project team membership dynamically, such as automating user access control or cleaning up project collaborators after task completion.
Practical examples:
- Automatically removing a user from a project when they leave a team.
- Managing project permissions by syncing user lists from an external system.
- Cleaning up project memberships during project archival workflows.
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 that the user was successfully removed or details about the updated project state. There is no indication that binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating with the Vikunja API.
- Needs the base URL of the Vikunja instance configured in the credentials.
- Uses HTTP requests to interact with the Vikunja REST API endpoints.
Troubleshooting
Common issues:
- Providing an invalid project ID or user ID will cause the operation to fail.
- Network connectivity problems or incorrect API URL configuration can prevent successful API calls.
- Insufficient permissions for the API key may result in authorization errors.
Error messages and resolutions:
- "User not found in project": Verify the user ID and ensure the user is currently part of the project.
- "Project not found": Confirm the project ID or selection is correct.
- Authentication errors: Check that the API key credential is valid and has necessary permissions.
- Network errors: Ensure the Vikunja API URL is reachable from the n8n environment.