What makes Justworks easy or hard to automate
Justworks is a PEO, which means it is co-employer of record for your team and runs payroll, benefits and compliance. That makes it a system you want to read from far more than write to. The good news is that Justworks now has a Partner API with OAuth 2.0 and scopes for company, member, payroll, paystub, time-off and deduction data. The catch is access: you request it from Justworks rather than generating a key yourself.
In practice that changes the order of work. We file the access request at the start, describe exactly what data the workflow needs, and build the non-API parts in parallel. If access is slow or the scopes you receive are narrower than hoped, the project still ships something useful.
Where direct access is not available, there are three fallbacks. Justworks’ native integrations cover common syncs. Unified HR API providers such as Finch connect to Justworks on your behalf. And scheduled report exports can feed a workflow that reads a CSV, which is less elegant but dependable.
The AI layer
Because Justworks handles the regulated work, AI adds the most in the space around it:
- Answering questions about your handbook and the benefits documents you choose to publish, so HR stops fielding the same ten questions.
- Explaining payroll changes in plain English after code has computed the differences by department and pay period.
- Preparing onboarding plans that are specific to role and location, and chasing the steps that stall.
Personal data stays the boundary. An assistant can explain your PTO policy to anyone; it should not tell one employee about another’s salary. OpenAI and Anthropic do not train on API data by default, but access control is still your job.
Limits to plan around
- Approval before access. No approval, no API. Put the request in the first week.
- Scope fit. You get the scopes Justworks grants. Design the workflow around the minimum you need so the request is easy to approve.
- Token refresh. Confirm how long Justworks’ access and refresh tokens last. A workflow that runs only monthly may need a scheduled refresh in between so it does not find its token expired.
- Read-mostly design. Payroll and benefits changes belong in Justworks’ own interface with a person approving them.
How Lumeor typically connects it
We start with n8n and the sources we can reach immediately: your ATS, a form, Slack and the reports you already export. Once Justworks approves API access, we swap the report step for an HTTP Request credential using OAuth. For teams outgrowing a PEO, we often compare against Gusto or Rippling. Rippling lets admins create their own scoped API tokens, while Gusto also restricts its API to approved partners, so check API access before you switch for that reason. The onboarding guide and HR policy assistant guide cover the two builds we see most. If you are not sure where to start, the AI readiness assessment ranks the options.