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 retrieve multiple time entry records based on a specified query. It is designed to fetch batches of time entries efficiently, supporting pagination and filtering through predefined queries.
Common scenarios where this node is beneficial include:
- Generating reports or analytics on time spent across projects or tasks.
- Synchronizing time tracking data from Easy Redmine into other systems.
- Automating billing or payroll processes by extracting detailed time logs.
For example, a user might select a saved time entry query that filters entries for a specific project and then use this node to pull all matching time entries for further processing or export.
Properties
| Name | Meaning |
|---|---|
| EasyRedmine Time Entries Query Name or ID | Select a predefined query to filter the time entries returned. You can choose from a list or specify an ID using an expression. |
| Return All | Boolean flag indicating whether to return all matching results or limit the number of results returned. |
| Offset | Number specifying the starting point in the result set (used when not returning all). |
| Limit (1-100) | Maximum number of results to return when not returning all. Must be between 1 and 100. |
Output
The node outputs an array of JSON objects representing time entries retrieved from Easy Redmine. Each object corresponds to a single time entry record containing fields such as time spent, associated task or issue, user information, timestamps, and other relevant metadata defined by the selected query.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Easy Redmine instance.
- The node expects the base URL of the Easy Redmine API to be configured via credentials.
- Uses Easy Redmine's predefined time entry queries to filter results.
Troubleshooting
Common Issues:
- Invalid or expired API credentials will cause authentication failures.
- Specifying a non-existent or unauthorized time entry query ID will result in empty results or errors.
- Requesting too many results without enabling "Return All" may lead to incomplete data retrieval.
Error Messages:
- Errors related to API request failures typically include messages from Easy Redmine's API response.
- If the node throws an error mentioning "errors" in context data, it usually indicates issues with the query or permissions.
Resolutions:
- Verify API credentials and ensure they have sufficient permissions.
- Confirm the time entry query exists and is accessible by the authenticated user.
- Use the "Return All" option carefully to avoid performance issues; otherwise, adjust offset and limit parameters appropriately.