Harvest

Enable the Harvest connector in your fastn dashboard, then let each customer authenticate their own Harvest account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Harvest client code in your app and no per-customer branch in your codebase. Setup is 4 steps.

Yes. Every connection is scoped to the individual customer, so each authorises their own Harvest account and only ever sees their own work items, assignees and due dates. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.

Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reads logged time and summarises where a week went.

fastn does. When Harvest changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.

Yes. Items can be created, updated, assigned and transitioned from your product, and changes made in Harvest can trigger your workflows in return.

Yes. However a team has configured Harvest, whether that is custom fields, statuses and workflow stages or its own calendars and working hours, those are mapped per customer, so an unusual setup works without custom code from you.

A common starting point: log time against their own projects and tasks from inside your product. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.

It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Harvest does not change your per-connector cost. You can start free with 3 connected accounts.