Actions115
- Course Actions
- Bundle Actions
- Course Grade Actions
- Course Grade Detail Actions
- Course Teacher Actions
- Email Actions
- Email Campaign Actions
- Email Campaign Course Actions
- Email Campaign Excluded Course Actions
- Email Campaign Excluded List Actions
- Enroll Actions
- Email Campaign Excluded Plan Actions
- Email Campaign List Actions
- Email Campaign Plan Actions
- Email List Actions
- MindzPay Account Actions
- MindzPay Invoice Actions
- MindzPay Payment Actions
- MindzPay Subscription Actions
- Subscription Actions
- Team Actions
- User Actions
Overview
The "Team Update" operation in this node allows updating the permissions and membership status of a user within a team. This is useful for managing user roles and access rights dynamically, such as granting or revoking admin privileges, teacher roles, or access to specific features like courses, marketing, or statistics.
Practical examples include:
- Promoting a team member to an admin role.
- Granting a user permission to manage courses or marketing campaigns.
- Removing a user's team membership or adjusting their access levels without deleting the user.
Properties
| Name | Meaning |
|---|---|
| User ID | The unique identifier of the user whose team permissions are being updated. |
| Admin Permission | Whether the user has administrative permissions within the team (true/false). |
| Teacher Permission | Whether the user has teacher permissions within the team (true/false). |
| Team Permission | Whether the user is considered part of the team (true/false). |
| Courses Permission | Whether the user has permissions related to courses (true/false). |
| GuruPay Permission | Whether the user has permissions related to GuruPay features (true/false). |
| Statistics Permission | Whether the user has access to statistics features (true/false). |
| Marketing Permission | Whether the user has marketing-related permissions (true/false). |
| Editor Permission | Whether the user has editor permissions (true/false). |
Output
The output JSON structure typically contains the updated user team membership and permissions data after the update operation completes successfully. It reflects the current state of the user's roles and access rights within the team.
If the node supports binary data output, it would generally represent any files or attachments related to the team or user updates, but based on the provided code and properties, this node primarily outputs JSON data representing the updated team user information.
Dependencies
- Requires an API key credential for authenticating with the Mindz API.
- The node depends on the Mindz API service to perform the update operations on team user permissions.
- Proper configuration of the OAuth2 API credentials in n8n is necessary to authorize requests.
Troubleshooting
Common issues:
- Invalid or missing User ID: The update will fail if the specified user does not exist or the ID is incorrect.
- Insufficient permissions: The API key used must have adequate rights to modify team memberships.
- Network or API errors: Connectivity issues or API downtime can cause failures.
Error messages:
- "User not found": Verify the User ID is correct and exists in the system.
- "Unauthorized": Check that the API credentials are valid and have the required scopes.
- "Invalid parameters": Ensure all required fields are provided and correctly formatted.
Resolving these usually involves verifying input values, checking API credentials, and ensuring network connectivity.
Links and References
- Mindz API Documentation (general reference for API endpoints and permissions)
- n8n OAuth2 Credential Setup Guide (for configuring API authentication)