Employee fields Onboarded writes back to TempWorks

Last updated: September 25, 2026

The fields Onboarded pushes to TempWorks Beyond on its own, with no automation from you. Anything not on this list needs a custom automation.

What's covered

This lists the employee data Onboarded writes to TempWorks Beyond automatically when onboarding tasks complete. It does not cover what TempWorks sends to Onboarded — see 📄 What data syncs between TempWorks and Onboarded? for the inbound direction.

The Field Mappings screen doesn't control this list. The mappings you edit under your TempWorks configuration govern what Onboarded ingests from TempWorks. The write back below is fixed — adding a row there won't push a new field to Beyond.

Fields written automatically

Field

Where it lands in Beyond

Notes

First name

Employee record

Written on create and on every later update.

Last name

Employee record

Written on create and on every later update.

Middle name

Employee record

Update only — see the callout below.

Address

Employee address

Required to create the employee at all. An address Onboarded can't validate stops creation.

Email address

Primary email contact method

—

Phone number

Primary phone contact method

US, Canada and UK numbers only.

Social Security Number

Government personal ID

Needs a country resolved from the address. No valid address, no SSN push.

Date of birth

EEO record

—

Branch

Employee record

Set at creation. Without a branch, the employee can't be created.

Middle name is sent on updates but not when Onboarded first creates the employee record in Beyond. On a brand-new employee it stays empty until the next push. If middle name has to be present from the start, plan for the second push or set it in TempWorks.

Everything else needs an automation

Driver's license number is the one people ask about most, and it's the clearest example of the rule: if a field isn't in the table above, nothing carries it to Beyond on its own.

To push one, build an automation with an HTTP Request action pointed at the TempWorks proxy. The proxy handles authentication with your account's existing TempWorks credentials, so you're not managing a second set of keys. 📄 How do I log a message on a TempWorks employee record from an automation? walks through that shape end to end — the same pattern applies to any Beyond endpoint.

What triggers a push

The writeback isn't on a schedule. It runs when:

  • A task's status changes — this pushes the employee record.

  • A placement is created — this pushes the employee record and kicks off onboarding actions.

  • A form's PDF is generated or skipped — this pushes the document.

Related