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 manage teams within the task management system. Specifically, the "Team - Create" operation allows users to create a new team by specifying its name and an optional description. This is useful in scenarios where you want to programmatically organize users or projects into distinct groups for better collaboration and access control.
Practical examples include:
- Automatically creating a new team when onboarding a new department.
- Setting up teams dynamically based on project requirements.
- Integrating with other systems to sync team structures.
Properties
| Name | Meaning |
|---|---|
| Team Name | The name of the team to be created (required). |
| Description | A textual description providing more details about the team (optional). |
Output
The node outputs JSON data representing the newly created team as returned by the Vikunja API. This typically includes fields such as the team's unique identifier, name, description, creation timestamps, and possibly other metadata related to the team entity.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Vikunja API.
- The base URL for the Vikunja API must be configured in the node credentials.
- The node sends HTTP requests with JSON payloads and expects JSON responses.
Troubleshooting
- Missing Required Fields: If "Team Name" is not provided, the node will likely throw a validation error. Ensure this field is filled.
- Authentication Errors: Invalid or missing API credentials will cause authentication failures. Verify that the API key and base URL are correctly set.
- API Endpoint Issues: Network problems or incorrect API URLs can lead to request failures. Confirm the API URL does not have trailing slashes and is reachable.
- Permission Denied: The API user may lack permissions to create teams. Check user roles and permissions in Vikunja.
- Unexpected API Responses: If the API changes or returns errors, inspect the response message for clues and update the node configuration accordingly.