Productivity

Harvest

Harvest is time tracking and invoicing for client work — people log hours against a project, and those hours become invoices.

Authentication

  • OAuth 2.0
  • Personal access token

Actions

Generic API request. Call any Harvest API endpoint on this connection, for the case where no shipped action covers it yet. The connection supplies the base URL, the authentication and the egress route, so only the path, query and body are yours to fill.

  • Create clientCreate a client (POST /clients, application/json).
  • Create time entryCreate a time entry (POST /timeentries, application/json).
  • Delete time entryDestructiveDelete a time entry (DELETE /timeentries/{id}).
  • Get projectRead one Harvest project by id — the unit that time is tracked against.
  • Get time entryRead one Harvest time entry by id — a single logged block of work.
  • List clientsList the clients in the Harvest account — the organisations that projects and invoices are billed to.
  • List invoicesList the invoices in the Harvest account.
  • List projectsList projects, most recently created first, e.g. to find a project id before reading its time entries.
  • List time entriesList time entries sorted by spentdate, e.g. a week of billable hours on one project.
  • List usersList the people in the Harvest account — the team members who log time, as opposed to the clients they bill.
  • Update time entryDestructiveUpdate a time entry (PATCH /timeentries/{id}, application/json).

Triggers

  • New or updated clientStarts when a client is created or updated in Harvest, so a workflow can react to billing-relationship changes.
  • New or updated invoiceStarts when an invoice is created or updated in Harvest, so a workflow can react to billing changes.
  • New or updated projectStarts when a project is created or updated in Harvest, so a workflow can react to scope or status changes.
  • New or updated time entryStarts when a time entry is created or updated in Harvest, so a workflow can react to logged time.
  • New or updated userStarts when a team member is created or updated in Harvest, so a workflow can react to roster changes.

Product names, logos and brands are the property of their respective owners and are used here for identification only. Their use does not imply endorsement by, or affiliation with, those owners.