The NaturalHR integration lets you export candidate and new hire data from Pinpoint (both ATS and Onboarding) directly into NaturalHR, creating an employee record without retyping information.
Please be aware that NaturalHR was acquired by Moorepay, so you may see either brand name referenced; they are currently used interchangeably.
Setting up the integration
Step 1:
Contact your CSM and ask them to enable the integration for you.
Step 2:
Once the integration is enabled, in your Pinpoint platform, go to Integrations → My Plugins.
Step 3.
Find NaturalHR and click it.
Step 4.
Go to any application in Pinpoint and, from the three-dots menu on the right-hand side, pick "Send to NaturalHR". If the form loads correctly and you can see options in dropdowns, the connection is set up correctly.
Step 5.
Save
Step 6.
Ask your CSM for support with data mapping so you can define the data source for each field the integration sends to Natural HR. Pinpoint team will set up the mapping for you. We can also hide any optional fields from the form if you don't want to use them.
How it works
A user selects Send to NaturalHR from a candidate's application or onboarding profile (or as a stage action).
A form appears, pre-filled where mappings exist, with additional fields shown for optional features.
The user completes any missing details.
On submit, NaturalHR creates the employee record.
If enabled, NaturalHR automatically creates a holiday allowance and/or a user login account.
Pinpoint shows a success or error message based on the outcome.
Outcomes:
Full success — employee, holiday allowance, and user account all created.
Partial success — employee created, but the allowance and/or user account failed. These have to be added manually in NaturalHR.
Complete failure — employee creation itself failed, so nothing was created.
Common support issue: If the employee record is created but the holiday allowance or user account request fails, Pinpoint still reports the export as a success (with a note appended). This is the most frequent "it said it worked but nothing happened" ticket for this integration.
Two optional features
Both are off by default and configured independently in plugin settings:
Enable Holiday Allowance Creation — automatically creates a time-off allowance for the new employee. Adds required fields for allowance type and value.
Enable User Account Creation — automatically creates a NaturalHR login for the new employee, with a system-generated password. Adds required fields for login email and user group.
If either feature fails, the employee record is still created successfully. Only the failed piece needs manual completion in NaturalHR.
Field mapping
Fields on the export form come from one of three places: a Pinpoint field mapping (Liquid template, configurable per company), a dropdown pulled live from NaturalHR, or free text typed by the recruiter.
Only four fields are pre-filled out of the box: First Name, Last Name, Email, and Start Date. Everything else, including Title, Gender, both address lines, Town, County, Country, Postcode, Phone, and Mobile, arrives blank by default, even though NaturalHR ships default mappings. This is because those default mappings reference merge tags that don't exist in Pinpoint's vocabulary, so they render empty. We recommend reviewing and correcting these mappings during setup rather than assuming the defaults work.
One field can never be pre-filled at all: Manager is sent to NaturalHR but isn't in the mappable list, so it always has to be picked by hand.
Tip: Hiding a field using the whitelist (see below) stops it from appearing on the form, but does not stop it from being sent if it already has a value.
Data sent to NaturalHR
Each export can trigger up to three API calls, always in this order:
Create employee (always runs)
Create holiday allowance (only if enabled, and only if NaturalHR returned an employee ID)
Create user account (only if enabled, and only if NaturalHR returned an employee ID)
Only the first call can fail the whole export. The other two are best-effort and aren't retried or rolled back. Required fields to complete an export: First Name, Last Name, Email, Date of Birth, National Insurance Number, Job Update Date, FTE flag, Active flag, Salary Date, and Allowances Date. Holiday allowance and user account fields become required only when those features are switched on.
A few field quirks worth knowing:
Date of Birth, Salary Date, and Job Update Date are free-text boxes, not date pickers — they must be entered as
YYYY-MM-DDor NaturalHR will reject them.National Insurance Number must be unique in NaturalHR. Since Pinpoint doesn't track whether someone has already been exported, re-exporting the same person will fail on this field — that's the usual sign of an accidental duplicate.
Hours Per Week is rounded to a whole number, so half-hour contracts lose precision.
Data Pinpoint reads from NaturalHR
Pinpoint reads live reference data to populate dropdowns (jobs, departments, cost centres, sites, managers, business units, job statuses, and allowance types). There are no webhooks and no polling — nothing about a leaver, status change, or profile update ever flows back into Pinpoint.
Two things to be aware of:
Dropdown lists are cached for up to an hour, so a newly added job role or site in NaturalHR may take a little while to appear in Pinpoint. Re-saving the plugin refreshes the cache sooner.
Every list except Managers is capped at 500 entries. If you have more than 500 job roles, departments, cost centres, sites, business units, or job statuses, the dropdown will be silently truncated with no warning.
Once an export succeeds, Pinpoint doesn't store the NaturalHR employee ID anywhere, so it shows it once in the success message and then discards it. This is also why there's no built-in warning if a candidate has already been exported.
Troubleshooting
Symptom | Likely cause |
"API Key Error" callout | No API key entered, or key is invalid |
"Your read-only API key is not valid" | Optional read-only key is set but incorrect |
Job/department/site dropdown is empty | Underlying NaturalHR list call failed (bad key or outage) — this fails silently rather than showing an error |
"The national insurance number must be unique" | This person has likely already been exported |
Date rejected with a format error | Date wasn't entered as |
"Employee created, but holiday allowance/user account creation failed" | The employee record was still created — complete the missing piece manually in NaturalHR |