Actions32
- Assignment Actions
- Client Actions
- Project Actions
- Report Actions
- Task Actions
- Time Actions
- Timecard Actions
- Webhook Actions
Overview
This node interacts with the Everhour API to retrieve a specific timecard for a user on a given date. It is useful in scenarios where you need to fetch detailed time tracking information for an individual user on a particular day, such as for attendance monitoring, payroll processing, or productivity analysis.
Practical examples:
- Fetching a user's timecard to verify clock-in and clock-out times.
- Retrieving daily work hours for a user to calculate billable hours.
- Integrating timecard data into HR or accounting systems for automated reporting.
Properties
| Name | Meaning |
|---|---|
| User ID | The numeric identifier of the user whose timecard is being retrieved. |
| Date | The specific date (in date-time format) for which the timecard is requested. |
Output
The output is a JSON object representing the timecard data for the specified user and date. This typically includes details such as clock-in time, clock-out time, break durations, and possibly other time-tracking metadata associated with that day.
No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating requests to the Everhour API.
- The node uses the Everhour API base URL configured in the credential.
- Network access to the Everhour API endpoint is necessary.
Troubleshooting
Common issues:
- Invalid or missing user ID or date parameters will cause the API request to fail.
- Authentication errors if the API key credential is incorrect or expired.
- Network connectivity problems preventing access to the Everhour API.
Error messages:
- Errors returned from the API (e.g., "User not found" or "Timecard not available") will be surfaced.
- Authentication failures will indicate invalid credentials.
Resolutions:
- Verify that the User ID and Date inputs are correctly provided and valid.
- Ensure the API key credential is properly set up and has sufficient permissions.
- Check network connectivity and firewall settings to allow outbound API calls.
Links and References
- Everhour API Documentation
- n8n Documentation on HTTP Request Node (for understanding API calls)
- Date and Time Handling in n8n