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
The node integrates with the Vikunja API to manage projects and their associated teams. Specifically, the "Add a Team" operation under the "Project" resource allows users to add a team to a specified project with defined access rights. This is useful in collaborative environments where project access needs to be controlled and shared among different teams.
Practical examples include:
- Adding a marketing team to a product launch project with read-only access.
- Granting an engineering team admin rights on a development project to allow full control.
- Sharing a project with a support team with read & write permissions for issue tracking.
Properties
| Name | Meaning |
|---|---|
| Project Title or ID | The target project to which the team will be added. Can be selected from a searchable list or specified by ID. |
| Team ID | The team to add to the project. Can be selected from a searchable list or specified by ID. |
| Right | The level of access granted to the team on the project. Options: Read Only (0), Read & Write (1), Admin (2). |
Output
The node outputs JSON data representing the result of adding the team to the project. This typically includes confirmation details such as the project ID, team ID, and the assigned access rights. There is no indication that binary data is output by this operation.
Dependencies
- Requires an active connection to the Vikunja API via an API key credential.
- The base URL for the API must be configured in the node credentials.
- The node uses internal helper methods to search and map projects and teams for selection lists.
Troubleshooting
Common Issues:
- Invalid project or team ID: Ensure the IDs exist and are accessible with the provided API credentials.
- Insufficient permissions: The API key used must have rights to modify project team memberships.
- Network or API endpoint errors: Verify the API URL and network connectivity.
Error Messages:
- "Project not found": Check that the project ID or selected project exists.
- "Team not found": Verify the team ID or selected team is valid.
- "Unauthorized": Confirm the API key has sufficient permissions.
Resolving these usually involves verifying input values, checking API credentials, and ensuring the Vikunja server is reachable.