How do I configure field mappings for TempWorks?

Last updated: May 28, 2026

Field mappings tell Onboarded how to translate data from TempWorks into your Onboarded records. Each mapping connects a TempWorks field to an Onboarded field path — for example, employee.firstName in TempWorks to employee.firstName in Onboarded.

Before you start

  • Your TempWorks integration must already be connected. If you haven't done that yet, see How do I set up the TempWorks integration?

  • You need account-owner or admin permissions in Onboarded.

Default mappings

When you first connect TempWorks, Onboarded automatically creates a set of default field mappings covering the most common fields across all five entity types. These are marked Required by Integration and cannot be deleted — they're the minimum needed for the integration to function correctly.

You can add custom mappings on top of the defaults to pull in any additional fields you need.

Steps

Step 1 — Open the Configuration step

  1. Navigate to Account Settings → Integrations and click Configure next to TempWorks.

  2. Click through to Configuration (step 2 of the wizard). Field Mappings appear in the upper section of this step.

Step 2 — Add a field mapping

  1. Click New Mapping. A dialog opens with four fields.

  2. Choose a TempWorks Entity. Select which entity type this mapping is for: Employee, Job Order, Customer, Employer, or Assignment.

  3. Choose a TempWorks Field. Select the specific field from TempWorks you want to map. The available fields update based on the entity type you selected.

  4. Choose an Onboarded Field Path. Search for and select the Onboarded field that should receive the data. Field paths follow a dot-notation format like employee.phone or employer.ein. You can also map to custom attributes — for example, employee.custom_attributes.tempworks_branch. If you need a new custom attribute, click New custom attribute to create one.

  5. Choose a Scalar Type. Select the data type of the TempWorks field: string, integer, decimal, boolean, date, datetime, or address. This must match what TempWorks actually sends — a type mismatch will cause syncs to fail for that field.

  6. Click Create. The mapping is saved and takes effect on the next sync.

Each Onboarded field path can only have one mapping
You can't map two TempWorks fields to the same Onboarded field path. If you try, you'll see a "field mapping for path already exists" error. Edit the existing mapping instead.

Step 3 — Edit or remove a mapping

  1. To edit a mapping, click its row in the list. The entity, field, and scalar type cannot be changed after creation — delete it and recreate if you need to change those. You can update the Onboarded field path.

  2. To remove a mapping, open it and click Delete. Mappings marked Required by Integration cannot be deleted.

Available TempWorks fields

The fields available per entity type are:

  • Employee — employeeId, firstName, middleName, lastName, phoneNumber, emailAddress, address

  • Job Order — jobOrderId, jobTitle, address

  • Customer — customerId, customerName

  • Employer — employerId, employerName, legalName, federalEmployerIdentificationNumber, phoneNumber, address

  • Assignment — assignmentId, employeeId, customerId, employerId

When changes take effect

New and updated mappings take effect on the next sync event — you don't need to restart the sync. Records that synced before the mapping was added won't be retroactively updated. To apply a new mapping to already-synced records, run a full sync again from the Configuration step.

Troubleshooting

A sync record shows a field error. Go to Integrations → TempWorks and check the Error Message column. It will show which field failed and what value was rejected. Common causes: wrong scalar type selected (e.g., mapping a field as integer when TempWorks sends a string), or an address with a country code Onboarded doesn't recognize. Fix the mapping and re-run the sync.

"A field mapping for path already exists" error. You're trying to map two TempWorks fields to the same Onboarded path. Find the existing mapping for that path in the list and either edit it or delete it first.

A required mapping is missing from the list. Default mappings are created automatically when you first connect TempWorks. If they're missing, contact your Onboarded contact — this may indicate the configuration needs to be re-initialized.

Related