Integrations are free to use within ApplicantStack but require an account and/or subscription directly from the individual partners.
Step 1: Create a Namely Personal Access Token:
Login to your Namely account and from the settings menu, next to your avatar, select "API" here:
Then from the "Personal Access Token" tab, name the new personal access token "ApplicantStack" and select "Create":
NOTE: You will be notified that you have one chance to copy the Personal Access Token.
Step 2: Setting up Namely Integration within ApplicantStack
Any Administrator can login to their ApplicantStack account and go to the Settings Menu and select "Setup":
Then from the Integrations menu scroll down to the "Payroll & HRIS" section and select "Activate" under Namely:
Add your Namely account name (The first part of your Namely URL) and the Namely Personal Access Token. Once the information has been added select "Save":
Then select "Configure" from the Settings menu followed by "Application Fields" here:
Select "Create Field" to add new fields:
Create a new filed called "Namely Start Date", set the Type to "Date" and choose "Save":
NOTE: The new field MUST be named "Namely Start Date" of type Date
Step 3: Pushing a Hired candidate's information to Namely
Once you move a candidate to the "Hired" stage, you will see the following Stage Change Confirmation menu:
NOTE: If you did not correctly name the filed in the previous step to "Namely Start Date", you will receive the following error message:
- The Namely Access Token is created in the Namely portal. That token is good for the entire account, and will be setup once by an admin of the Namely account. It is good for 2 years. After that, an error will be thrown in the candidate history that the candidate wasn’t moved to Namely, due to the access token being expired. Once that happens, a new Personal Access Token would need to be created in Namely, and updated in ApplicantStack. It’s created in Namely under API -> Personal Access Tokens. The access token is only displayed once when created, and if the user who created that token leaves/is removed from Namely, a new token needs to be created.