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 Vikunja task management system. Specifically, the "Update Team" operation allows users to modify an existing team's details such as its name and description. This is useful in scenarios where team information needs to be kept current, for example, when a team's purpose changes or additional context needs to be added.
Practical examples include:
- Renaming a team to reflect a new project focus.
- Adding or updating a descriptive summary to clarify the team's role.
- Keeping team metadata consistent across multiple tools by automating updates via n8n workflows.
Properties
| Name | Meaning |
|---|---|
| Team Name or ID | Select the team to update either by choosing from a searchable list of existing teams or by specifying the team's unique ID directly. |
| Team Name | The new name to assign to the team. This is a required field when updating a team. |
| Description | A textual description providing additional information about the team. Optional but recommended for clarity. |
Output
The node outputs JSON data representing the updated team object as returned by the Vikunja API. This typically includes fields such as the team's ID, updated name, description, and possibly other metadata managed by Vikunja.
If the node supports binary data output (not indicated here), it would generally relate to attachments or files associated with the team, but this operation focuses on JSON data only.
Dependencies
- Requires an active connection to the Vikunja API.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The base URL for the Vikunja instance must be set correctly in the credential configuration.
Troubleshooting
- Invalid Team ID or Name: If the specified team does not exist, the API will return an error. Ensure the team identifier is correct or select from the provided list.
- Missing Required Fields: The "Team Name" property is mandatory for updates; omitting it will cause validation errors.
- Authentication Errors: Verify that the API key or token is valid and has sufficient permissions to update teams.
- Network Issues: Check connectivity to the Vikunja server and ensure the base URL is correctly configured without trailing slashes.
Links and References
- Vikunja API Documentation – Official API reference for detailed endpoint information.
- n8n Documentation – Guidance on setting up credentials and using custom nodes.