Skip to main content

Adding a Checkr action to a journey

R
Written by Riya Sebastian
Updated over 3 weeks ago

Using journeys, HR, IT, and other teams can maintain a checklist of tasks, communication, and automated actions around key employee moments like onboarding, offboarding, promotions, learning, or compliance in one place.

For example, you could set up an onboarding journey to ship a new hire swag, ask their manager to assign them a buddy, and order a Checkr background check. Without Atomicwork, this might have had to involve a member of your team logging into Checkr and ordering a candidate report manually.

With Atomicwork, you can add it as a journey action to an onboarding journey.

Adding a Checkr action to a journey

  1. Connect Checkr to Atomicwork.

  2. Navigate to the journey you want to create this action in

  3. Click on Add an action > Order a Checkr background check

  4. Enter the employee's information for whom you want to run the background check.

    • Tip: You can use dynamic placeholders to make this action completely automated. For example, if you enter ##{{employee.first_name}} in the “First name” field and ##{{employee.last_name}}, Atomicwork will order a background check for “Katherine Johnson” when you assign the journey to Katherine Johnson.

    • If you’d like to also add an employee’s work location as a dynamic placeholder, we’d recommend you add them as People fields and import the data so you can use country/state/city as placeholders.

  5. Choose the Checkr package you want to order. You can only order one package at a time, so please set up multiple actions if you want to order multiple checks like previous employment verification or education verification done.

  6. Checkr actions are automated actions that do not need to be manually ordered by an HR or IT manager. So, you only need to specify when you want the action to be executed.

    1. Your two options are the day the employee moves to the stage or a day relative to the day an employee moves to this stage.

  7. Last but not least, give the Checkr action a name that is easy to understand so your teammates know why you’ve set it up. Checkr actions will be visible to journey collaborators but not to employees who have been assigned this journey.

  8. Click “Add” to add the action to your journey.

Best practices and tips:

  1. If you have different onboarding journeys for different locations, you can just enter the same work location for all employees in a journey and just use a dynamic placeholder for the employee’s personal data

Did this answer your question?