Integrating with Gem

this guide covers connecting gem to pin https //docs pin com/integrating with gem#connecting gem to pin syncing candidates to gem https //docs pin com/integrating with gem#syncing candidates to gem when candidates sync to gem https //docs pin com/integrating with gem#when candidates sync to gem checking if a candidate synced to gem https //docs pin com/integrating with gem#checking if a candidate synced to gem manually syncing a candidate to gem https //docs pin com/integrating with gem#manually syncing a candidate to gem candidate data synced to gem https //docs pin com/integrating with gem#candidate data synced to gem how pin checks for duplicates in gem https //docs pin com/integrating with gem#how pin checks for duplicates in gem source candidates from gem https //docs pin com/integrating with gem#source candidates from gem connecting gem to pin navigate to settings > ats integration and select gem from the list click "continue" enter your gem api key and click "continue" add "pin com" as the source name follow the steps to locate the tracking url and paste it in the field choose an admin user who will be used to perform actions in gem and then click "set up integration" syncing candidates to gem to sync candidates from each job in pin to a specific job in gem go to job settings > position details scroll to the ats integration section c hoose when to sync candidates by selecting one of the following triggers never contact information is found they receive their first message t hey reply to an email they reply to an email and are interested s elect the gem job you want to sync candidates to candidates will sync from pin to the matching job in gem pin does not sync candidates to a specific stage in gem once you've selected your preferred trigger, pin will automatically update the settings and sync candidates to the selected job in gem based on the chosen trigger reminder you’ll need to set up the syncing for each job you want to send from pin to gem in the position details tab within the job settings 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 gem once the selected trigger occurs, candidates will sync to gem within a few minutes for example if you choose the trigger “export candidates when contact information is found”, the candidate will automatically sync to gem a few minutes after being added to outreach checking if a candidate synced to gem to confirm if a candidate has synced to gem, you can open their profile in pin if you see the gem logo, this means that they’ve been successfully synced clicking the logo will take you directly to their profile in gem manually syncing a candidate to gem if the candidate hasn’t synced yet select the candidate in pin click “export to ats” choose the gem 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 gem logo appear on their profile important once a candidate has synced to gem, their contact information cannot be re synced if some information did not sync, you’ll need to manually update that candidate’s profile in gem the "export to ats" button only works for candidates who haven’t already synced to gem 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 gem the following candidate data will sync to gem from pin full name email phone number (this will not sync over if the candidate's phone number is found after they synced over to gem) linkedin profile url current role a pin generated resume pdf if the candidate was sourced from pin which team member sourced the candidate note candidates can only sync from pin to the matching job in gem pin does not sync candidates to a specific stage in gem moving them further in gem's pipeline will need to be manually updated on gem's side how pin checks for duplicates in gem pin runs a check before syncing whenever a candidate is added to outreach to prevent duplicate profiles for gem, 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 gem source candidates from gem after connecting gem to pin, you can use the “ats candidates” filter to include or exclude candidates from your ats when searching for candidates