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 and their users. Specifically, for the "Team" resource and the operation "Toggle a User's Admin Status in a Team," it allows you to change whether a user has administrative privileges within a specified team. This is useful in scenarios where team roles need to be dynamically adjusted, such as promoting a member to admin to grant them more control or demoting an admin to a regular user.
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 on which to operate. You can select a team from a searchable list or specify its ID directly. |
Note: Although only the "Team Name or ID" property is provided here, typically toggling a user's admin status would also require specifying the user and the desired admin state; however, these are not included in the provided properties snippet.
Output
The node outputs JSON data representing the result of the toggle operation on the user's admin status within the team. This typically includes confirmation of the updated user role or the updated team membership details.
If the node supports binary data output (not indicated in the provided code), it would represent any files or attachments related to the team or user, but this is unlikely for this operation.
Dependencies
- Requires an API key credential for authenticating with the Vikunja API.
- Needs the base URL of the Vikunja instance configured in the credentials.
- Uses HTTP requests to interact with the Vikunja REST API endpoints related to teams.
Troubleshooting
Common Issues:
- Invalid or missing team ID/name: Ensure the team exists and the identifier is correct.
- Insufficient permissions: The API key used must have rights to modify team memberships.
- Network or connectivity problems: Verify that the Vikunja API URL is reachable.
Error Messages:
- "Team not found": Check that the team ID or name is correct.
- "Unauthorized" or "Forbidden": Confirm that the API key has appropriate permissions.
- "Invalid input": Make sure all required parameters, including user identification and admin status, are correctly provided.