[ Productivity ]
Harvest integration for your workflows.
Connect Harvest to Collabase once and use 11 actions in your workflows. No code needed, hosted in Switzerland.
Harvest in Collabase
Connect Harvest to Collabase once and use 11 actions in your workflows. No code needed, hosted in Switzerland.
[ About the service ]
Time Tracking Software with Invoicing
How to connect it
- Open the integrations in the workspace settings.
- Choose Harvest and connect your account.
- Add a trigger or an action to the workflow.
Harvest triggers
Harvest does not start a workflow on its own. You use its actions after any other trigger.
Harvest actions
| Name | Description | Fields |
|---|---|---|
| Get Clients | Fetches Clients |
|
| Get Estimates | Fetches Estimates |
+ 1
|
| Get Expenses | Fetches expenses |
+ 3
|
| Get Invoices | Fetches invoices |
+ 2
|
| Get Projects | Fetches projects |
|
| Get Roles | Fetches Roles |
|
| Get Tasks | Fetches Tasks |
|
| Get Time Entries | Fetches Time Entries |
+ 6
|
| Get Users | Fetches Users |
|
| Uninvoiced Report | Uninvoiced hours and expenses for all billable projects |
|
| Custom API Call | Make a custom API call to a specific endpoint |
+ 3
|
[ Productivity ]
Related integrations
Tools that often share a workflow.
Questions about Harvest
What can I automate with Harvest in Collabase?
Harvest brings 11 actions and 0 triggers, for example Get Clients, Get Estimates, Get Expenses, Get Invoices and 7 more. You combine them in a workflow without code and mix them with every other integration.
How do I connect Harvest to Collabase?
You open the integrations in the workspace settings, choose Harvest and connect your account once, using OAuth 2.0. After that all triggers and actions are available in the workflow.
Does the Harvest integration cost extra?
No. All integrations are included in every licence, in the Isolated Cloud and in Self-Hosted operation. There is no module price.
Test it against your own content. A proof of concept is ready within days.
We set up an instance with your content and you test it against real workflows. In a first conversation we clarify scope, operating model and timing.