Use API and Zapier to get your Harvest data into Float

Justyna Kawalec avatar
Written by Justyna Kawalec
Updated over a week ago

Although we currently do not have a way to integrate your Float account with Harvest directly, you can use the API and Zapier to transfer your Harvest data into Float. To do it, you'd need active accounts at Float, Harvest, and Zapier, and access to the API key.

To set up a Zap, you first need to map the corresponding fields between the two systems - for each field that needs to be transferred from Harvest to Float, you need to map the corresponding fields or IDs. For example, if you're transferring "Task Name" from Harvest to "Task Name" in Float, these fields should be mapped accordingly. This requires working with the API on both systems to extract the required IDs and complete Zapier's mapping table.

Once all the fields are mapped, you can create the automation following the steps below:

  1. In Zapier click +Create Zap.

  2. Trigger App: Choose the app that will trigger the integration. This would be Harvest in your case. Select the specific trigger event, such as "New Time Entry."

  3. Connect Harvest Account: Follow the prompts to connect your Harvest account to Zapier. You might need to provide API keys or other authentication details.

  4. Configure Trigger: Set up the trigger event according to your needs. This could involve specifying filters, time frames, or other criteria for when the trigger should activate.

  5. Action App: Choose the app where the action will take place. This will be Float in your case.

  6. Connect Float Account: Follow the prompts to connect your Float account to Zapier. Similar to Harvest, this could involve providing API keys or authentication.

  7. Configure Action: Define the action you want to happen in Float when the trigger from Harvest occurs. This might involve creating a new task, project, or resource allocation in Float based on the information from Harvest.

  8. Test and Turn On: After configuring both the trigger and action, run a test to ensure the integration works as expected. If the test is successful, you can turn on the Zap to start the integration.

Did this answer your question?