Actions32
- Assignment Actions
- Client Actions
- Project Actions
- Report Actions
- Task Actions
- Time Actions
- Timecard Actions
- Webhook Actions
Overview
This node integrates with the Everhour API to create a new time entry associated with a specific task. It allows users to log time spent on tasks by specifying the task ID, duration in seconds, date of the time entry, and an optional comment. This is useful for teams or individuals who want to track work hours precisely within their project management workflow.
Common scenarios:
- Logging billable hours for client projects.
- Tracking time spent on specific tasks for reporting or payroll.
- Adding manual time entries after completing work offline.
Example:
A user completes a 2-hour task and wants to record this in Everhour. They provide the task ID, set the time to 7200 seconds (2 hours), specify the date when the work was done, and optionally add a comment describing the work.
Properties
| Name | Meaning |
|---|---|
| Task ID | The unique identifier of the task to which the time entry will be linked. |
| Time (Seconds) | Duration of the time entry in seconds (e.g., 3600 for one hour). |
| Date | The date and time when the time was logged (timestamp). |
| Comment | Optional text comment describing the time entry or additional details about the work. |
Output
The node outputs the JSON response from the Everhour API representing the created time entry. This typically includes details such as the time entry ID, task association, time duration, date, comment, and other metadata returned by the API.
No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating with 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
- Authentication errors: Ensure that the API key credential is correctly configured and has sufficient permissions.
- Invalid Task ID: If the task ID does not exist or is incorrect, the API will return an error. Verify the task ID before creating the time entry.
- Date format issues: The date must be provided in a valid ISO 8601 format; otherwise, the API may reject the request.
- Time value errors: The time duration should be a positive number representing seconds. Negative or zero values might cause errors.
- API rate limits: Excessive requests may lead to rate limiting by Everhour. Implement retries or backoff if needed.