Integrating with Ashby

this guide covers creating an api key https //docs pin com/integrating with ashby#6cfes connecting ashby to pin https //docs pin com/integrating with ashby#48mr1 syncing candidates to ashby https //docs pin com/integrating with ashby#zuuo3 when candidates sync to ashby https //docs pin com/integrating with ashby#hc4fl checking if a candidate synced to ashby https //docs pin com/integrating with ashby#wucu3 manually syncing a candidate to ashby https //docs pin com/integrating with ashby#eahwx candidate data synced to ashby https //docs pin com/integrating with ashby#uexfu how pin checks for duplicates in ashby https //docs pin com/integrating with ashby#qh17m creating an api key to connect pin with ashby, you’ll first need to create an api key in ashby you can follow ashby’s guide for step by step instructions on generating an api key when creating the api key, make sure it includes the following endpoint permissions required by pin jobs read candidates read & write organization read api keys read connecting ashby to pin navigate to settings > ats integration and select ashby from the list enter your ashby api key in the api key field after entering your api key, the integration will be connected syncing candidates to ashby to sync candidates from each job in pin to a specific job in ashby go to the automation tab in pin scroll to the "export candidates to ats" section select the ashby job you want to sync candidates to next, choose when to sync candidates by selecting one of the following triggers when they're added to an outreach sequence when they reply to an email when they reply to an email and are interested once you've selected your preferred trigger, click “enable” to save your settings pin will now automatically sync candidates to the selected job in ashby based on the chosen trigger note you’ll need to set up the syncing for each job you want to send from pin to ashby in the automation tab we recommend setting up the job sync before adding candidates to outreach this ensures candidates sync correctly to the job without issues if you prefer not to sync candidates to a job, you can still set up a trigger and leave the job field empty when candidates sync to ashby once the selected trigger occurs, candidates will sync to ashby within a few minutes for example if you choose the trigger “export candidates when they're added to an outreach sequence”, the candidate will automatically sync to ashby a few minutes after being added to outreach checking if a candidate synced to ashby to confirm if a candidate has synced to ashby, you can open their profile in pin if you see the ashby logo, this means that they’ve been successfully synced clicking the logo will take you directly to their profile in ashby manually syncing a candidate to ashby if the candidate hasn’t synced yet select the candidate in pin click “export to ats” choose the ashby job you want to sync the candidate to, then click “export” to complete the sync after exporting, refresh the page, and you should now see the ashby logo appear on their profile important once a candidate has synced to ashby, their contact information cannot be re synced if some information did not sync, you’ll need to manually update that candidate’s profile in ashby the "export to ats" button only works for candidates who haven’t already synced to ashby if an integration was connected after the selected trigger, pin won’t retroactively sync those candidates in that case, use the "export to ats" button to sync them over candidate data synced to ashby the following candidate data will sync to ashby from pin full name email phone number linkedin profile url location (city, state, country) current and previous roles education a pin generated resume pdf if the candidate was sourced from pin which team member sourced the candidate note all candidates will automatically sync into ashby as leads how pin checks for duplicates in ashby pin prevents duplicate candidate profiles by running a check before syncing for ashby, duplicates are checked against email address linkedin url if a match is found on either field, pin will not create a new candidate profile in recruiterflow