Integrations
Plays well with the tools you already use.
Keep JobAdder or Bullhorn, and your payroll. Workhr connects to them, runs the live part of every job in between, and answers to your AI.
13live connectorsNZ + AUpayroll
Your stack, connected.
Workhr sits alongside the systems your desk runs on today, and each one keeps working. Moving records over from somewhere else? See how your data comes across.
Recruitment, CRM and sales
Where candidates, clients and placements already live.
Payroll and finance
Approved hours out to pay runs and invoices.
AI
The model behind Workhr AI, and the assistant you already use.
Workplace
The email, calendar, chat, sign-in and recorder your team already uses.
Site safety
PPE and inductions sorted before anyone turns up.
One shift, from placement to pay run.
Your ATS places. Your payroll pays. Workhr runs the live part in between, so every approved hour reaches the pay run and the invoice without anyone typing it twice.
- STEP 1
Place
Your consultant places the worker in JobAdder or Bullhorn, exactly as they do today.
Your ATS - STEP 2
Deploy and roster
The placement lands as an assignment. Workhr rosters the shift and confirms the worker.
Workhr - STEP 3
Sign in on site
The worker taps in and out on site, GPS-stamped, with breaks and allowances on the shift.
Worker app - STEP 4
Approve
The site supervisor approves the timesheet before anything reaches payroll.
Client portal - STEP 5
Pay and bill
Pay lines and the client invoice come from the same approved hours, at the rate on the day.
Astute, Xero, iPayroll or Crystal
One approved timesheet. Pay and bill are both derived from it, so the hours a worker is paid for and the hours a client is billed for always agree.
Workhr talks to your AI.
Connect Claude or ChatGPT once through the Workhr MCP connector, then ask your business anything. Answers come from your live Workhr data, read-only and scoped to what you’re allowed to see.
- Runs as you. Every question runs as the signed-in user, with that person’s access and nothing more.
- Read-only. Your assistant can look things up. It can’t change a record.
- Audited. Everything is logged, and tenants stay isolated from each other.
ClaudeChatGPTor any MCP-capable assistantClaudeWorkhr connectedWhich sites are short this Saturday?
Workhr · read shifts for Sat 17 Oct read-only
- Hornby DC: 5 of 8 pickers confirmed, 3 short
- Rolleston subdivision: 1 labourer unfilled
Before you connect anything.
Anything else, ask us on a demo. We’ll show you how your own stack fits, on your own data.
What do Live, Available and On the roadmap mean?
Live is a connector that runs today. Available means it works end to end today in another way: as an import that recognises the vendor's export, a finished connector, a file your payroll clerk imports, or through the MCP connector. On the roadmap means it's planned and has no connector yet, so we don't describe it as working.
Do we have to stop using JobAdder or Bullhorn?
No. JobAdder or Bullhorn stays your ATS and your consultants keep placing in it. Workhr picks up at the placement and runs deployment, site sign-in, timesheets and pay and bill, with the placement as the source of truth for who is on assignment.
Does Workhr replace our payroll?
No. Astute, Xero, iPayroll, Crystal or MYOB IMS keeps running pay. Workhr captures the hours on site, gets them approved, and sends them through with the pay and charge rate that applied on the day each shift was worked.
Our tool isn't listed. Can we still bring our data across?
Usually, yes. The import engine recognises common vendor exports by their columns and maps the rest field by field, with a preview before anything is written. See how your data comes across.
What can our AI assistant see?
Only what the signed-in person is allowed to see. The MCP connector is read-only, each question runs as that user, and every question is audited.
Bring your stack. We’ll meet it.
Tell us what you run today and we’ll show you how it fits, on your own data.