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 teams and their users. Specifically, the "Remove a User From a Team" operation allows you to remove a specified user from a given team within Vikunja. This is useful in scenarios where team membership needs to be updated dynamically, such as when a user leaves a project or organization, or when access permissions need to be adjusted.
Practical examples:
- Automatically removing a user from a team when they are deactivated in your HR system.
- Managing team memberships based on project assignments by adding or removing users programmatically.
Properties
| Name | Meaning |
|---|---|
| Team Name or ID | The team to operate on. You can select a team from a searchable list or specify its ID directly. |
| User ID | The numeric identifier of the user to remove from the selected team. |
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 an error message if the operation failed. The exact structure depends on the Vikunja API response but generally includes status information.
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 API endpoint is necessary.
Troubleshooting
Common issues:
- Providing an invalid team 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 lead to connection failures.
Error messages:
- Errors indicating "team not found" or "user not found" suggest incorrect IDs.
- Authentication errors imply issues with the provided API key or credentials.
- Timeout or network errors indicate connectivity problems.
Resolution tips:
- Verify that the team and user IDs are correct and exist in Vikunja.
- Ensure the API key has sufficient permissions to modify team memberships.
- Confirm the API URL is correctly set without trailing slashes.
- Check network connectivity and firewall settings.