What data syncs between TempWorks and Onboarded?
Last updated: May 28, 2026
This article explains which entity types sync between TempWorks and Onboarded, what direction data flows, and what triggers each sync.
Sync direction overview
The TempWorks integration is primarily one-directional: TempWorks is the system of record for workforce data, and Onboarded pulls that data in to drive onboarding. Onboarded pushes a smaller set of data back to TempWorks — completed forms as documents, task status as onboarding actions, and employee profile updates collected during onboarding.
Data that syncs from TempWorks into Onboarded
Employee → Onboarded Employee
Core identity fields: first name, middle name, last name, phone number, email address, and address. The TempWorks employee ID and branch ID are stored as custom attributes so they can be referenced in field mappings and onboarding actions.
Customer → Onboarded Client
Customer name and customer ID. Onboarded creates or updates a Client record to match.
Job Order → Onboarded Job
Job title and work site address. The TempWorks job order ID is stored as a custom attribute. If the work site address isn't included in the webhook, Onboarded fetches it separately from the TempWorks API.
Employer → Onboarded Employer
Employer name, legal name, federal EIN, phone number, and address. Employer records are typically created as a side effect of syncing an assignment — Onboarded fetches the full employer details from TempWorks as part of that process.
Assignment → Onboarded Placement
An assignment ties an employee to a customer, job order, and employer. When Onboarded syncs an assignment, it chains through all four entities — syncing the employee, client, job, and employer if they haven't been synced yet — then creates a Placement record that links them together.
Data that Onboarded pushes to TempWorks
Onboarding Actions (Tasks)
Every task created, updated, or deleted in Onboarded is pushed to TempWorks as an Onboarding Action. This gives TempWorks a live view of onboarding progress — form names, completion status, due dates, and progress — without requiring anyone to log into Onboarded separately.
Completed form PDFs
When an employee completes a form that has a document mapping configured, Onboarded uploads the completed PDF to the employee's TempWorks profile under the mapped document type. See How do I set up document mappings for TempWorks? for setup details.
Employee profile updates
When an employee updates their name, address, phone, or email through an Onboarded form, those changes are pushed back to their TempWorks employee record. This keeps TempWorks in sync when employees provide corrected or more complete information during onboarding.
What field mappings control
Field mappings determine exactly which TempWorks fields map to which Onboarded field paths. Default mappings are created automatically when you connect TempWorks and cover the standard fields for all five entity types. You can add custom mappings to pull in additional fields — for example, mapping a TempWorks custom field to an Onboarded custom attribute. See How do I configure field mappings for TempWorks? for details.
What triggers syncs
Initial sync: Started manually from the Configuration wizard. Pulls all employees, customers, job orders, employers, and assignments in bulk. Sync time depends on the size of the account.
Real-time webhooks (after initial sync): TempWorks pushes change events to Onboarded as they happen — new employees, updated job orders, new assignments, and so on. Onboarded processes these in the background, so records in Onboarded stay current without manual intervention.
Outbound events (Onboarded → TempWorks): Task and form events in Onboarded trigger near-real-time pushes to TempWorks. These run as background jobs and retry automatically on failure.