Actions116
- 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
- Email Campaign Excluded Plan Actions
- Email Campaign List Actions
- Email Campaign Plan Actions
- Email List Actions
- Enroll Actions
- MindzPay Account Actions
- MindzPay Invoice Actions
- MindzPay Payment Actions
- MindzPay Subscription Actions
- Subscription Actions
- Team Actions
- User Actions
Overview
The "Team - Partial Update" operation in this node allows updating specific permission settings for a user within a team. Instead of replacing the entire user record, it modifies only selected permissions such as admin rights, teacher status, and access to various modules like courses, marketing, or integrations.
This operation is useful in scenarios where you want to adjust a user's role or capabilities incrementally without affecting other user data. For example, you might grant a user marketing permissions while leaving their other permissions unchanged, or revoke editor access temporarily.
Practical examples:
- Granting a user admin privileges to manage team settings.
- Enabling teacher permissions for a user who just joined the teaching staff.
- Updating financial-related permissions like GuruPay access for billing purposes.
Properties
| Name | Meaning |
|---|---|
| User ID | The unique identifier of the user whose permissions are being updated. |
| Admin Permission | Whether the user has administrative permissions (true/false). |
| Teacher Permission | Whether the user has teacher permissions (true/false). |
| Courses Permission | Whether the user has access to course-related features (true/false). |
| GuruPay Permission | Whether the user has permissions related to GuruPay payment system (true/false). |
| Statistics Permission | Whether the user can access statistics and analytics features (true/false). |
| Marketing Permission | Whether the user has marketing-related permissions (true/false). |
| Editor Permission | Whether the user has content editing permissions (true/false). |
| Integration Permission | Whether the user has permissions to manage integrations with other systems (true/false). |
Output
The output JSON contains the result of the partial update operation on the specified user’s team permissions. It typically includes confirmation of the updated fields and possibly the updated user permission object reflecting the new state.
If the node supports binary data output, it would represent any files or attachments returned by the API, but for this operation, the output is expected to be purely JSON-based permission data.
Dependencies
- Requires an API authentication token configured in n8n credentials to interact with the Mindz API.
- The node depends on the Mindz platform's API endpoints for managing team user permissions.
- Proper network connectivity and valid user IDs are necessary for successful updates.
Troubleshooting
- Invalid User ID: If the provided User ID does not exist or is malformed, the API will likely return an error indicating the user was not found. Verify the User ID before running the node.
- Insufficient Permissions: The API key or token used must have sufficient rights to modify team permissions; otherwise, authorization errors may occur.
- Partial Update Failures: If none of the permission fields are set or all are false, the API might reject the request as no changes are specified.
- API Rate Limits: Frequent updates might hit rate limits imposed by the Mindz API, causing temporary failures.
To resolve these issues:
- Double-check input parameters.
- Ensure the API credential has appropriate scopes.
- Add error handling in your workflow to catch and log API errors.
- Space out requests if hitting rate limits.
Links and References
- Mindz API Documentation (hypothetical link)
- n8n documentation on Creating Custom Nodes
- General REST API best practices for partial updates (PATCH method)