Actions57
- Team Actions
- Webhook Actions
- 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
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 organizations want to programmatically organize users into teams for better project and task collaboration.
Practical examples include:
- Automatically creating teams when onboarding new departments.
- Setting up teams dynamically based on external HR or CRM data.
- Integrating team creation as part of a larger workflow that manages projects and tasks.
Properties
| Name | Meaning |
|---|---|
| Team Name | The name of the team to be created. This is a required field. |
| Description | An optional textual description providing more details about the team. |
Output
The node outputs JSON data representing the newly created team object as returned by the Vikunja API. This typically includes fields such as the team's unique identifier, name, description, and possibly metadata like creation timestamps.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Vikunja API.
- The base URL for the Vikunja API must be configured in the node credentials.
- The node sends requests with
Content-Type: application/jsonand expects JSON responses.
Troubleshooting
- Missing or invalid API credentials: Ensure the API key and base URL are correctly set in the node's credentials.
- Validation errors: If the "Team Name" is missing or empty, the API will reject the request. Always provide a non-empty team name.
- Network issues: Verify network connectivity to the Vikunja API endpoint.
- API errors: Check the response message for details if the API returns an error status; it may indicate permission issues or malformed requests.
Links and References
- Vikunja API Documentation (for detailed API endpoints and payload structures)