Actions37
- Issue Actions
- Lead Actions
- Opportunity Actions
- Account Actions
- Attendance Actions
- Personal Contact Actions
- Time Entry Actions
- User Actions
Overview
This node integrates with the Easy Redmine platform to perform various operations on its resources. Specifically, for the Attendance resource and the Get One operation, it retrieves a single attendance record by its unique identifier. This is useful when you need detailed information about a specific attendance entry, such as checking an employee's attendance on a particular day or verifying attendance details for reporting purposes.
Practical examples:
- Fetching attendance details of an employee for payroll processing.
- Retrieving a specific attendance record to verify time logged during a project.
- Accessing attendance data to audit or correct entries.
Properties
| Name | Meaning |
|---|---|
| Attendance ID | The unique numeric identifier of the attendance record to retrieve. |
Output
The node outputs JSON data representing the requested attendance record. The structure typically includes fields relevant to attendance such as date, user, status, hours worked, and any other metadata defined by Easy Redmine for attendance entities.
If the node supports binary data output (not indicated here), it would be summarized accordingly, but in this case, the output is purely JSON.
Dependencies
- Requires an API key credential for authenticating with the Easy Redmine API.
- Needs the base URL of the Easy Redmine instance configured in the node credentials.
- The node depends on Easy Redmine's REST API being accessible and properly configured to allow read access to attendance records.
Troubleshooting
Common issues:
- Invalid or missing Attendance ID will cause the operation to fail.
- Network connectivity problems or incorrect API endpoint configuration can prevent successful API calls.
- Insufficient permissions on the API key may result in authorization errors.
Error messages:
- Errors returned from the API are captured and presented; if multiple errors exist, they are concatenated into a single message.
- If the node is set to continue on failure, errors for individual items are returned as JSON objects with an
errorfield. - To resolve errors, verify the Attendance ID is correct, ensure API credentials have proper permissions, and confirm network connectivity.
Links and References
- Easy Redmine Official Website
- Easy Redmine API Documentation (Assumed typical location; please verify with your Easy Redmine instance)