Actions57
- Team Actions
- Webhook Actions
- 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
Overview
This node integrates with the Vikunja API to retrieve data related to projects, tasks, labels, teams, and webhooks. Specifically, for the Project resource with 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 audit project membership, synchronize user lists with other systems, or display project collaborators within workflows.
Practical examples include:
- Automatically listing all users of a project to send notifications.
- Syncing project user lists with external team management tools.
- Generating reports on project participation.
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, username, email, and roles within the project (based on typical API user representations). The exact structure depends on the Vikunja API response but generally provides comprehensive user information relevant to the project.
No binary data output is involved in this operation.
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 access to the Vikunja API endpoint is necessary.
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 "Authentication failed": Check API key validity and permissions.
- "Project not found": Verify the project ID or selection mode.
- Timeouts or connection errors: Inspect network settings and API availability.
Resolving these usually involves verifying credentials, project identifiers, and network configurations.