Mindz icon

Mindz

Interact with Mindz API
Join our community

Actions116

Overview

The node provides an interface to update user information in the Mindz system via its API. It allows modifying various user attributes such as email, name, username, suspension status, gender, contact details, birth date, personal or corporate identification, and address information.

This node is beneficial in scenarios where user data needs to be kept current or corrected automatically, for example:

  • Synchronizing user profile updates from another system.
  • Automating user account management workflows.
  • Suspending or reactivating users programmatically based on external triggers.

Practical example: Automatically updating a user's email and phone number when they submit a form on a website, ensuring the Mindz platform always has the latest contact info.

Properties

Name Meaning
User ID The unique identifier of the user to update (required).
Email The user's email address.
First Name The user's first name.
Last Name The user's last name.
Username The user's username.
Suspended Whether the user is suspended. Options: Keep Current Value, Yes (suspended), No (not suspended).
Gender The user's gender. Options: Male, Female.
Phone The user's phone number.
Birth Date The user's birth date.
Bio A short biography or description about the user.
Person Type The type of person. Options: Pessoa Física (individual), Pessoa Jurídica (corporate entity).
CPF/CNPJ Brazilian individual or company tax identification number.
Corporate Name The corporate name if applicable.
Country The country of the user.
Zip Code The postal code of the user's address.
State The state or province of the user's address.
City The city of the user's address.
District The district or neighborhood of the user's address.
Street The street name of the user's address.
House Number The house or building number of the user's address.
Complement Additional address information (e.g., apartment, suite).

Output

The node outputs JSON data representing the updated user object returned by the Mindz API after the update operation. This typically includes all user fields with their new values reflecting the changes made.

If the API supports it, the output may also include metadata about the update operation such as timestamps or status codes.

No binary data output is indicated for this operation.

Dependencies

  • Requires an active connection to the Mindz API using an OAuth2-based API key credential configured in n8n.
  • The node depends on the Mindz API being accessible and the provided credentials having permission to update user data.

Troubleshooting

  • Common issues:

    • Invalid or missing User ID will cause the update to fail.
    • Providing invalid field formats (e.g., malformed email or date) may result in API errors.
    • Insufficient permissions on the API key can lead to authorization errors.
    • Network connectivity problems can cause request timeouts or failures.

  • Error messages:

    • "User not found" indicates the specified User ID does not exist.
    • "Unauthorized" or "Forbidden" suggests credential or permission issues.
    • Validation errors will specify which input fields are incorrect or missing.

  • Resolutions:

    • Verify the User ID is correct and exists in the Mindz system.
    • Check that all required fields are properly formatted.
    • Ensure the API credentials have update permissions.
    • Confirm network connectivity and API endpoint availability.

Links and References

  • Mindz API documentation (general reference for user management endpoints)
  • n8n OAuth2 credential setup guide
  • Best practices for managing user data in Mindz

Discussion