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
The 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 Teams operation, it fetches all teams associated with a specified project. This is useful in scenarios where you need to manage or analyze team memberships within a project, such as automating reporting on team involvement, synchronizing team data with other systems, or managing permissions programmatically.
For example, you might use this node to:
- List all teams collaborating on a particular project to display in a dashboard.
- Automate notifications to all teams involved in a project when updates occur.
- Integrate team membership data into an external HR or project management system.
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 teams will be retrieved. |
Output
The node outputs JSON data representing the list of teams associated with the specified project. Each item in the output corresponds to a team object as returned by the Vikunja API, typically including details such as team name, ID, and possibly other metadata relevant to the team.
If the node supports binary data output (not indicated here), it would represent attachments or files related to the teams, but based on the provided code and properties, the output is purely JSON.
Dependencies
- Requires an active connection to the Vikunja API.
- Needs an API authentication token credential configured in n8n to authorize requests.
- The base URL for the Vikunja API must be set correctly in the credentials.
- The node uses internal helper methods to search and map projects, ensuring that project selection is user-friendly.
Troubleshooting
Common Issues:
- Incorrect or missing API URL or authentication token will cause authorization errors.
- Specifying a non-existent project ID or title will result in empty or error responses.
- Network connectivity issues may prevent the node from reaching the Vikunja API.
Error Messages:
- Unauthorized / 401: Check that the API key or token is valid and has sufficient permissions.
- Not Found / 404: Verify that the project ID or title exists and is accessible.
- Timeouts or Network Errors: Ensure network connectivity and that the API URL is reachable.
Resolving these usually involves verifying credentials, project identifiers, and network settings.
Links and References
- Vikunja Official Website
- Vikunja API Documentation
- n8n Documentation on Creating Custom Nodes