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 - Create" operation in this node allows you to add a user to a team with specific permissions. This is useful for managing team members' roles and access rights within an organization or project managed through the Mindz platform. For example, you can create a new team member entry specifying whether they have admin rights, teaching privileges, marketing access, and other permission types.
Practical scenarios include:
- Adding a new instructor to a course team with teacher permissions.
- Granting marketing team members access to relevant statistics and marketing tools.
- Assigning integration permissions to users responsible for connecting external services.
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 (true/false). |
| Teacher Permission | Whether the user has teacher permissions (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 (true/false). |
| Marketing Permission | Whether the user has marketing-related permissions (true/false). |
| Editor Permission | Whether the user has editor permissions (true/false). |
| Integration Permission | Whether the user has permissions to manage integrations (true/false). |
Output
The output JSON contains the result of the creation operation, typically including details about the newly created team membership such as the user ID, assigned permissions, and possibly metadata confirming the successful addition.
If the node supports binary data output (not indicated here), it would represent any files or attachments related to the team creation process, but this operation primarily deals with JSON data.
Dependencies
- Requires an API authentication token credential configured in n8n to connect to the Mindz API.
- The node depends on the Mindz platform's API endpoints for team management.
- No additional external services are explicitly required beyond the Mindz API.
Troubleshooting
Common Issues:
- Missing or invalid User ID: Ensure the User ID provided exists and is correctly formatted.
- Insufficient permissions: The API key used must have rights to modify team memberships.
- Network or API errors: Check connectivity and API status.
Error Messages:
- "User not found": Verify the User ID is correct.
- "Permission denied": Confirm that the API credentials have adequate permissions.
- "Invalid input": Check that all required fields are provided and valid.
Resolving these usually involves verifying input parameters, ensuring proper API credentials, and checking network connectivity.
Links and References
- Mindz API Documentation (general reference for API endpoints and permissions)
- n8n Documentation on creating custom nodes and using credentials
- Best practices for managing team permissions in collaborative platforms