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 automate project membership management, 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 to it in your HR system.
- Cleaning up project memberships during periodic audits.
- Integrating with other tools to synchronize user permissions across platforms.
Properties
| Name | Meaning |
|---|---|
| Project Title or ID | The 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 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 operation.
Dependencies
- Requires an API key credential for authenticating with the Vikunja API.
- The node uses the base URL configured in the credentials to send requests to the Vikunja server.
- No additional external dependencies beyond the Vikunja API.
Troubleshooting
Common issues:
- Providing an invalid or non-existent project ID or user ID will likely cause errors.
- 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" — Check that the project ID or selected project exists and is accessible.
- Authentication errors — Confirm that the API key credential is valid and has necessary permissions.
- Network errors — Ensure the API URL is correct and the server is reachable.