What is nullable?
On the integration mapping step, some vendor fields support a nullable toggle:
Nullable (allowed empty): You may send the field, but some employees can have blank values. The vendor accepts blanks (for example, optional
middle_name).Required (not nullable): Every record must have a value for that field before Aragorn AI sends data.
Hovering the control explains: when marked solid/required, field values cannot be empty if you provide a mapping.
Example: middle name
Carta accepts middle_name but understands not everyone has one.
Map
middle_nameand leave it nullable.Employees with a middle name send it; employees without send blank—Carta continues processing.
If your organization requires middle names for every employee:
Toggle the field to required.
Aragorn AI validates before contacting Carta.
If any employee lacks middle_name, the job fails with a validation error (for example, middle name is missing).
Vendor default vs your override
Vendors may mark a field as optional by default. You can override stricter rules in your organization by marking a field required—even when the vendor would accept blanks.