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 multiple timecard records for a specified user. The "Get Many" operation under the "Timecard" resource fetches timecards associated with a user, optionally filtered by date. This is useful for scenarios where you want to analyze or process a user's time tracking data in bulk, such as generating reports, auditing work hours, or integrating timecard data into other systems.
Practical examples:
- Fetch all timecards for a user within a specific date range to calculate total hours worked.
- Retrieve recent timecards to monitor attendance or compliance.
- Integrate timecard data into payroll or project management workflows.
Properties
| Name | Meaning |
|---|---|
| User ID | The numeric identifier of the user whose timecards are to be retrieved. |
| Date | (Optional) A specific date to filter the timecards returned for the user (YYYY-MM-DD). |
Output
The output is an array of JSON objects, each representing a timecard record for the specified user. Each timecard object typically includes details such as clock-in and clock-out times, break durations, and the date of the timecard.
The structure of each output item (json field) corresponds directly to the timecard data returned by the Everhour API for that user.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential configured in n8n to authenticate requests to the Everhour API.
- The node uses the Everhour API base URL from the configured credentials.
- Network access to the Everhour API endpoint is necessary.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Providing an incorrect or non-existent User ID may result in empty results or errors.
- Date format must be valid ISO date strings; otherwise, the API might reject the request.
Error messages:
- Authentication errors indicate problems with the API key setup; verify and reconfigure credentials.
- HTTP errors from the API (e.g., 404 Not Found) suggest invalid parameters like user ID or date.
- Rate limiting errors may occur if too many requests are made in a short period; implement retries or delays.