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 users. Specifically, the "Add a User" operation under the "Project" resource allows you to add an existing user to a specified project by providing the project's identifier and the user's ID. This is useful in scenarios where you want to programmatically manage team membership within projects, such as automating onboarding workflows or synchronizing user access across systems.
Practical examples:
- Automatically adding a new employee to relevant projects when they join a team.
- Syncing user assignments from an external HR system into Vikunja projects.
- Managing project collaborators dynamically based on external triggers.
Properties
| Name | Meaning |
|---|---|
| Project Title or ID | The target project to which the user will be added. You can select a project from a searchable list or specify its ID directly. |
| User ID | The numeric identifier of the user to add to the project. |
Output
The node outputs JSON data representing the result of the API call to add the user to the project. This typically includes confirmation details about the updated project-user association or the user entity added. There is no indication that binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating with the Vikunja API.
- The node expects the base URL of the Vikunja instance to be configured in the credentials.
- Network connectivity to the Vikunja server is necessary.
Troubleshooting
Common issues:
- Providing an invalid or non-existent project ID or user ID will likely cause the API call to fail.
- Insufficient permissions for the API key may prevent adding users to projects.
- Network errors or incorrect base URL configuration can cause connection failures.
Error messages:
- Errors related to "user not found" or "project not found" indicate invalid identifiers.
- Authentication errors suggest problems with the API key or credential setup.
- Timeout or network errors require checking connectivity and endpoint correctness.
To resolve these, verify the IDs used, ensure the API key has appropriate permissions, and confirm the Vikunja API URL is correct.