TempWorks placement names

Last updated: September 25, 2026

Every placement the TempWorks integration creates is named after the flow that created it. Scope a policy rule on placement.name and you control which onboarding an employee gets — a job board applicant, a walk-in, or someone whose hire status just changed.

What's covered

This lists every value the TempWorks integration writes to placement.name, and the flow that produces each one. It doesn't cover how to build the rule itself — see 📄 How do I build a policy? for that.

placement.name is a system property on the placement, stored as a string. It's available on every account, so you don't need to create it.

The names

Value	Written when	Worth knowing
`Assignment`	An assignment syncs in from TempWorks.	Comes from the assignment sync, not from anything the employee does. This trigger is always on.
`Candidacy`	An employee applies through a job-apply link that carries one or more job orders — the usual job board path.	A posting listing several job orders creates one placement per order on the same registration, each named `Candidacy`.
`General Application`	An employee applies through a job-apply link with no job order on it.	The careers-page, social and kiosk path. The employee picks a branch first, and you get a single placement.
`Hire Status (status)`	An employee's hire status in TempWorks changes to one you've selected on the hire-status placement trigger.	The status is appended in parentheses — for example `Hire Status (Active)`. When the status name isn't available, the raw status code lands there instead.
`Candidate Status (status)`	An employee's status against a specific job order changes to one you've selected on the job-order candidate-status trigger.	Also parenthesised. Because the webhook carries the order, the placement resolves to a job and a customer.

Using a name in a policy rule

Point the rule's fact at placement.name and match the value.

equal for one flow — placement.name equal Candidacy assigns the packet only to job board applicants.
in to cover several — placement.name in Candidacy, General Application gives one policy every applicant, however they arrived.
contains for a family of statuses — placement.name contains Hire Status catches every hire-status placement regardless of which status fired it.

An equal match against Hire Status never fires. Hire-status and candidate-status placements always carry the status in parentheses, so the stored value is Hire Status (Active), never Hire Status. Use contains for the whole family, or equal against the full value including the parentheses.