Everhour icon

Everhour

Interact with Everhour API
Join our community

Actions32

Overview

This node interacts with the Everhour API to update a specific timecard entry for a user on a given date. It allows modifying clock-in and clock-out times as well as the break duration in seconds. This operation is useful for correcting or adjusting recorded work hours, ensuring accurate time tracking and payroll calculations.

Common scenarios:

  • Adjusting an employee's clock-in or clock-out time after a manual correction.
  • Adding or updating break durations that were not initially recorded.
  • Fixing timecard entries due to missed punches or errors in automatic tracking.

Practical example:
An HR manager notices that an employee forgot to clock out at the end of the day. Using this node, they can update the timecard by setting the correct clock-out time and break duration for that date, ensuring the total worked hours are accurate.

Properties

Name Meaning
User ID The numeric identifier of the user whose timecard is being updated.
Date The date of the timecard entry to update (date and time format).
Clock In Time The new clock-in time in "HH:MM" format (optional; only set if updating).
Clock Out Time The new clock-out time in "HH:MM" format (optional; only set if updating).
Break Time (Seconds) Duration of breaks taken during the work period, expressed in seconds (optional).

Output

The node outputs the updated timecard data as JSON. The structure corresponds to the response from the Everhour API for a timecard update, typically including fields such as user ID, date, clock-in time, clock-out time, break time, and possibly other metadata related to the timecard entry.

No binary data output is produced by this node.

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.
    • Incorrectly formatted clock-in or clock-out times (not matching "HH:MM") may result in validation errors.
    • Insufficient permissions or invalid API credentials will lead to authentication errors.
    • Network connectivity problems can cause request failures.

  • Error messages and resolutions:

    • "Unauthorized" or "Authentication failed": Verify that the API key credential is correctly configured and has proper permissions.
    • "Invalid date format": Ensure the date parameter is provided in a valid ISO date-time format.
    • "Invalid time format": Confirm clock-in and clock-out times follow the "HH:MM" format.
    • "User not found": Check that the user ID exists in Everhour.
    • If the node throws a generic error, enabling "Continue On Fail" can help process subsequent items without stopping the workflow.

Links and References

Discussion