---
title: Integrating with Gem
slug: integrating-with-gem
icon: 💎
docTags: 
createdAt: 2025-08-18T17:32:40.181Z
---

This guide covers:

::::VerticalSplit{layout="middle"}
:::VerticalSplitItem
- [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)
:::

:::VerticalSplitItem
- [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

1. Navigate to **Settings -> ATS Integration** and **select Gem&#x20;**&#x66;rom the list.
2. Click **"Continue"**&#x20;

::Image[]{src="https://api.archbee.com/api/optimize/JtqPsvk-s0xQ7dgMBVpor/vVlTT2GoElGrx3QtLZ9rJ_image.png" size="60" isUploading="false" width="632" height="1126" darkWidth="632" darkHeight="1126" showCaption="false"}

3. Enter your **Gem API Key&#x20;**&#x61;nd click **"Continue"**

::Image[]{src="https://api.archbee.com/api/optimize/JtqPsvk-s0xQ7dgMBVpor/qXhxByQuL9CuZQULpPNnZ_image.png" size="60" isUploading="false" width="636" height="1132" darkWidth="636" darkHeight="1132" showCaption="false" indent="1"}

4. Add **"Pin.com"&#x20;**&#x61;s the source name

::Image[]{src="https://api.archbee.com/api/optimize/JtqPsvk-s0xQ7dgMBVpor/EiPf1G6kAcH-gm_zJasVo_image.png" size="60" isUploading="false" width="637" height="1134" darkWidth="637" darkHeight="1134" showCaption="false"}

5. Follow the steps to locate the **tracking URL** and paste it in the field

::Image[]{src="https://api.archbee.com/api/optimize/JtqPsvk-s0xQ7dgMBVpor/apKs6kbW5k5LZfmQdrX3t_image.png" size="60" isUploading="false" width="640" height="1136" darkWidth="640" darkHeight="1136" showCaption="false"}

6. Choose a&#x6E;**&#x20;admin user&#x20;**&#x77;ho will be used to perform actions in Gem and then click **"Set up integration"**

::Image[]{src="https://api.archbee.com/api/optimize/JtqPsvk-s0xQ7dgMBVpor/rET4lAS84kqVUhRGezraY_image.png" size="60" isUploading="false" width="639" height="1135" darkWidth="639" darkHeight="1135" showCaption="false"}

***

# Syncing candidates to Gem

To sync candidates from each job in Pin to a specific job in Gem:&#x20;

1. Go to **Job Settings -> Position Details**.
2. Scroll to the **ATS Integration&#x20;**&#x73;ection.
3. Choose when to sync candidates by selecting one of the following triggers:
   - Never
   - Contact information is found
   - They receive their first message
   - They reply to an email
   - They reply to an email and are interested
4. Select 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.

![](https://api.archbee.com/api/optimize/JtqPsvk-s0xQ7dgMBVpor/XACm6V7M6CvrWWVyP2qXY_cleanshot-2026-09-08-at-141707-2x.png)

:::hint{type="warning"}
**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.

![](https://api.archbee.com/api/optimize/JtqPsvk-s0xQ7dgMBVpor/3KK1TaqHumbB4hEjcMVPG_cleanshot-2026-09-09-at-105424-2x.png)

***

# Manually syncing a candidate to Gem

If the candidate hasn’t synced yet:

1. Select the candidate in Pin.
2. Click **“Export to ATS”**.&#x20;
3. Choose the Gem job you want to sync the candidate to, the&#x6E;**&#x20;click “Export”&#x20;**&#x74;o complete the sync.
4. After exporting, refresh the page, and you should now see the Gem logo appear on their profile.

![](https://api.archbee.com/api/optimize/JtqPsvk-s0xQ7dgMBVpor/7T5h-SiwTWWUo-OeCifPK_cleanshot-2026-09-09-at-113145-2x.png)

:::hint{type="warning"}
**Important:**&#x20;

- 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&#x20;**&#x6F;nly 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:

1. Full name
2. Email
3. Phone number (this will not sync over if the candidate's phone number is found after they synced over to Gem)
4. LinkedIn profile URL
5. Current role
6. A Pin generated resume PDF
7. If the candidate was sourced from Pin
8. Which team member sourced the candidate

:::hint{type="info"}
**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.&#x20;

![](https://api.archbee.com/api/optimize/JtqPsvk-s0xQ7dgMBVpor/rpkHJMmkETFYj88idyMi0_image.png)

