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
The "Add a Team" operation for the Project resource in this node allows you to associate a team with a specific project in Vikunja. This is useful for managing project access and collaboration by granting teams different levels of permissions on projects.
Common scenarios include:
- Adding a new team to a project to enable collaborative work.
- Assigning specific rights (read-only, read & write, admin) to teams based on their role in the project.
- Automating project team management workflows within n8n.
For example, you could use this node to add a marketing team to a product launch project with read & write access, enabling them to update tasks and progress.
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 adding 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 API key credential for authenticating with the Vikunja API.
- Needs the base URL of the Vikunja instance configured in the node credentials.
- Uses Vikunja REST API endpoints to perform operations.
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 list mode to select valid entries.
- Insufficient Permissions: The API key used must have sufficient rights to modify project teams; otherwise, authorization errors may occur.
- Network Issues: Connectivity problems with the Vikunja server will cause request failures. Verify network access and API URL correctness.
- Invalid Rights Value: The "Right" property must be one of the allowed options (0, 1, 2). Providing invalid values may cause errors.