Paychex
HR Client id and secretRead payroll, worker and company data from Paychex in any Windmill script, flow or app.
Set up in 3 steps
Register an application
At developer.paychex.com, register an application for your account. Paychex issues a client id and secret once it is approved.
Add the resource in Windmill
Open Resources, add a resource of type paychex, and fill client_id and client_secret.
Run your first script
Fork any script below and read before writing anything. There are dozens here, so search by the verb you need.
Scripts
Building blocks, if none of the projects above fit. Fork one, run it, or call it as a step inside your own flow.
Worker Time Off
Worker Statuses
Worker State Tax
Worker Profile Image
Worker Pay Standards
Worker Pay Rates
Worker Pay Rate
Worker Pay Components
Worker Pay Component
Worker I9 Status
Worker Federal Tax
Worker Documents
Worker Document
Worker Direct Deposits
Worker Direct Deposit
Worker Custom Fields
Worker Custom Field
Worker CustomField
Worker Contacts
Worker Contact
Worker Compensation
Worker Communications
Worker Communication
Worker Checks
Worker Check
Worker Assignments
Worker
Webhook
Request Client Access
Pay Component to a check.
Resource type
paychex — the shape of the credential every script on this page expects.
| Field | Type | Required | What it is |
|---|---|---|---|
| client_id | string | Yes | OAuth client ID |
| client_secret | string | Yes | OAuth client secret |
Questions
Why a pair and not a token?
The scripts exchange these two for a short-lived token on each run, so nothing expires in the resource and there is nothing to rotate by hand.
This reads payroll data
It does. Keep the resource in a folder only the right people can read, and give the application the narrowest access Paychex will grant it.
Are my credentials stored on the hub?
Never. They live only in your own Windmill workspace, encrypted at rest.