Connect Harvest to monday.com
We build integrations that let monday.com drive Harvest: a change on a board runs an action in Harvest.
What monday.com can do in Harvest
Actions a change on a board can run in Harvest.
| Action |
|---|
| Client |
| Create client |
| Delete client |
| Get client |
| Get many clients |
| Update client |
| Company |
| Get company |
| Contact |
| Create contact |
| Delete contact |
| Get contact |
| Get many contacts |
| Update contact |
| Estimate |
| Create estimate |
| Delete estimate |
| Get estimate |
| Get many estimates |
| Update estimate |
| Expense |
| Create expense |
| Delete expense |
| Get expense |
| Get many expenses |
| Update expense |
| Invoice |
| Create invoice |
| Delete invoice |
| Get invoice |
| Get many invoices |
| Update invoice |
| Project |
| Create project |
| Delete project |
| Get project |
| Get many projects |
| Update project |
| Task |
| Create task |
| Delete task |
| Get task |
| Get many tasks |
| Update task |
| Time entry |
| Time entry: Create via duration |
| Create via start and end time |
| Delete time entry |
| Time entry: Delete external reference |
| Get time entry |
| Get many time entries |
| Restart time entry |
| Stop time entry |
| Update time entry |
| User |
| Create user |
| Delete user |
| Get user |
| Get many users |
| Me user |
| Update user |
Recipes
Each recipe is one change and what it does on the other side.
When an item is created, create a project in Harvest
When a subitem is created, add a task to the Harvest project
When a column changes, update the contact details in Harvest
Keep Harvest as it is. We connect it to monday.com.
We build the integration around what you already have. Harvest keeps doing the job it does for you today, and monday.com gets the data it needs to plan and track the work around it.
Before we build, we agree which system owns each record. The integration then carries data between Harvest and monday.com, so nobody copies it by hand.
Nothing your team relies on has to be replaced.
We highly recommend Worktables. They took the time to listen to all of our challenges and created an integrated system to manage all aspects of our operations.
What stays the same
Harvest stays as it is
The integration connects to Harvest the way you use it today. It moves the data, and nothing you rely on has to change.
Each record lives once
We agree which system owns each record before we build, so there is one right copy, not two.
Data arrives on its own
When data needs to reach the other side, the integration carries it. No exports, no re-keying.
How we connect Harvest to monday.com
-
Scope
We agree which system owns each record, which events should move it, and which board it lands on.
-
Build the workflow
We build the workflow that carries data between Harvest and monday.com and logs every run.
-
Connect the board
We map each field to your columns, groups and statuses, and test on a copy of the board before it goes live.
-
Support
We watch it after launch, fix what breaks, and change it when your process changes.
Questions about connecting Harvest
Do we have to replace anything?
No. Harvest stays as it is, and so does monday.com. The integration carries data between them; it does not replace either one.
What if monday.com already offers an integration with Harvest?
Then we start from what it covers. Where it does the job, we build on it; where your process needs more, we build around it.
Can we test it before it goes live?
Yes. We test on a copy of your board before the integration touches the live one.
Who looks after it once it is running?
We do. We watch it after launch, fix what breaks, and change it when your process changes. Every run is logged, so there is a record of what moved and when.
Related in Productivity & Docs
See more in Productivity & DocsTell us what Harvest and monday.com should do together
Book a free call and walk us through your process. We'll tell you what the integration should do and how we'd build it.