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 "Add a Team" operation for the Project resource in this Vikunja node allows you to associate a team with a specific project and assign access rights to that team. This is useful for managing collaborative workspaces where different teams need varying levels of access to projects. For example, you might add a marketing team to a product launch project with read-only access, while giving the development team admin rights to manage tasks and settings.
Common scenarios include:
- Granting a new team access to an existing project.
- Adjusting team permissions on a project by adding them with specific rights.
- Automating team-project associations as part of onboarding or project setup workflows.
Properties
| Name | Meaning |
|---|---|
| Project Title or ID | The target project to which the team will be added. You can select from a list of projects or specify the project ID directly. |
| Team ID | The team to add to the project. Select from a searchable list of teams or provide the team ID. |
| Right | The permission level granted to the team on the project. Options are: Read Only, Read & Write, Admin. |
Output
The node outputs JSON data representing the result of the API call to add the team to the project. This typically includes confirmation details such as the project ID, team ID, and assigned rights. The exact structure depends on the Vikunja API response but generally confirms successful association.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to a Vikunja instance via an API URL and an API authentication token (provided through n8n credentials).
- Uses Vikunja's REST API endpoints for projects and teams.
- The node relies on internal helper methods to search and map projects and teams for selection lists.
Troubleshooting
- Invalid Project or Team ID: If the provided project or team ID does not exist, the API will return an error. Ensure IDs are correct or use the searchable list mode to pick valid entries.
- Insufficient Permissions: The API user must have rights to modify project team assignments. Lack of permissions will cause authorization errors.
- Network Issues: Connectivity problems with the Vikunja server will prevent the operation from completing.
- Incorrect Rights Value: The "Right" property must be one of the predefined options (0, 1, 2). Providing invalid values may cause request failures.
To resolve errors, verify credentials, check project and team existence, and confirm the API user's permissions.