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 its resources. Specifically, for the User resource with the Get Many operation, it retrieves multiple user records from Easy Redmine based on optional filtering criteria.
Typical use cases include:
- Fetching a list of users filtered by predefined or custom queries.
- Retrieving paginated user data for reporting or synchronization purposes.
- Automating workflows that require bulk user information from Easy Redmine.
For example, you might use this node to get all users who belong to a certain department or have specific roles, then process or export that data further in your workflow.
Properties
| Name | Meaning |
|---|---|
| EasyRedmine User Query Name or ID | Choose a predefined query to filter the user results. You can select from a loaded list of queries or specify a query ID using an expression. |
| Return All | Boolean flag to decide whether to return all matching users or limit the number of results. |
| Offset | Number indicating the starting point (offset) in the result set when not returning all results. |
| Limit (1-100) | Maximum number of user records to return when not returning all. Must be between 1 and 100. |
Output
The node outputs an array of JSON objects representing user entities retrieved from Easy Redmine. Each object corresponds to a user and contains fields as defined by Easy Redmine's user model (e.g., user ID, name, email, role, etc.).
If binary data were involved (not applicable here), it would be summarized accordingly, but this operation returns only JSON data.
Dependencies
- Requires connection to an Easy Redmine instance via an API key credential.
- The node expects the base URL of the Easy Redmine domain to be configured in the credentials.
- No additional external dependencies are required beyond the Easy Redmine API access.
Troubleshooting
Common Issues:
- Incorrect or missing API credentials will cause authentication failures.
- Specifying an invalid query ID or name may result in empty results or errors.
- Setting
Return Allto false but providing an offset or limit outside allowed ranges may cause unexpected behavior.
Error Messages:
- Errors returned from the Easy Redmine API are captured and presented. For example, if the query ID is invalid, the error message from the API will be shown.
- Network or authentication errors will typically indicate issues with credentials or connectivity.
Resolutions:
- Verify API credentials and domain configuration.
- Ensure the query ID or name exists and is accessible.
- Use valid numeric values for offset and limit within specified bounds.