The Everhour integration brings time entry data into WorkSights as Time Log activities, placing your team’s logged hours in the daily timeline alongside work from your connected project management, communication, and delivery tools.

What sets Everhour apart from other time tracking integrations is task-level context. When a time entry is linked to a task in an external tool (Asana, ClickUp, Jira, Monday, GitHub, Basecamp, or Trello), WorkSights captures that link alongside the entry.

WorkSights AI can connect logged time to the task it was logged against when analyzing project or team activity, without any additional configuration on your part.

Everhour requires a paid plan for API access. Free-tier Everhour accounts cannot connect.

For connection steps, see Everhour Setup.

What WorkSights Receives

Time entries

Each logged time entry appears as a Time Log activity in WorkSights. The activity title follows the Everhour hierarchy: Client → Project → Task → Time Log. Duration is displayed in minutes.

Entries logged without a project or task assigned appear as Time Log, with the entry name shown in the activity detail instead.

Only activity that occurs after the integration is connected will appear in WorkSights. When a time entry is deleted in Everhour, WorkSights removes the corresponding activity.

Comments

If a comment is added to a time entry in Everhour, the text appears in the activity detail field in WorkSights.

Task Links

Time entries linked to tasks in external project management tools carry a task reference that WorkSights captures alongside the entry (a ClickUp task ID, a Jira issue key, an Asana task ID, and so on). WorkSights AI can connect logged time to the source task when analyzing project or team activity.

Users

WorkSights imports Everhour team members and matches them to WorkSights users by full name. Everhour does not expose email addresses through its API. Users whose names do not match exactly require manual mapping from the Users tab.

WorkSights does not ingest expenses, invoices, estimates, or data from free-tier Everhour accounts.

How Everhour Activity Appears

Everhour time entries appear on the activity timeline as Time Log activities sourced from Everhour. Each entry shows the start and end time, duration in minutes, and the full title hierarchy: Client → Project → Task → Time Log. Entries logged without a project or task show as Time Log with the entry name in the detail.

Time Log is a passive activity type. Everhour entries are displayable by default and not scored, which means they appear in the timeline and activity stream but do not contribute to performance calculations. Scorable can be toggled manually per entry if needed.

About Timestamps

Everhour provides a date and a total duration for each time entry. It does not provide start or end times.

WorkSights infers both from what it has: the moment the entry is saved becomes the end time, and start is calculated backward from the duration. A 45-minute entry saved at 3:00 PM appears in WorkSights as 2:15 PM to 3:00 PM.

For entries logged retroactively, the times shown in WorkSights reflect when the entry was submitted, not when the work happened. If someone fills in four days of timesheets on Friday afternoon, all four entries will show times anchored to Friday afternoon. WorkSights has no way to reconstruct the time of day on each prior date. Everhour does not capture that information.

This same behavior applies to Harvest when start and end times are not enabled in Harvest's settings.

Integration Page Overview

The Everhour integration page contains three tabs:

• ‍Overview: connection status and integration owner‍
• Users: Everhour team members mapped to WorkSights users‍
• Connections: connected Everhour accounts

Data Access and Privacy

WorkSights accesses Everhour through the API token provided during setup. The integration is read-only.

WorkSights receives:

• Time entry duration, date, and billable flag
• Client, project, and task names used to build the activity title
• Comments from the time entry comment field
• Task links to external project management tools where present

WorkSights does not receive:

• Expenses, invoices, or estimates
• Financial or billing data
• Any content beyond time tracking metadata

Troubleshooting

If Everhour activity is not appearing:

• Check that the affected user is mapped in the Users tab. Everhour matches by full name, not email. If the name in Everhour differs from the name in WorkSights, the user will not be mapped automatically and will need to be matched manually.
• Confirm the Everhour account is on a paid plan. Free-tier accounts cannot authenticate with the API.
• If no activity has appeared since connecting, try disconnecting and reconnecting from Services to re-establish the webhook subscription.
• For persistent issues, contact support via the in-app chat.

If times shown look earlier or later than expected:

• Everhour does not provide start or end times on entries. WorkSights uses the time an entry was saved as the end time and calculates start from the duration. For retroactively logged entries, times will reflect when the entry was submitted, not when the work happened. See the Timestamps section above.

If the Reconnect button is missing:

• This is expected for Everhour. API tokens do not expire, so there is no reconnect flow. To update your token, disconnect the integration from Services and reconnect with the new one.

Related Guides

Everhour Setup