Actions113
- Accounts Actions
- Account Users Actions
- Agent Bots Actions
- Users Actions
- Inbox API Actions
- Contacts API Actions
- Conversations API Actions
- Messages API Actions
- CSAT Survey Page Actions
- Account Agent Bots Actions
- Agents Actions
- Canned Responses Actions
- Canned Response Actions
- Custom Attributes Actions
- Contacts Actions
- Contact Actions
- Automation Rule Actions
- Help Center Actions
- Conversations Actions
- Conversation Assignment Actions
- Conversation Labels Actions
- Inboxes Actions
- Messages Actions
- Integrations Actions
- Teams Actions
- Custom Filters Actions
- Webhooks Actions
- Reports Actions
Overview
This node allows updating a user on the platform by specifying the user's numeric ID and optionally modifying their name, email, password, and custom attributes. It is useful in scenarios where user information needs to be maintained or corrected programmatically, such as syncing user data from another system, automating user profile updates, or managing user accounts in bulk.
Practical examples:
- Automatically update a user's email address when it changes in an external CRM.
- Change a user's password based on a security policy update.
- Add or modify custom attributes for users to enrich their profiles with additional metadata.
Properties
| Name | Meaning |
|---|---|
| Id | The numeric ID of the user on the platform (required to identify which user to update). |
| Name | The new name of the user. |
| The new email address of the user. | |
| Password | The new password for the user. Must contain uppercase, lowercase letters, number, and special character. |
| Custom Attributes | JSON object representing custom attributes to associate with the user (key-value pairs). |
Output
The node outputs JSON data representing the updated user object returned by the platform's API. This typically includes the user's current details after the update operation, such as id, name, email, and any custom attributes.
If the platform supports binary data related to the user (e.g., profile pictures), this node does not explicitly handle binary output.
Dependencies
- Requires an API key credential to authenticate requests to the platform.
- The base URL for the API must be configured in the node credentials.
- Uses the ChatWoot API as defined in the bundled OpenAPI specification.
Troubleshooting
- Invalid User ID: If the provided user ID does not exist, the API will likely return a "not found" error. Verify the ID before running the node.
- Password Validation Errors: Passwords must meet complexity requirements (uppercase, lowercase, number, special character). Failure to comply will cause the API to reject the update.
- Malformed Custom Attributes: The
custom_attributesfield expects valid JSON. Invalid JSON syntax will cause parsing errors. - Authentication Failures: Ensure the API key credential is correctly set up and has sufficient permissions to update users.
- Network Issues: Check connectivity and base URL configuration if requests fail to reach the API.
Links and References
- ChatWoot API Documentation (for detailed API usage and user update endpoint)
- JSON Syntax Guide (for formatting custom attributes)