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 - Create" operation in this node allows you to add a user to a team within the Mindz platform, specifying various permission levels for that user. This is useful for managing team membership and access control programmatically, such as automating onboarding processes or synchronizing team roles from other systems.
Practical examples include:
- Adding a new employee to a project team with specific permissions.
- Automating role assignments when users join or change teams.
- Managing access rights for different team members based on their responsibilities.
Properties
| Name | Meaning |
|---|---|
| User ID | The unique identifier of the user to be added to the team. |
| Admin Permission | Whether the user has administrative permissions within the team (true/false). |
| Teacher Permission | Whether the user has teacher-level 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-related features (true/false). |
| Marketing Permission | Whether the user has marketing-related permissions (true/false). |
| Editor Permission | Whether the user has editor-level permissions (true/false). |
Output
The node outputs JSON data representing the result of the create team operation. This typically includes confirmation of the user's addition to the team along with the assigned permissions and any relevant metadata returned by the Mindz API.
If the operation supports binary data output (not indicated here), it would represent files or attachments related to the team or user, but this is not applicable for this operation.
Dependencies
- Requires an active connection to the Mindz API via an OAuth2-based authentication credential.
- The node depends on the Mindz API being accessible and properly configured with necessary permissions to manage team memberships.
- No additional external services are required beyond the Mindz API.
Troubleshooting
Common issues:
- Invalid or missing User ID: Ensure the User ID provided exists and is correctly formatted.
- Insufficient API permissions: Verify that the API credentials have rights to modify team memberships.
- Network or connectivity errors: Check internet connection and Mindz API availability.
Error messages:
- "User not found": The specified User ID does not exist; verify the ID.
- "Permission denied": The API key lacks sufficient privileges; update credentials or permissions.
- "Invalid input": One or more properties have incorrect types or values; review input parameters.
Resolving these usually involves verifying input data, checking API credentials, and ensuring the Mindz service is operational.
Links and References
- Mindz API Documentation (hypothetical link)
- OAuth2 Authentication setup guides for Mindz API
- n8n documentation on creating custom nodes and using OAuth2 credentials