Gusto
Gusto is in beta in Ploy. Ploy scans your Gusto company's employees, contractors, company admins and departments, and can add people and manage department membership. The integration is built from Gusto's published API and has not yet been run against a live Gusto company, so we ask for your consent before connecting (step 1 below).
What Ploy reads
Every employee of the Gusto company you connect, including people still onboarding and people who have been terminated.
Every contractor, individual or business, including dismissed contractors.
Every company admin. Admins have full access to payroll, benefits and every employee record, so they are shown with the Company admin access level. Employees and contractors are shown with self-service access.
Each department and who is in it.
HR details for employees and contractors who have a work email: name, department, job title, manager, start date and end date.
Terminated employees and dismissed contractors are shown as blocked and lose their access in Ploy. An admin removed in Gusto loses their access in Ploy at the next scan.
What Ploy can change
Add a person: as an employee, who then completes their own onboarding in Gusto, or as a company admin.
Remove a person: only employees who have not finished onboarding. Gusto does not let other apps delete onboarded employees, contractors or admins, so terminate or dismiss them in Gusto.
Departments: add people to and remove people from a department.
Ploy never terminates employees or dismisses contractors, because those run payroll.
Before you start
You need a Gusto developer application authorized for your company, with its client ID and client secret, and a current access token and refresh token for the company.
To scan, the application needs the scopes employees:read, contractors:read, company_admin:read and departments:read. To add people and manage departments it also needs employees:manage, company_admin:write and departments:write. Gusto's Technical Solutions team changes an application's scopes.
You need your company's UUID.
Step 1: Agree to the beta terms
The first page of the Gusto setup in Ploy has a required consent checkbox. Because the integration is in beta, ticking it lets Ploy record redacted error data when a Gusto request fails: the error status and message with any personal data, tokens and secrets removed. We use it only to fix the integration quickly. You cannot continue without ticking it.
Step 2: Enter the connection details
In Ploy, open Integrations, find Gusto and start the setup.
Tick the beta consent checkbox.
Choose the environment: Production for your live company, or Demo for a company in Gusto's demo environment.
Enter the company UUID.
Paste the application's Client ID and Client secret.
Paste the company's Access token and Refresh token.
Ploy renews the tokens itself from then on. Each renewal retires the previous refresh token, so use this token pair only for Ploy. If another tool renews the same pair, the connection stops working and you need to paste a new pair.
Step 3: Test the connection
Ploy tests the connection by reading one employee with the access token you pasted. If the test fails:
"Gusto rejected the access token": generate a fresh token pair for the company and paste both tokens again.
"Gusto refused to list employees": the application is missing the employees:read scope. Ask Gusto's Technical Solutions team to add it.
"Gusto could not find that company": check the company UUID, and that it belongs to the environment you chose.
What to expect
The first scan runs shortly after setup and then every six hours. People appear in Ploy with their Gusto access level: Employee, Contractor or Company admin. Someone who is both an employee and an admin appears twice, once for each. People still onboarding are shown as not yet signed in.
Not included yet: multi-factor authentication, last sign-in times, and removing someone's admin access, which is done in Gusto.