Upsert Worker Custom Object Data

Upsert Worker Custom Object Data

Read a worker's custom object data and create or update it via the upsert endpoint.

1. Retrieve the custom object definition to confirm the target custom object type exists before reading or writing instance data.
2. Retrieve the worker's current custom object data. A 200 indicates existing data; a 404 indicates none exists yet. Both outcomes are accepted so the flow can branch on the result.
3. Update the worker's existing custom object data with the supplied values. Returns 200 when the instance already existed.
4. Create new custom object data on the worker using the supplied values. Returns 201 when the instance did not previously exist.

What you'll need to have ready

• definitionId: The unique identifier of the custom object definition to validate against.
• workerId: The unique Workday identifier of the worker.
• customObjectName: The name of the custom object type.
• data: Custom object field values keyed by field API name.

For your developer

Arazzo workflow workday-extend:upsert-worker-custom-object, 4 operations: getCustomObjectDefinition → getWorkerCustomObject → updateWorkerCustomObject → updateWorkerCustomObject. Specs on APIs.io.