clickup_get_time_entries
Retrieve time entries from a ClickUp Workspace filtered by date range, space, folder, list, or task, with support for billable and assignee filters. Use to audit tracked time or build timesheet reports.
Instructions
List time entries in a Workspace, optionally scoped by date range and location.
Calls GET /team/{team_id}/time_entries, ClickUp's Time Tracking 2.0
surface. Without start_date/end_date ClickUp returns every entry in
the Workspace, so narrow the range and/or scope (space/folder/list/task)
on busy Workspaces.
When to Use:
Auditing or summarizing time logged across a Workspace, Space, Folder, List, or single task over a period.
Building a timesheet/report (combine with
is_billableandassignee).
When NOT to Use:
To fetch one known entry by id — use
clickup_get_time_entry.To check only the entry currently running for a user — use
clickup_get_running_time_entry(cheaper, no date math needed).
Returns:
A markdown (default) or JSON list of entries — id, task, user, start/end,
duration, billable flag, and tags. A negative duration means that
entry is an actively running timer for that user (elapsed-so-far), not a
finished duration.
Pagination:
This endpoint has no limit/offset — ClickUp returns the full matching
set in one call. Display here is capped at 50 rows for context-window
safety; narrow start_date/end_date or the location filters to see
everything without truncation.
Examples: params = {"team_id": "123", "start_date": 1700000000000, "end_date": 1700600000000, "is_billable": True} params = {"team_id": "123", "task_id": "abc123", "include_task_tags": True}
Error Handling: 404 means team_id/space_id/folder_id/list_id/task_id doesn't exist or isn't accessible; 429 means the ~100 req/min per-token rate limit was hit.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| params | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |