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 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 team to operate on. You can select a team from a searchable list or specify its ID directly. |
The property supports two modes:
- From List: Search and select a team by name.
- ID: Provide the unique identifier of the team.
Output
The node outputs JSON data representing the team object retrieved from the Vikunja API. This typically includes fields such as the team's ID, name, description, and other metadata defined by the API.
No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating with the Vikunja API.
- The base URL for the API must be configured in the node credentials.
- The node depends on the Vikunja API being accessible and responsive.
Troubleshooting
Common Issues:
- Invalid or missing API credentials will cause authentication failures.
- Providing an incorrect team ID or selecting a non-existent team from the list will result in errors or empty responses.
- Network connectivity issues may prevent the node from reaching the Vikunja API.
Error Messages:
- Authentication errors indicate problems with the API key or permissions.
- "Team not found" or similar messages suggest the specified team does not exist.
Resolutions:
- Verify and update the API key credential.
- Double-check the team ID or select the correct team from the list.
- Ensure network access to the Vikunja API endpoint.