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 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 participates in a project.
- Cleaning up project permissions by detaching obsolete teams.
- Automating project team management workflows based on organizational changes.
Properties
| Name | Meaning |
|---|---|
| Project Title or ID | The target project to operate on. Can be selected from a searchable list of projects or specified directly by its ID. |
| Team ID | The team to remove from the project. Can be selected from a searchable list of teams or specified directly by its ID. |
Output
The node outputs JSON data representing the result of the removal operation. Typically, this will confirm whether the team was successfully removed from the project. The exact structure depends on the Vikunja API response but generally includes status information and possibly the updated project or team details.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Vikunja API.
- Needs an API authentication token configured in n8n credentials for authorization.
- The base URL for the Vikunja API must be set correctly in the node's credential configuration.
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 token used must have rights to modify project teams.
- Network or API endpoint errors: Verify the API URL and network connectivity.
Error Messages:
- "Project not found": Check if the project ID or selection is correct.
- "Team not found": Verify the team ID or selection.
- "Unauthorized" or "Forbidden": Confirm API credentials have necessary permissions.
- "Failed to remove team": Could indicate server-side issues or invalid request format; review input parameters.
Resolving these typically involves validating inputs, checking API credentials, and ensuring the Vikunja service is operational.