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 perform various operations on different resources such as issues, leads, opportunities, accounts, attendances, personal contacts, time entries, and users. Specifically, for the User resource with the Get One operation, the node retrieves detailed information about a single user by their unique User ID.
Typical use cases include:
- Fetching detailed user profile data for display or processing in workflows.
- Integrating user information into other systems or reports.
- Automating user-related tasks based on retrieved user details.
For example, you might use this node to get a user's full profile before assigning them a task or sending a notification.
Properties
| Name | Meaning |
|---|---|
| User ID | The unique numeric identifier of the user to retrieve. |
The "User ID" property is required when performing the "Get One" operation on the "User" resource. It specifies which user record to fetch.
Output
The node outputs JSON data representing the user entity retrieved from Easy Redmine. The structure typically includes all available fields for a user, such as name, email, role, status, and any custom attributes defined in Easy Redmine.
If the node supports binary data output (not indicated here), it would be summarized accordingly, but for this operation, the output is purely JSON.
Dependencies
- Requires an API key credential for Easy Redmine authentication.
- Needs the Easy Redmine domain URL configured in the node credentials.
- Relies on Easy Redmine's REST API being accessible and properly configured.
Troubleshooting
Common Issues:
- Invalid or missing User ID: Ensure the User ID is provided and corresponds to an existing user.
- Authentication errors: Verify that the API key and domain are correctly set up.
- Network or connectivity problems: Confirm that the Easy Redmine instance is reachable.
Error Messages:
- Errors returned from the API will be captured and can include messages like "User not found" if the ID does not exist.
- If the node fails and "Continue On Fail" is disabled, execution stops with an error referencing the item index.
- When "Continue On Fail" is enabled, errors are returned as part of the output JSON with an "error" field describing the issue.
Resolving these usually involves checking input parameters, credentials, and network access.