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 company.
- 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 uses the base URL configured in the credentials to send requests.
- The node depends on the Vikunja API being accessible and the provided user and project IDs being valid.
Troubleshooting
- Invalid Project or User ID: If the project or user ID does not exist or is incorrect, the API will likely return an error. Verify IDs before running the node.
- Authentication Errors: Ensure the API key credential is correctly set up and has sufficient permissions to modify project memberships.
- Network Issues: Connectivity problems to the Vikunja API endpoint will cause failures; check network access and API availability.
- Permission Denied: The authenticated user may lack rights to add users to the project; verify user roles and permissions in Vikunja.
Common error messages might include HTTP 401 Unauthorized (authentication failure), 404 Not Found (invalid project or user), or 403 Forbidden (insufficient permissions).
Links and References
- Vikunja API Documentation (for detailed API endpoints and payloads)
- n8n Documentation on Creating Custom Nodes