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
This node integrates with the Vikunja API to retrieve data related to projects, tasks, labels, teams, and webhooks. Specifically, for the "Project" resource and the "Get All Users" operation, it fetches all users associated with a specified project. This is useful in scenarios where you need to manage or analyze team members involved in a project, such as generating reports on user participation, assigning tasks based on user availability, or syncing project user lists with other systems.
Practical examples:
- Automatically listing all users of a project to send notifications or updates.
- Integrating with HR or communication tools to reflect current project team members.
- Auditing project access by retrieving all users linked to a project.
Properties
| Name | Meaning |
|---|---|
| Project Title or ID | The project to operate on. You can select a project from a searchable list or specify its ID directly. This identifies which project's users will be retrieved. |
Output
The node outputs JSON data containing the list of users associated with the specified project. Each user object typically includes details such as user ID, name, email, and possibly roles or permissions within the project context.
If the node supports binary data output (not indicated here), it would represent files or attachments related to the users or project, but this operation primarily returns structured JSON user data.
Dependencies
- Requires an API key credential for authenticating with the Vikunja API.
- Needs the base URL of the Vikunja instance configured in the credentials.
- The node uses HTTP requests to communicate with the Vikunja API endpoints.
Troubleshooting
Common issues:
- Invalid or missing project ID: Ensure the project exists and the ID or selection is correct.
- Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- Network connectivity problems: Confirm that the Vikunja API URL is reachable from the n8n environment.
Error messages:
- Unauthorized or 401 errors indicate invalid credentials; reconfigure the API key.
- 404 errors may mean the project ID does not exist or the user lacks access.
- Timeout or connection errors suggest network issues or incorrect API URL.
Resolving these usually involves checking credentials, verifying project identifiers, and ensuring network accessibility.