AdaptivMapr

HR & People

The templates in this pack

Employee master records with identity, contact, and bank details. Contains PII.

The templates in this pack

Schema

The canonical field set, printed as it ships.

8 fields with multilingual hints (DE / FR / IT / EN / ES) and field-level validators. Any source column that resolves to one of these is mapped by the cascade — most of them on the deterministic layers, with no LLM call.

employees_v1
fields
8
required
2
validated
3
hints
39
Canonical columnTypeRequiredValidatorsHeader hints the cascade matches
employee_idstringyes—personalnummermatriculematricolaemployee idnúmero de empleado
legal_namestringyes—namenomnomelegal namenombre
emailemail—emailemaile-mailmailcorreocourriel
national_idstring—regexausweisnummerahvnuméro nationalcodice fiscalenational iddni
ibanstring—ibanibancomptekontobank account
hire_datedate——eintrittsdatumdate d'embauchedata di assunzionehire datefecha de contratación
departmentstring——abteilungdépartementdipartimentodepartmentdepartamento
statusenumactiveterminatedon_leave——statusstatutstatoestado

Read the same definition as JSON at GET /v1/templates/employees_v1. A hint match resolves on layer 2 — no LLM call, no token spend, just the flat per-map fee. Hover a validator id to see what it checks.

  • 8 canonical fields
  • 2 required
  • 3 validated
  • 39 header hints
  • HR & People pack

Try it

A real file, a real call, one template id.

6 rows, synthetic AHV/IBAN, DE headers. Fully synthetic — safe to share, commit, and run in CI.

bash
curl -X POST https://api.adaptivmapr.com/v1/uploads \
  -H "Authorization: Bearer $ADAPTIVMAPR_API_KEY" \
  -F "file=@employees_sample.csv" \
  -F "template=employees_v1"
→ upload created · mappings ready · confirm before commit
This is a high-risk template. Its mappings response comes back with requires_hitl: true so you can gate your own commit. Schema-only mode — headers plus at most three sample rows, each clamped to 80 characters — is a data-minimization mode. Full-data routes the metered layer-5 call in-region under a BAA at a 20% uplift, and stays locked until the workspace accepts the BAA/NDA in-app.
mcp
adaptivmapr.match_headers({
  template_id: "employees_v1",
  headers: ["employee_id", "legal_name", "email", "national_id"]
})
schema-only · headers and ≤3 clamped rows only

Put employees in production — without shipping raw records.

Schema-only mapping leaves only headers and a handful of clamped samples. Add full-data when you need row-level AI, routed in-region under a BAA.