Integrations

Connect PrismHR or TempWorks

WagePilot connects to PrismHR and TempWorks through their APIs, with access that your company grants. Neither has a sign-up for outside software: access comes from your own account, and you can change or remove it at any time. WagePilot only reads from these systems.

Last updated October 15, 2026

What the connection is used for

  • Payroll review. WagePilot reads each client's pay data, matches it to your projects and checks it against prevailing-wage rules.
  • Timesheet intake. When a client sends timesheets (email tables, Excel, Word, PDFs or photos), WagePilot matches each name to an employee in your payroll system. You review the lines and download an import file for PrismHR or TempWorks.
  • WagePilot does not create timecards or change payroll in either system. People on your team import and approve the file there.

PrismHR

A PrismHR administrator at your PEO does this in PrismHR.

  1. Create a web service user for WagePilot under Back Office > System > Change > System Parameters > Actions > Web Service Users. PrismHR recommends a separate user for each integration.
  2. Under Allowed Methods, add:
    • ClientMasterService.getClientList and PayrollService.getPayrollVouchers#NODIRECTDEPOSIT for payroll review;
    • EmployeeService.getEmployeeList and EmployeeService.getEmployee to match timesheet names to employees.
  3. Under Company Access, choose the clients whose payroll or timesheets WagePilot should see.
  4. Under Allowed IPs, add WagePilot's outbound IP addresses (see below).
  5. In WagePilot, an owner or admin opens Integrations, chooses PrismHR, and enters the user name and password, your PEO ID and your PrismHR API address. Test connection checks the sign-in, the clients the user can see and access to payroll.

WagePilot never asks for unmasked Social Security numbers, and it drops any that appear in a response before storing anything.

TempWorks

TempWorks issues API credentials to its Enterprise customers, for their own database, so the request comes from your company.

  1. Ask your TempWorks account manager for API access for WagePilot.
  2. Ask for a service client (client ID, client secret, tenant and PID) that can read customers, employees and assignments (scopes customer-read and employee-read). Your account SID and auth token also work.
  3. Give TempWorks WagePilot's outbound IP addresses for your allow list (see below).
  4. In WagePilot, an owner or admin opens Integrations, chooses TempWorks, enters the credentials and runs Test connection.

WagePilot's IP addresses

PrismHR and TempWorks usually accept API calls only from approved IP addresses. Email hello@wagepilot.ai for WagePilot's current list. We tell you before it changes.

Link your clients

After the connection test passes, link each WagePilot client to the matching client in PrismHR or TempWorks. Payroll review and timesheet matching use that link. A client that isn't linked can still have timesheets read, but names are not matched to employee IDs and only a CSV export is available.

Timesheets by email

Each client can have its own WagePilot email address, created on the Timesheets page. Forward a client's timesheet email to it, attachments and all, and it becomes a batch to review. WagePilot accepts email from members of your organization and from senders you allow for that client, such as @client.com, and checks that the sender is genuine.

Entering hours directly: not available yet

Today WagePilot produces an import file. Entering timecards straight into TempWorks or PrismHR would need write access: in TempWorks, a staff user with time-entry and payroll permissions; in PrismHR, the timesheet upload methods. If you would like to pilot it, email hello@wagepilot.ai.

All integrations