Actions37
- Issue Actions
- Lead Actions
- Opportunity Actions
- Account Actions
- Attendance Actions
- Personal Contact Actions
- Time Entry Actions
- User Actions
Overview
This node integrates with Easy Redmine to update user information. It allows modifying various fields of a user entity such as email, first name, last name, login, phone number, and custom fields. This operation is useful in scenarios where user details need to be kept current, for example:
- Synchronizing user data from an external system.
- Correcting or updating user contact information.
- Adding or modifying custom attributes related to users.
Practical example: Automatically update a user's phone number and email address when changes are detected in your CRM system.
Properties
| Name | Meaning |
|---|---|
| User ID | The unique identifier of the user to update. |
| Update Fields | A collection of fields to update on the user: |
| The user's email address. | |
| - First Name | The user's first name. |
| - Last Name | The user's last name. |
| - Login | The user's login name. |
| - Phone | The user's phone number. |
| - Custom Fields | Multiple custom fields can be specified, each with an ID and a value to set. |
Output
The node outputs JSON data representing the updated user entity as returned by the Easy Redmine API. The structure typically includes the updated user properties reflecting the changes made.
If the node supports binary data output (not indicated here), it would represent associated files or attachments related to the user, but this node focuses on JSON user data only.
Dependencies
- Requires an API key credential for Easy Redmine with appropriate permissions to update user entities.
- The node expects the base URL of the Easy Redmine instance to be configured in the credentials.
- No additional external dependencies beyond the Easy Redmine API.
Troubleshooting
Common issues:
- Invalid or missing User ID will cause the update to fail.
- Insufficient permissions on the API key may result in authorization errors.
- Providing invalid field values (e.g., malformed email) might cause validation errors from the API.
Error messages:
- Errors returned from the API are captured and presented; they often include detailed messages about what went wrong.
- If the node is set to continue on failure, errors for individual items will be included in the output JSON under an
errorproperty.
Resolution tips:
- Verify that the User ID exists and is correct.
- Check API credentials and permissions.
- Validate input field formats before running the node.