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 manage and retrieve time tracking data. Specifically, the "Time" resource with the "Get Many" operation allows users to fetch multiple time entries within a specified date range. This is useful for scenarios such as generating reports on tracked work hours, auditing time logs, or integrating time data into other systems.
For example, a project manager could use this node to pull all time entries between two dates to analyze team productivity or billable hours.
Properties
| Name | Meaning |
|---|---|
| From Date | Start date for filtering time entries. Only entries on or after this date will be retrieved. |
| To Date | End date for filtering time entries. Only entries on or before this date will be retrieved. |
Output
The output consists of an array of JSON objects, each representing a single time entry retrieved from Everhour. Each object contains details about the time entry such as task ID, duration, date, comments, and other metadata provided by the Everhour API.
No binary data is output by this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Everhour API.
- The node uses the base URL configured in the credential to send HTTP GET requests.
- Proper network access to the Everhour API endpoint is necessary.
Troubleshooting
- Empty results: If no time entries are returned, verify that the date range ("From Date" and "To Date") is correct and that there are time entries recorded in that period.
- Authentication errors: Ensure the API key credential is valid and has sufficient permissions to read time entries.
- API rate limits: If many requests are made in a short time, the Everhour API might throttle requests. Implement retries or reduce request frequency.
- Invalid date format: Make sure the "From Date" and "To Date" inputs are valid date-time values.