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 associated teams. Specifically, the "Remove a Team From a Project" operation allows users to disassociate a team from a given project. This is useful in scenarios where team membership changes or when reorganizing project access control.
Practical examples include:
- Removing a team that no longer works on a specific project.
- Managing project permissions dynamically by adding or removing teams as needed.
- Automating cleanup of project-team associations during organizational changes.
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. |
| Team ID | The team to remove from the project. Select from a searchable list of teams or provide the team's ID. |
Output
The node outputs JSON data representing the result of the API call to remove the team from the project. Typically, this will confirm success or provide details about the updated project state. There is no indication of binary data output for this operation.
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 Vikunja REST API endpoints related to projects and teams.
Troubleshooting
Common issues:
- Invalid project or team ID: Ensure the IDs provided exist and are accessible with the current API credentials.
- Insufficient permissions: The API key used must have rights to modify project-team associations.
- Network or API endpoint errors: Verify the base URL and network connectivity to the Vikunja server.
Error messages:
- "Project not found" or "Team not found": Check that the specified IDs are correct.
- "Unauthorized" or "Forbidden": Confirm the API key has appropriate permissions.
- Timeout or connection errors: Check network settings and Vikunja server availability.