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
This node integrates with the Vikunja API to retrieve information about teams. Specifically, the "Get" operation under the "Team" resource fetches details of a single team by its name or ID. This is useful in scenarios where you need to access team metadata for project management, reporting, or automation workflows that involve team-specific data.
For example, you might use this node to:
- Retrieve a team's details before assigning tasks.
- Fetch team information to display in dashboards.
- Automate notifications or updates based on team attributes.
Properties
| Name | Meaning |
|---|---|
| Team Name or ID | The identifier of the team to operate on. You can select a team from a searchable list or specify the team ID directly. |
The property supports two modes:
- From List: Select a team interactively from a searchable dropdown.
- ID: Provide the exact team ID as a string.
Output
The node outputs JSON data representing the requested team's details as returned by the Vikunja API. This typically includes fields such as the team's ID, name, description, and other metadata relevant to the team entity.
No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating requests to the Vikunja API.
- The base URL for the API must be configured in the node's credentials.
- The node depends on the Vikunja API being accessible and responsive.
Troubleshooting
- Invalid Team ID or Not Found: If the specified team ID does not exist, the API will likely return an error or empty response. Verify the team ID or select from the list mode.
- Authentication Errors: Ensure the API key credential is correctly set up and has sufficient permissions.
- Network Issues: Confirm that the API URL is correct and reachable from the n8n environment.
- Empty List in Dropdown: If no teams appear in the selection list, check that the API user has access to teams and that there are existing teams in Vikunja.