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 node interacts with the Mindz API to perform various operations on different resources. Specifically, for the User resource with the Get operation, it retrieves detailed information about a specific user identified by their User ID. This is useful in scenarios where you need to fetch user profile data, verify user details, or integrate user information into workflows such as CRM updates, reporting, or personalized communications.
Practical example:
You might use this node to get a user's full profile before sending them a customized email campaign or to synchronize user data between Mindz and another system.
Properties
| Name | Meaning |
|---|---|
| User ID | The unique identifier of the user whose details you want to retrieve. This is a required string input. |
Output
The output contains a JSON object representing the user's data as returned by the Mindz API. This typically includes fields such as user name, email, status, roles, and other profile-related information depending on the API's response structure.
If the node supports binary data (not indicated here), it would be summarized as user-related files or attachments, but for the Get operation on User, the output is purely JSON data.
Dependencies
- Requires an active connection to the Mindz API using OAuth2 authentication.
- The node depends on valid credentials configured in n8n to authenticate API requests.
- No additional external services are needed beyond the Mindz API.
Troubleshooting
Common issues:
- Invalid or missing User ID will cause the API call to fail.
- Expired or incorrect API credentials will result in authentication errors.
- Network connectivity problems can prevent successful API calls.
Error messages:
- "User not found" — Verify that the User ID is correct and exists in the Mindz system.
- "Authentication failed" — Check that the API credentials are correctly set up and have not expired.
- "Request timeout" — Ensure stable internet connection and retry.
Resolving these usually involves verifying input parameters, refreshing credentials, and checking network status.
Links and References
- Mindz API Documentation (example placeholder link)
- n8n OAuth2 Credential Setup Guide
- n8n Node Development Documentation