Everhour icon

Everhour

Interact with Everhour API

Overview

This node interacts with the Everhour API to manage time entries, specifically allowing you to update existing time records. The "Update Time" operation lets you modify details of a particular time entry such as the duration, date, and any associated comments.

Common scenarios where this node is useful include:

  • Correcting or adjusting logged work hours after the fact.
  • Adding or updating notes/comments on a time entry for better context.
  • Changing the date of a time entry if it was recorded incorrectly.

For example, if a user accidentally logged 1 hour instead of 2 hours for a task on a specific date, this node can update that time entry to reflect the correct duration.

Properties

Name Meaning
Time Entry ID The unique identifier of the time entry to update.
Time (Seconds) The new time duration in seconds to set for the time entry.
Date The date associated with the time entry.
Comment Optional comment or note describing the time entry.

Output

The node outputs the updated time entry data as JSON. This typically includes all fields returned by the Everhour API for a time entry after the update, such as the updated time duration, date, comment, and other metadata related to the time entry.

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 credentials.
  • Network access to the Everhour API endpoint is necessary.

Troubleshooting

  • Invalid Time Entry ID: If the provided Time Entry ID does not exist or is incorrect, the API will return an error. Verify the ID before running the node.
  • Authentication Errors: Ensure the API key credential is valid and has sufficient permissions to update time entries.
  • Invalid Date or Time Format: The date must be in a valid datetime format accepted by the API; otherwise, the request may fail.
  • Missing Required Fields: Time Entry ID, Time (seconds), and Date are required. Omitting these will cause errors.
  • API Rate Limits: Frequent updates might hit API rate limits; handle such errors by retrying after some delay.

Links and References

Discussion