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.
Practical examples include:
- Automatically listing all teams assigned to a project to display in a dashboard.
- Syncing project team information with an external HR or collaboration tool.
- Triggering workflows based on team membership changes within a project.
Properties
| Name | Meaning |
|---|---|
| Project Title or ID | The target 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 team details such as team name, ID, and possibly other metadata.
If the node supports binary data output (not indicated here), it would represent any file or media content related to the teams, but this operation primarily deals with JSON data.
Dependencies
- Requires an active connection to the Vikunja API.
- Needs an API authentication token or key configured in the node credentials to authorize requests.
- The base URL for the Vikunja API must be set correctly in the node's credential configuration.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication errors.
- Incorrect project ID or selecting a non-existent project will result in empty results or errors.
- Network connectivity problems may prevent the node from reaching the Vikunja API.
Error messages:
- Authentication failures: Check that the API key/token is valid and has sufficient permissions.
- "Project not found" or similar: Verify the project ID or selection is correct.
- Timeout or network errors: Ensure the API URL is reachable and there are no firewall restrictions.
Links and References
- Vikunja API Documentation — Official API reference for understanding available endpoints and data structures.
- n8n Documentation — For general guidance on using n8n nodes and configuring credentials.