Skip to content
ActionHarvestUpdated May 2026

How do I create a Harvest time entry?

Short answer: Drop the "HarvestCreate Harvest Time Entry" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

FieldTypeRequiredDescription
Project ID
project_id
numberRequiredThe Project ID assigned by Harvest. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label.
Task ID
task_id
numberRequiredTask ID
Date
spent_date
dateRequiredDate. (date/time)
Hours
hours
numberRequiredHours. e.g. "2.5"
Notes
notes
stringOptionalNotes
Sample request
{
"project_id": "{{trigger.project_id}}",
"task_id": "{{trigger.task_id}}",
"spent_date": "{{trigger.spent_date}}",
"hours": "2.5",
"notes": "{{trigger.notes}}"
}
Returns
{
"id": 12345,
"task": {
"id": 200,
"name": "Development"
},
"hours": 2.5,
"project": {
"id": 100,
"name": "My Project"
},
"spent_date": "2026-04-11"
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Create Harvest Time Entry.

Any of these apps can fire this action as part of a workflow.

FAQ

Questions about Create Harvest Time Entry.

What does the Create Harvest Time Entry action do in Harvest?
Posts a time entry with project, task, hours, billable flag, notes. For "calendar meeting → auto-log time to client project" workflows that keep timesheets complete without manual entry.
What inputs does Create Harvest Time Entry require?
Required: Project ID, Task ID, Date, Hours. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Harvest returns an error?
The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does Create Harvest Time Entry support batch operations?
Yes. Run Create Harvest Time Entry inside a Loop node to process arrays. Tiny Command handles Harvest's rate limits automatically so you don't have to throttle manually.
More actions

Other Harvest actions.

Send create harvest time entry from your workflows.

Triggered by anything in the catalog. Free tier available. No credit card.