Skip to main content
Who can do this: Admins with the Company Settings Access permission connect and configure the integration. Users with the Hire Candidates permission create employees in your HR system when they hire.Availability: Your HR system needs to be on the supported list. If you don’t see it on the Integrations page, ask your Customer Success Manager.
Journeyfront connects to your human resources information system (HRIS) so hiring data moves without spreadsheets or copy and paste. You can create a new hire’s employee record in your HR system in one click, keep Journeyfront’s employee records in step with your HR system, and pick real HR records, like departments and work locations, in your custom fields. Journeyfront works with many HR systems, including Workday, BambooHR, ADP, Paylocity, Paychex and UKG, through one standard integration. Setup is the same whichever system you use.

What the integration does

Connect your HR system

Before you start, make sure you have:
  • Sign-in details for your HR system. Depending on the system, you may also need an API key or client secret. Your HRIS administrator can help.
  • The right access in your HR system. The account you connect with needs permission to create employee records and to read the data Journeyfront uses, such as locations and departments.
1

Find your HR system

Go to Settings, then Integrations. HR systems are listed under HRIS. Use Filter or Search to find yours quickly.
The Integrations page in Settings, with HR systems such as Workday, UKG Pro and BambooHR listed under HRIS, ATSs listed under ATS, and the Filter and Search boxes highlighted
2

Start the connection

Click your HR system’s tile, then click Connect to followed by its name.
An HR system's integration page, here UKG Pro, with an Inactive status and the Connect to UKG Pro button
3

Review permissions and sign in

A secure window lists the data Journeyfront is asking to access. Review it and continue. Then follow the steps for your HR system: sign in, or enter the key it asks for. A short guide at the bottom of the window explains where to find each value.
The secure connection window for Workday asking for the Workday REST API Endpoint, with the View Guide link for the connection guide highlighted at the bottom
4

Confirm the connection

When you see Connection set up successfully!, close the window. The tile now shows Active, and the Details tab shows who connected it and when.
Once connected, your HR system’s page in Integrations has these tabs:

Create employees when you hire

Turn on employee creation

1

Open Create Employee Settings

Go to Settings, then Integrations, open your HR system, and select the Create Employee Settings tab.
2

Turn it on

Turn on Enable Employee Creation and click Save. The Create Employee in option now appears in the hire window for your team.
3

Map your fields

Under Field Mappings, choose which Journeyfront field fills each field in your HR system. Add a Default Value for any field that should be filled in when the Journeyfront field is empty.
Two more settings appear once employee creation is on:
  • Pass JF Country Options and Pass JF State Options: if your HR system doesn’t supply its own country or state list, Journeyfront fills the dropdown from its own list. Turn these off if your HR system expects different codes; the field then becomes free text.
Set default values for fields your HR system requires but recruiters rarely know at the moment of hire, such as a standard work schedule. Recruiters then only fill in what’s different, and fewer sends stop on a missing field.

Send a new hire to your HR system

1

Hire the candidate

On the Candidate Application, click Actions, then Hire. In the hire window, make sure Create Employee in your HR system is checked (it’s checked for you when your HR system is connected), then complete the hire.
The Hire window for a candidate, with the HRIS Integration option Create Employee in UKG Pro checked
2

Review the mapped information

A window opens showing what Journeyfront filled in from the Candidate Application on the left, and your HR system’s fields on the right. Check the pre-filled values, such as name and email.
3

Fill in required fields

Fill in anything your HR system requires that Journeyfront doesn’t have, such as a start date, work location or manager. Required fields are marked with a red asterisk (*).
4

Attach documents and send

Choose any documents to include, such as the resume or signed offer letter, if your HR system accepts them. Then click Send.
The employee record is created in your HR system right away. Journeyfront records who sent it and when at the top of the Candidate Application and in Comments & Activities.
Some HR systems, such as ADP and Paychex, create the record as an in-progress or onboarding hire rather than an active employee. That’s decided by your HR system, not Journeyfront.
The Send to UKG Pro window, with fields mapped from Journeyfront filled in, the required Start Date still empty, and the resume and signed offer letter selected as attachments

Sync employees from your HR system

The employee sync brings your employees from your HR system into the Journeyfront Employees page on a schedule. It updates people who already exist in Journeyfront, adds new ones, and can mark their Candidate Applications as hired.

Set up the sync

Go to Settings, then Integrations, open your HR system, and select Employee Sync Settings. Click Save Configuration. Once the sync is on, the Field Mapping section appears below. Map the fields pulled from your HR system to Journeyfront fields, and choose Unknown Option Handling for dropdown fields: Auto-create adds a value that isn’t an option yet, and Skip leaves the field blank.
Pick an identifier both systems really share. If candidates apply with their personal email, Personal Email finds the most matches. Use Work Email only when work emails are reliably filled in your HR system, and Employee Number or Employee ID when Journeyfront already stores that number for your people.

Map job titles to job profiles

On the Job Profile Mapping tab, match each job title in your HR system to a Journeyfront job profile. Synced employees are assigned to that profile, and Auto-Mark as Hired uses it to find the right job req.
  • Match Strategy: use Job Title only for one profile per title. Use Job Title + Location or Job Title + Department when the same title maps to different profiles depending on where someone works.
  • Add Manual Mapping adds one mapping at a time. For many titles, click Download Template, fill it in, and use Import CSV.
Titles without a mapping are flagged when the sync runs.

Preview and review syncs

The Sync History tab lists every run with its date, status, who started it, and how many people were created, updated, unchanged or had errors. Click View to see the results of a run, or CSV to download them.
1

Preview first

Click Preview Sync to see what a sync would do without changing anything. A preview is required before your first sync.
2

Run the sync

When the preview looks right, click Run Sync Now and confirm. After that, the sync also runs on your schedule.
A sync can create, update and end employee records in Journeyfront based on your HR system’s data. Review a preview after any change to your matching, filters or mappings.

Pick HR records in custom fields (HRIS objects)

An HRIS Object custom field lets your team pick a record straight from your HR system, such as a work location, company, department, job code or employee, instead of typing its code by hand. The field keeps both the record’s name, so people can read it, and your HR system’s code for it, so your exports, offer letters and other systems get exactly what they expect. You can add HRIS Object fields to job reqs, hiring classes and offers. Candidates never see them; they aren’t available on application forms.

Create an HRIS Object field

1

Open the field settings

Go to Settings, then Custom Fields, then Job Req Fields or Hiring Class Fields. For offers, go to Settings, then Offers, then Offer Fields. Add a field.
2

Name it

Enter a Label, the name everyone sees on the form and as a column header, such as “Department”. The Key is suggested from the label. You can edit the key before you save, but not after.
3

Choose the list

Set Type to HRIS Object, then choose the HRIS Object list the field draws from. Lists are named the way your HR system names them, with a short description of each. If you picked a list of groups, set a Group Type to narrow it, for example so one field means Department and another means Division.
4

Check the preview and save

The Preview shows the real picker with your real records, so you can search it exactly as your team will. The Values row shows the two values the field produces and their merge fields. Click Save.
The Add Hiring Class Field window with Field Type set to HRIS Object and the HRIS Object list open, offering Location, Company, Group, Job and Employee
Name the field the way your business talks about it, like “Cost Center”, even if your HR system calls the list something else. And use the Preview before you save: it’s the quickest way to confirm you picked the right list when several sound alike.

Pick a value

Open the job req, hiring class or offer and click the field. A Recently used section shows the five records your team chose most recently for that field. To find anything else, start typing a name or a code; a full code matches exactly and comes first. The field shows the record’s name with its code beside it as a chip, so leading zeros like 0001 stay visible.
A Work Location field on the Create Hiring Class window, open to show a search box, a Recently used section and all results, each location with its code beside it
Records retired in your HR system don’t appear in the picker, so no one can choose one that no longer exists.

Use an HRIS Object field in offer letters

An HRIS Object offer field gives your templates two merge fields. Use the field’s key for the record’s name, for example {{WORK_LOCATION}}, and add _ID for your HR system’s code, for example {{WORK_LOCATION_ID}}. You can also set a default for the field on an offer package, so every offer from that package starts pre-filled.

Keep your lists up to date

Lists refresh automatically. Using the picker never calls your HR system; it reads what Journeyfront has already synced, so it stays fast and puts no load on your HR system. To pull a change right away, go to Settings, then Integrations, open your HR system, select the HRIS Objects tab and click Refresh now. The same tab shows every list, where it comes from, how many records it holds, whether a field uses it, and how the last sync went, including why a list couldn’t be read.
The HRIS Objects tab of an HR system integration, here UKG Pro, with the Refresh now button, when it last synced, each record type and chosen list with its record count, and whether a field uses it
When a record is renamed in your HR system, the new name shows everywhere on the next sync. When one is retired, it stops appearing for new selections, but every job req, hiring class and offer already using it keeps its name and code.

Connect a web service for lists your integration doesn’t cover

If a list you need isn’t part of the standard integration, or your HR system isn’t supported by it, you can connect to your HR system’s own web services. You’ll need details from whoever manages your HR system.
1

Open the HRIS web service card

Go to Settings, then Integrations, and open HRIS web service in the HRIS section.
2

Enter the connection details

Fill in HRIS, Web services host, Service account username, Service account password, Company API key and User API key. Your HR team creates the service account with read access to the lists you want.
3

Test and save

Click Test and save. Journeyfront signs in once to check the details, and the connection only turns on if that works.
4

Add your lists

For each list, give it a name your admins will see, the service to call, and which response fields hold the code and the display name. Your HR team provides these. Each list then appears as an HRIS Object option when you create a field.
The Add web service list window, with a list name, the operation to call, where the rows are in the response, and the code and name fields filled in
Credentials are stored encrypted and never shown again. You’ll see whether each one is set, not its value. A web service connection works with or without the standard integration.

Edit, archive or delete an HRIS Object field

Open the field’s menu on the settings page.
  • Edit: change the label and description at any time. The Key can’t change after the field is created, and the list can’t change once any record has a value for it. To use a different list, create a new field.
  • Archive: removes the field from forms but keeps every value already recorded. You can restore it later.
  • Delete: removes the field and its values permanently. Journeyfront shows how many records would be affected before you confirm.
Archive is almost always the better choice. It keeps your history and can be undone.

Disconnect your HR system

Go to Settings, then Integrations, open your HR system and click Disconnect on the Details tab. Employee records you already sent stay in your HR system, and data already synced into Journeyfront stays in Journeyfront. Disconnecting can’t be undone; to use the integration again, you connect from the start.

FAQ

Every supported HR system is listed under HRIS on the Integrations page, including Workday, BambooHR, ADP, Paylocity, Paychex, UKG and many more. If yours isn’t listed, ask your Customer Success Manager.
No. Each Journeyfront account connects to one HR system. To switch, disconnect the current one first.
First name, last name and email are mapped automatically. Your admins can map more fields and set defaults in Create Employee Settings. Depending on your HR system, the window may also ask for things like home address, start date, work location, department and manager. You can attach documents such as the resume and signed offer letter if your HR system accepts them.
No. Each send creates a new employee record in your HR system. Journeyfront shows a check mark once a candidate has been sent, so you don’t send them twice by accident.
It can. If the candidate was sent before, the hire window shows when, with a warning that sending again may create a second employee in your HR system. Check your HR system before you send.
Yes. When you hire several candidates at once, the bulk hire window includes a section for your HR system. Fill in shared values once, adjust any candidate individually, and Journeyfront creates each employee.
You’ll see an error explaining why, usually a missing required field or a connection problem. Fix it and send again. A failed attempt doesn’t create a partial record, and Journeyfront doesn’t retry on its own.
Usually the list hasn’t synced yet. Open the HRIS Objects tab on your integration to see when it last ran and whether anything went wrong. If a list couldn’t be read, the reason is shown there; often it’s a permission your service account needs in your HR system.
A multiple choice field is a list you type and maintain by hand, and its value is just the option’s label. An HRIS Object field gets its options from your HR system, stays current on its own, and carries your HR system’s code alongside the name.
Yes. Journeyfront connects through secure, authenticated APIs, and you approve exactly what it can access when you connect.

Integrations overview

Everything Journeyfront connects to.

Custom fields

Add your own fields to job reqs, hiring classes and applications.

Offer fields

Fields that fill in your offer letters.

Hiring classes

Group hires who share a start date.