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 manage teams and their users. Specifically, the "Toggle a User's Admin Status in a Team" operation allows you to change whether a user has administrative privileges within a specified team. This is useful for managing team roles dynamically, such as promoting or demoting users based on project needs or organizational changes.
Practical examples include:
- Automatically granting admin rights to a user when they join a team.
- Revoking admin status from a user who no longer requires elevated permissions.
- Managing team roles programmatically as part of onboarding or offboarding workflows.
Properties
| Name | Meaning |
|---|---|
| Team Name or ID | The target team to operate on. You can select a team from a searchable list or specify its ID directly. |
Note: The property supports two modes:
- From List: Select a team by searching through existing teams.
- ID: Provide the unique identifier of the team manually.
Output
The node outputs JSON data representing the result of the toggle operation on the user's admin status within the specified team. This typically includes confirmation of the updated user role or the current state of the team membership after the change.
If the node supports binary data output (not evident from the provided code), it would relate to any files or attachments associated with the team or user, but this is not indicated here.
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 depends on internal helper functions for searching teams (
searchTeams) and making API requests.
Troubleshooting
Common Issues:
- Providing an invalid or non-existent team ID will cause the operation to fail.
- Insufficient permissions with the API key may prevent toggling admin status.
- Network connectivity issues can interrupt communication with the Vikunja API.
Error Messages:
- Errors related to "team not found" indicate that the specified team does not exist or the ID is incorrect.
- Authentication errors suggest problems with the API key or credential configuration.
Resolutions:
- Verify the team ID or select the team from the list to ensure correctness.
- Check that the API key has sufficient permissions to modify team user roles.
- Ensure network access to the Vikunja API endpoint is available.
Links and References
- Vikunja API Documentation – Official API reference for understanding endpoints and payloads.
- n8n Documentation – For general guidance on using custom nodes and credentials.