Short answer: You can list harvest time entries in Harvest by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Harvest List Harvest Time Entries action to a workflow, map its 3 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
From Date from | date | Optional | From Date. (date/time) |
To Date to | date | Optional | To Date. (date/time) |
Project ID project_id | number | Optional | Filter by project |
{"from": "{{trigger.from}}","to": "{{trigger.to}}","project_id": "{{trigger.project_id}}"}
{"time_entries": [{"id": 12345,"task": {"name": "Development"},"hours": 2.5,"notes": "Feature work","project": {"name": "My Project"},"spent_date": "2026-04-11"}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.