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 teams and their users. Specifically, the "Remove a User From a Team" operation allows you to remove a specified user from a given team. This is useful in scenarios where team membership needs to be updated dynamically, such as when an employee leaves a project or changes roles.
Practical examples:
- Automatically removing a user from a team when they are no longer assigned to a project.
- Managing team memberships based on external HR system updates.
- Cleaning up team members after project completion.
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 from the team or details about any error encountered. There is no indication that binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating with the Vikunja API.
- The base URL for the Vikunja API must be configured in the node credentials.
- The node uses HTTP requests to interact with the
/teamsendpoint of the Vikunja API.
Troubleshooting
Common issues:
- Providing an invalid or non-existent team 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 associated with the API key may block user removal actions.
Error messages:
- Errors related to "team not found" or "user not found" indicate incorrect IDs.
- Authentication errors suggest issues with the provided API key or credentials.
- Timeout or connection errors point to network or API availability problems.
To resolve these:
- Verify that the team and user IDs are correct and exist in Vikunja.
- Check that the API key has sufficient permissions.
- Confirm the API URL and network connectivity.