Easy Redmine icon

Easy Redmine

Easy Redmine Operations

Overview

This node integrates with Easy Redmine to manage users and other resources. Specifically, the User - Create operation allows you to create a new user in Easy Redmine by providing essential user details such as login, first name, last name, email, and optional additional information like phone number and custom fields.

Common scenarios for this node include automating user onboarding processes, syncing user data from other systems into Easy Redmine, or programmatically managing user accounts without manual intervention.

For example, you could use this node to automatically create a new user in Easy Redmine whenever a new employee is added to your HR system, ensuring they have immediate access to project management tools.

Properties

Name Meaning
Login The unique login identifier for the new user.
First Name The user's first name.
Last Name The user's last name.
Email The user's email address (e.g., name@email.com).
Phone (Optional) The user's phone number.
Custom Fields (Optional) Additional custom fields for the user. Each custom field requires an ID and a value.

Output

The node outputs JSON data representing the created user entity as returned by the Easy Redmine API. This typically includes the user's ID, login, name, email, and any other relevant metadata assigned by the system.

If the node supports binary data output (not indicated here), it would represent associated files or attachments related to the user, but this operation focuses on JSON user data only.

Dependencies

  • Requires an active connection to an Easy Redmine instance.
  • Needs an API authentication token configured in the node credentials to authorize requests.
  • The base URL for API requests is taken from the configured domain credential.
  • No additional external dependencies are required beyond the Easy Redmine API.

Troubleshooting

  • Common Issues:

    • Missing or invalid API credentials will cause authentication failures.
    • Providing incomplete mandatory fields (e.g., missing login or email) may result in validation errors from the API.
    • Incorrect custom field IDs or values can cause the API to reject the request.
  • Error Messages:

    • Errors returned from the API are captured and presented in the node output under an error key.
    • If multiple errors occur, they are concatenated into a single message.
    • To resolve errors, verify all required fields are correctly filled and that the API credentials have sufficient permissions.

Links and References

Discussion