Actions15
Overview
This node integrates with the Redmine API to manage users, projects, and issues. Specifically for the User - Update operation, it updates an existing user's details in Redmine by specifying the user ID and any fields to modify. This is useful in scenarios where user information needs to be maintained or synchronized automatically, such as updating user roles, statuses, or custom attributes after changes in an external system.
Practical examples include:
- Automatically locking a user account when they leave an organization.
- Changing a user's email notification preferences based on team settings.
- Updating custom fields for users to reflect new internal categorizations.
Properties
| Name | Meaning |
|---|---|
| User ID | The unique identifier of the user to update. |
| Additional Fields | A collection of optional fields to update for the user: |
| - Admin | Whether the user has administrator privileges (true/false). |
| - Authentication Source ID | The ID of the authentication source linked to the user. |
| - Custom Fields | Multiple custom fields, each with an ID and value, allowing flexible user attribute updates. |
| - Email Notifications | Options for email notifications the user receives: all, none, only assigned, only for my events, only owner. |
| - Must Change Password | Whether the user must change their password upon next login (true/false). |
| - Status | The status of the user: Active, Registered, or Locked. |
Output
The node outputs JSON data representing the updated user object returned from the Redmine API. This typically includes the user's current state after the update, reflecting all changed properties.
If the node supports binary data output (not indicated here), it would represent associated files or attachments related to the user, but this is not applicable for the User Update operation.
Dependencies
- Requires connection to a Redmine instance via its REST API.
- Needs an API key credential for authentication with Redmine.
- The node expects the Redmine base URL and API key to be configured in n8n credentials.
Troubleshooting
- Invalid User ID: If the provided User ID does not exist, the API will return an error. Verify the User ID before running the node.
- Insufficient Permissions: Updating certain fields may require admin privileges. Ensure the API key used has adequate permissions.
- Malformed Custom Fields: Custom fields must have valid IDs and values; otherwise, the API may reject the request.
- Network Issues: Connection errors to the Redmine server can cause failures. Check network connectivity and Redmine server availability.
- Error Messages: Errors are returned in the
errorfield in the output JSON if "Continue On Fail" is enabled. Review these messages for troubleshooting.