List of Fields Sent to HiBob
When you send a candidate to HiBob from Pinpoint, we send a small set of standard HiBob employee fields (the ones you can review and edit in the Send to Bob form) plus a large set of HiBob custom fields carrying almost all of the candidate's Job, Application, Offer and Onboarding data.
The custom field list is generated automatically from the data Pinpoint holds, so it grows as new fields are added to Pinpoint. The tables below reflect the current list.
The full custom field list applies to the Data Mapping workflow, which is used by all HiBob integrations set up on or after 1 September 2023. Integrations set up before that date use the original HiBob workflow, which sends only the standard fields listed in Fields you can edit in the Send to Bob form plus a single Birth date custom field.
Fields you can edit in the Send to Bob form
These fields are pre-filled from Pinpoint and can be changed before you send the candidate. They map to standard HiBob employee fields.
Form field | Where it goes in HiBob | Pre-filled from |
First name (required) |
| Application first name |
Last name (required) |
| Application last name |
Email (required) |
| Application email |
Mobile Phone |
| Application phone number |
Job Title |
| Job title |
Department |
| Job department |
Location (Site) |
| Job location |
Employment Contract |
| Job employment type |
Salary |
| Accepted offer salary, or the job's minimum compensation |
Currency |
| Accepted offer currency, or the job's compensation currency |
Payment Period |
| Mapped from the accepted offer's salary duration |
Payment Frequency | Custom field Payment Frequency | Mapped from the job's compensation frequency |
Reports to |
| Accepted offer manager's email, or the job's hiring manager email |
LinkedIn Url |
| Application LinkedIn URL |
Candidate start date |
| Application start date, or today's date |
Documents |
| Nothing selected by default |
Job Title, Department and Location (Site) must match the names used in your HiBob account exactly, otherwise HiBob will reject the value.
Documents lists everything Pinpoint holds for the candidate - files submitted with the application, their CV, background check reports, the signed offer letter, application answer attachments and onboarding documents. Each selected file is sent to HiBob as a name and a download link.
How Payment Period and Payment Frequency are mapped
HiBob only accepts its own preset values, so Pinpoint translates them. If a Pinpoint value has no HiBob equivalent, the field is left blank for you to choose.
Offer salary duration in Pinpoint | Payment Period in HiBob |
1 hour | Hourly |
1 day | Daily |
1 week | Weekly |
2 weeks | Monthly |
1 month | Monthly |
1 year | Annual |
Job compensation frequency in Pinpoint | Payment Frequency in HiBob |
--- | --- |
Per hour | Pro rata |
Per day | Pro rata |
Per week | Weekly |
Every two weeks | Every two weeks |
Per month | Monthly |
Per year | Monthly |
Custom fields sent automatically
Everything below is sent to HiBob as a custom field. You cannot edit these values in the Send to Bob form - they are taken from the candidate's record at the moment you send them.
Job fields
Field name in HiBob | Pinpoint data | HiBob field type |
Job - Uuid | Job's unique Pinpoint reference | Text |
Job - Title | Job title | Text |
Job - Description | Job description | Text |
Job - Compensation | Compensation summary shown on the job advert | Text |
Job - Compensation currency | Currency of the job's compensation | Text |
Job - Compensation frequency | How often the compensation is paid | Text |
Job - Compensation minimum | Bottom of the compensation range | Text |
Job - Compensation maximum | Top of the compensation range | Text |
Job - Employment type | Employment type (e.g. Permanent, Contract) | Text |
Job - Experience level | Experience level | Text |
Job - Workplace type | Workplace type (e.g. On-site, Hybrid, Remote) | Text |
Job - Remote | Whether the job is remote | Yes/No |
Job - Is remote with location restrictions | Whether a remote job is restricted to certain locations | Yes/No |
Job - Custom town | Custom town on the job's location | Text |
Job - Custom county | Custom county on the job's location | Text |
Job - Custom country | Custom country on the job's location | Text |
Job - Reporting to | Who the role reports to, as written on the job | Text |
Job - Benefits | Benefits listed on the job | Text |
Job - Company name override | Company name shown on the advert, if overridden | Text |
Job - Division | The job's division | Text |
Job - Structure custom group one | The job's custom structure group | Text |
Job - Structure link names | Names of the job's organisation structure levels | Text |
Job - Cover letter requirement | Whether a cover letter is required, optional or hidden | Text |
Job - Ask for middle name | Whether applicants are asked for a middle name | Yes/No |
Job - Ask for preferred name | Whether applicants are asked for a preferred name | Yes/No |
Job - Linked in premium posting | Whether the job was promoted on LinkedIn | Yes/No |
Job - Access through visibility | Whether access to the job is controlled by its visibility settings | Yes/No |
Job - Hold at | When the job was put on hold | Timestamp |
Job - Total hold time seconds | Total time the job spent on hold, in seconds | Number |
Job - Division is only sent if your account uses divisions, and Job - Structure custom group one is only sent if your organisation structure includes a custom group.
Application fields
Field name in HiBob | Pinpoint data | HiBob field type |
Application - Uuid | Application's unique Pinpoint reference | Text |
Application - First name | Candidate's first name | Text |
Application - Middle name | Candidate's middle name | Text |
Application - Last name | Candidate's last name | Text |
Application - Preferred pronouns | Candidate's preferred pronouns | Text |
Application - Email | Candidate's email address | Text |
Application - Phone | Candidate's phone number | Text |
Application - Phone iso2 | Country code of the candidate's phone number | Text |
Application - Date of birth | Candidate's date of birth | Date |
Application - Address1 | First line of the candidate's address | Text |
Application - Address2 | Second line of the candidate's address | Text |
Application - Town | Candidate's town or city | Text |
Application - Postcode | Candidate's postcode | Text |
Application - Country | Candidate's country | Text |
Application - Linkedin url | Candidate's LinkedIn profile URL | Text |
Application - Summary | Candidate's personal summary | Text |
Application - Cover letter text | Cover letter the candidate typed into the application | Text |
Application - Locale | Language the candidate applied in | Text |
Application - Channel | Where the application came from (e.g. a job board) | Text |
Application - Channel source | More detail on the application's source | Text |
Application - Ccuid | Candidate's identifier from the source job board, where one is provided | Text |
Application - Internal candidate | Whether the candidate is an internal applicant | Yes/No |
Application - Recruiter | Whether the application was submitted by an external recruiter | Yes/No |
Application - Request copy | Whether the candidate asked for a copy of their application | Yes/No |
Application - Start on | Candidate's start date | Date |
Application - Hired at | When the candidate was moved to Hired | Timestamp |
Application - Furthest stage at | When the candidate reached their furthest stage | Timestamp |
Application - Exported at | When the application was last exported to an external system | Timestamp |
Application - Stage lane position | The candidate's position in their current stage lane | Number |
Offer fields
These are taken from the candidate's accepted offer. If the candidate has no accepted offer, none of them are sent.
Field name in HiBob | Pinpoint data | HiBob field type |
Offer - Job title | Job title on the offer | Text |
Offer - Manager | Email address of the offer's manager | Text |
Offer - Salary amount | Offered salary | Text |
Offer - Salary currency | Currency of the offered salary | Text |
Offer - Salary duration | Period the salary covers (e.g. 1 year) | Text |
Offer - Paid days off | Paid time off included in the offer | Text |
Offer - Work address | Work address on the offer | Text |
Offer - Start at | Start date and time on the offer | Timestamp |
Offer - Start on | Start date on the offer | Date |
Offer - Result | Outcome of the offer | Text |
Offer - Result at | When the offer was accepted or declined | Timestamp |
Offer - Sent at | When the offer was sent | Timestamp |
Offer - Expires at | When the offer expires | Timestamp |
Offer - Expiration notification sent | Whether an expiry reminder was sent | Yes/No |
Offer - Comment | Internal comment on the offer | Text |
Offer - Signature type | How the offer was signed | Text |
Offer - Bulk offer uuid | Reference for the bulk offer the offer belongs to | Text |
Offer - Email subject | Subject line of the offer email | Text |
Offer - Email salutation | Salutation of the offer email | Text |
Offer - Email body | Body of the offer email | Text |
Offer - Email signature | Signature of the offer email | Text |
Offer - Letter subject | Subject of the offer letter | Text |
Offer - Letter body | Body of the offer letter | Text |
Offer - Letter signature | Signature on the offer letter | Text |
Offer - Additional letter text | Additional text added to the offer letter | Text |
Offer - Original correspondence | Original offer correspondence, as first sent | Text |
Your own custom fields
Any custom field you have created in Pinpoint against a Job, an Application or an Offer is also sent, as long as it hasn't been deleted. It arrives in HiBob named <Your field name> - Job, <Your field name> - Application or <Your field name> - Offer.
These custom field types are sent:
Pinpoint custom field type | HiBob field type |
Text (Short) | Text |
Text (Long) | Text |
Select | Text |
Multi Select | Text (values separated by commas) |
Number (Integer) | Number |
Number (Decimal) | Text |
Date | Date |
Yes / No | Yes/No |
Custom fields of type Users and Criteria Checklist are not sent.
Onboarding answers
When you send a candidate to HiBob from the Onboarding module, their onboarding answers are sent too, each named Onboarding Answer - <question title>.
These onboarding question types are sent:
Onboarding question type | HiBob field type |
Short Text | Text |
Long Text | Text |
URL | Text |
Date | Date |
Yes / No | Yes/No |
Checkbox | Yes/No |
Multiple Choice | Text (values separated by commas) |
Document, Unique Attachment, Image, Document Template, eSignature Document Template, DocuSign and HelloSign question types are not sent as answers. You can still send the files themselves by selecting them in the Documents picker on the Send to Bob form.
Getting newly added fields into HiBob
The field list is generated fresh every time you send someone, so a new custom field, a new onboarding question, or a new field released by Pinpoint is picked up automatically - there is nothing to change in your integration settings.
To get new fields onto HiBob's mapping screen without waiting for a real candidate, re-send the demo user: open your HiBob integration settings in Pinpoint and click Send to Bob in the Send demo user to Bob card. Pinpoint sends the complete current field list with example values, so every field - including the new ones - arrives in HiBob ready to be mapped.
A few things to check first:
The demo candidate email shown in that card must be set as the demo candidate in your HiBob Hire API settings.
Onboarding answer fields are only included if Onboarding is enabled on your account.
New onboarding questions must be saved to your question bank before they will be sent.
Good to know
Empty fields are left out. Any field with no value is dropped from the data we send, so HiBob only receives the fields the candidate actually has. A Yes/No field set to No still counts as a value and is sent.
Data is a snapshot. Everything is read at the moment you press Send to Bob. Later changes in Pinpoint are not pushed to HiBob.
