Log time on an Everhour task
everhour_log_timeLog hours worked on an Everhour task with duration (hours or seconds), optional date, comment, and user ID.
Instructions
Log (add) tracked time against an Everhour task. This is the primary tool for recording hours worked.
Args:
task_id (string): Everhour task ID. For Asana tasks: 'as:'.
duration ({ hours?: number } | { seconds?: number }): How long to log. Provide ONE of:
hours: decimal hours, 0-24 (e.g. 1.5 = 1h 30m)
seconds: integer seconds, 60-86400
date (string, optional): YYYY-MM-DD. Defaults to today.
comment (string, optional): Note describing the work.
user_id (number, optional): Defaults to the authenticated user (only admins can log for others).
response_format ('markdown' | 'json'): Output format
Returns the created time record: { "id": number, "date": "YYYY-MM-DD", "user": number, "time": number, // seconds "comment": string | null, "task": { "id": string, "name"?: string }, "createdAt": "ISO-8601" }
Examples:
"Log 2 hours on task as:1208... for today" → task_id='as:1208...', duration={ hours: 2 }
"Log 45 minutes on OPS-123 yesterday with comment 'fix flaky test'" → after resolving the task ID: duration={ seconds: 2700 }, date='YYYY-MM-DD', comment='fix flaky test'
For an Asana ticket where you only have the GID, prefer everhour_log_time_for_asana_task.
Error Handling:
404 → task not synced; verify with everhour_find_task_by_asana_id
409 → a time record already exists for that user/date — use everhour_update_time_record instead
422 → validation error (duration too long, future date, etc.)
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| date | No | Date the time was worked, YYYY-MM-DD. Defaults to today if omitted. | |
| comment | No | Optional note describing the work performed. | |
| task_id | Yes | Everhour task ID. For Asana-synced tasks the ID is 'as:<asanaGid>' (e.g. 'as:1208034567890123'). | |
| user_id | No | Everhour user ID to log time for. Defaults to the authenticated user. | |
| duration | Yes | ||
| response_format | No | Output format: 'markdown' for human-readable text or 'json' for machine-readable structured data | markdown |