Harvest Make integrationAutomate Harvest with Make.

Setting a new billable rate in Harvest no longer takes a manual edit: this module writes the rate for you from data your scenario already holds.

A signed deal elsewhere turns into a Harvest client without retyping the company name. The client is then ready to receive projects, contacts and invoices from later modules.

People who receive your invoices or answer your questions get their own record under the right Harvest client, filled from a form or your CRM instead of by hand.

Your scenario creates a Harvest invoice directly, which suits fixed fees and one-off charges that never went through a timesheet. Make passes the new invoice on so the next module can add lines or notify someone.

Receipts and costs captured elsewhere land in Harvest as expenses, attached to the right project, so they can be billed back or tracked against the budget.

A payment that reached you through your bank or your payment processor gets recorded on the matching Harvest invoice, so Harvest holds the same payment record as your bank.

This is the module that saves the most clicks at kickoff: the project appears in Harvest under its client, ready for people to log time the same day.

New kinds of work, say a fresh service line, get added to your Harvest task list from the scenario, which keeps the list consistent with the catalog you maintain elsewhere.

This module attaches an existing task to a project for you, so nobody has to open the project settings to add it.

Hours recorded outside Harvest, in a calendar, a ticket tool or a form, end up in the timesheet without a second round of typing.

New hires and freelancers get their Harvest account opened by the scenario, at the same moment as their other tools, which keeps onboarding in one flow.

Adding a line to an invoice that already exists lets you build the bill piece by piece: one line per deliverable, per fee or per expense your scenario finds.

Removing a client from Harvest from your scenario helps keep test data or duplicates out of your reports once another tool confirms they should go.

When someone leaves a client company, their contact can disappear from Harvest at the same time as from your CRM, so invoices stop going to an old address.

An expense cancelled or refused elsewhere is taken out of Harvest too, which stops it from being billed back to the client by accident.

Draft invoices created by a scenario during testing, or duplicates from a double run, can be wiped from Harvest without clicking through them one by one.

Closing a project for good can be automated, but this module goes further than it looks: along with the project, Harvest removes every time entry and expense tracked to it. Invoices tied to the project stay.

Retired services or old task names drop off your Harvest task list when the scenario says so, leaving people a shorter, clearer list to pick from.

Hours logged by mistake, or copied twice by a scenario, come out of the timesheet so they do not end up on an invoice.

Offboarding can close the Harvest account along with the rest, but only for people who never tracked anything: Harvest refuses to delete a user who has time entries or expenses.

One wrong line comes off an invoice while the rest of it stays untouched, which beats rebuilding the whole bill.

Keeping a client's details the same in Harvest and in your CRM stops being a chore: a change made on one side gets written on the other by the scenario.

A new phone number or email for someone at a client lands on their Harvest contact without a trip into the client page.

Corrections to a cost already in Harvest, a fixed amount or a better note, get applied from the scenario so the record stays accurate before billing.

An invoice that already exists in Harvest gets updated by the scenario, useful when a detail changes between the draft and the moment it goes out.

Project settings in Harvest follow what happens in your other tools: a renamed deal, a new scope, a project that moves to another client.

Renaming or adjusting a task in Harvest from the scenario keeps the task list aligned with the catalog your team maintains elsewhere.

Fixing hours after the fact, moving an entry to the right project or correcting its note, happens from the scenario instead of asking each person to redo it.

Profile changes decided elsewhere, a new role or a name correction, get written onto the person's Harvest account by the scenario.

One line of an invoice gets corrected, its description or amount, while every other line stays as it was.

The full record of one Harvest client comes back into your scenario, ready to be mapped into a document, an email or another app.

Everything Harvest knows about one contact is fetched in a single step, so a later module can address them correctly.

One expense and its details come into the scenario, handy to check a cost before approving, copying or billing it.

The current version of one Harvest invoice is read into the scenario, which is the safe way to check its state before doing anything else with it.

A single project's details arrive in your scenario, so later steps can use its name, its client or its settings without a separate lookup in Harvest.

Pulling one task from Harvest gives the scenario its full details, useful when an entry only carries a reference to the task.

One link between a task and a project is read in detail, so you can see how that task is set up inside that particular project.

One time entry comes back with its details, so the scenario can check it before editing, copying or deleting it.

The profile of one person on your Harvest account comes back into the scenario, ready to fill a welcome email or an HR record.

One link between a person and a project is read in detail, which tells your scenario how that person is set up on that project.

This module lets your scenario ask Harvest for things the other modules do not cover, using the Harvest connection you already created, so there is nothing new to authorize.

Your Harvest client list comes into the scenario, one bundle (one item passed to the next module) per client, ready to copy into a spreadsheet or a CRM.

The people saved under your Harvest clients come back as separate bundles, which gives you a clean source for a mailing list or an address book in another tool.

With the expenses recorded in Harvest in hand, the scenario can total them, file them or send them to your accounting side without anyone exporting a file by hand.

Your Harvest invoices arrive in Make as a list, which is the starting point for reminders, dashboards or a sync with your bookkeeping app.

Every payment recorded against one invoice shows up here, so you can tell whether a client paid in full or in several parts before you chase anyone.

The budget reports of your Harvest projects land in the scenario, so you can see how far each one has drawn on its budget and push that picture to a team channel or a sheet.

Each Harvest project comes out as its own bundle, handy for mirroring them into a planning board or checking that every project has a matching folder elsewhere.

You see which tasks are attached to which projects, so you can audit how your projects are set up.

You get the catalog of tasks defined in your Harvest account, the kinds of work people choose when they track time, such as design or meetings.

The hours logged in Harvest arrive one bundle per time entry, which is the raw material for timesheets, client reports or payroll exports built outside Harvest.

You see who is assigned to which project, so you can check that the right people can track time where they should before work starts.

The people in your Harvest account come back as separate bundles, useful to keep an HR sheet or a directory in another app aligned with who actually tracks time.