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 information 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 displaying team lists in dashboards, automating team-based notifications, or syncing team data with other systems.
Practical examples:
- Automatically listing all teams involved in a project to assign tasks accordingly.
- Generating reports on team participation across multiple projects.
- Syncing project team data with external collaboration tools.
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 determines which project's teams will be retrieved. |
Output
The node outputs JSON data containing the list of teams associated with the specified project. Each item in the output typically represents a team object with details such as team name, ID, and possibly other metadata provided by the Vikunja API.
If the node supports binary data output (not indicated here), it would represent attachments or files related to the teams, but this operation primarily returns structured JSON data about teams.
Dependencies
- Requires an API key credential for authenticating with the Vikunja API.
- Needs the base URL of the Vikunja instance configured in the credentials.
- Uses the
/projects/{projectId}/teamsendpoint internally to fetch teams (inferred from context).
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 or connectivity problems: Confirm the Vikunja API URL is reachable from n8n.
Error messages:
- Unauthorized or 401 errors indicate invalid API credentials.
- 404 errors may mean the project ID does not exist or the endpoint is incorrect.
- Timeout or network errors suggest connectivity issues.
Resolving these usually involves checking credentials, verifying project IDs, and ensuring network access.
Links and References
- Vikunja API Documentation – Official API reference for endpoints and authentication.
- n8n Documentation – For general guidance on using credentials and configuring nodes.