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. Specifically, for the Time Entry resource and the Get One operation, it retrieves a single time entry record by its unique identifier. This is useful when you need detailed information about a specific time entry logged in Easy Redmine, such as for auditing, reporting, or further processing within an automation workflow.
Practical examples:
- Fetching details of a particular time entry to verify hours worked on a project.
- Retrieving a time entry before updating or adding comments related to that entry.
- Using the retrieved data to generate custom reports or notifications.
Properties
| Name | Meaning |
|---|---|
| Time Entry ID | The unique numeric identifier of the time entry to retrieve. Required for "Get One" operation on Time Entry resource. |
Output
The node outputs JSON data representing the requested time entry object from Easy Redmine. The structure typically includes fields such as the time entry's ID, user, project, issue, spent time, date, and any other metadata associated with that time entry.
If the node supports binary data output (not indicated here), it would represent attachments or files related to the time entry, but this node primarily returns JSON data.
Dependencies
- Requires an API key credential for Easy Redmine with appropriate permissions to read time entries.
- The node expects the Easy Redmine domain URL configured in the credentials.
- No additional external dependencies are required beyond the Easy Redmine API access.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Time Entry ID will result in an error or empty response.
- Network or authentication failures due to incorrect API credentials or domain configuration.
- Rate limiting or permission errors if the API key lacks sufficient rights.
Error messages:
- Errors returned from the API are captured and can include messages like "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 problematic item index.
- To resolve, verify the Time Entry ID, check API credentials, and ensure the user has access rights.
Links and References
- Easy Redmine API Documentation — Official API docs for understanding available endpoints and data structures.
- n8n Documentation — For general guidance on using n8n nodes and handling credentials.