How do we perform custom data mappings when our fields do not match Harriet's defaults?

Map vendor-specific HRIS or webhook fields to Harriet so syncs and automations use the right attributes.

Your HRIS may use different field names or custom attributes than Harriet expects by default. Custom field mapping aligns the two sides so employee data and events behave correctly.

When you need it

Standard sync leaves important attributes blank or wrong in Harriet.
You use custom columns or non-standard objects in your HR system.
Webhooks or other integrations send payloads whose keys do not match Harriet’s expected shape.

What to do

In Company settings, open the relevant integration and look for field mapping or advanced mapping options (labels vary by integration).
Map each source field from your system to the Harriet attribute it should populate.
After saving, run a test sync or wait for the next scheduled sync and spot-check a few records.

Example

Your HRIS stores “Worker ID” in a custom attribute. You map it to Harriet’s employee identifier field so tickets and workflows reference the same ID as your payroll export.

Guardrails

Wrong mappings can overwrite good data—take a backup or export before large remaps if your process requires it.
Document the mapping in your internal runbook so the next admin knows why a custom field exists.