Harvest
Connect Harvest to Ploy to see every user in your Harvest account, the permission level each one holds, who has been archived, and which projects each person is assigned to. Ploy can also add users, change a user's permission level, archive and restore users, remove users, and assign users to projects or remove them.
This integration is in beta
The Harvest integration is in beta. It was built from Harvest's documented API v2 and has not yet been run against a live Harvest account, so some behaviour may differ from what is described here until it has.
The first step of setup is a consent checkbox. Ticking it lets Ploy send redacted error data to its own monitoring when a call to Harvest fails. Redacted means secrets, tokens and personal details are removed before anything is stored. Ploy uses it only to fix problems with the integration. You need to tick it to continue.
What Ploy reads
Every user in the connected Harvest account, with their name, email address and permission level. On accounts that use access roles, that is Administrator, Manager or Member, plus any extra capabilities a Manager holds (such as Project creator or Billable rates manager). On accounts that use permissions profiles, it is the profile name, including custom profiles your administrators created.
Archived users, shown as no longer having access.
The Harvest account itself, so several Harvest accounts connected to one Ploy organisation stay separate.
Every project that has assigned users, and who is assigned to it. Project managers are marked as such.
Harvest's descriptive roles (labels such as Designer) do not change what anyone can do, so they are not shown as access. Harvest does not report when a user last signed in, so last activity is not shown.
What Ploy can change
Add a user with their first name, last name and email address. Harvest sends them its own invitation email. You can choose a permission level: an access role (Administrator, Manager or Member) on accounts that use access roles, or a permissions profile on accounts that use profiles. Choose one or the other, not both. With neither, Harvest makes the person a Member. Adding someone who is already a user counts as done. If the address belongs to an archived user, Ploy asks you to restore them instead.
Change a user's permission level. Ploy uses the permission model the user is already on. A custom permissions profile must already exist in Harvest.
Archive a user and restore an archived user. Archiving keeps the person's time and expense history.
Remove a user. Harvest only deletes users who have never tracked time or expenses. For anyone else, Ploy archives them instead, which removes their access the same way. Removing someone who is already gone counts as done.
Assign a user to a project or remove them from it, from the project's page in Ploy. If Harvest keeps an assignment because it has time entries, Ploy deactivates it instead.
Before you start
You need a Harvest personal access token created by a Harvest Administrator. Ploy acts with that person's permissions, so it must be an Administrator to see every user and to make changes.
Sign in to Harvest as an Administrator.
Open the Developers page of your Harvest ID at id.getharvest.com/developers.
Create a personal access token and copy it.
Connect Harvest
In Ploy, open Integrations and choose Harvest.
Tick the beta consent checkbox.
Paste the personal access token and continue.
Select the Harvest account to scan. The list shows every Harvest account the token can reach.
Select Test to check the connection. Ploy reads the account's users to confirm it works.
Save the connection. The first scan starts straight away.
To connect another Harvest account, add another Harvest connection.
Troubleshooting
The account list is empty: Harvest did not return any accounts for that token. Go back and check the token was copied in full.
Harvest rejected the token: create a new personal access token and paste it in full.
That token cannot list users in this account: the person who created the token must be a Harvest Administrator in the account you selected.
Harvest refused the change: Harvest's own reason is shown with the error. A common one is a permissions profile name that does not exist in the account.