Gem integration
Alfa AI screens every applicant to your jobs, then sends the candidates you choose to the matching Gem job, with their resume.
Last verified
What works with Gem
| What you can do | With Gem |
|---|---|
| Link Alfa jobs to Gem jobs | Yes |
| Choose a Gem stage for each Alfa status | Yes |
| Send candidates to Gem | Yes |
| Attach each candidate's resume | Yes |
| Put shortlisted and sourced candidates straight into their mapped stage | YesApplicants marked Suitable or Not suitable go where Gem puts new applications |
| Add the score and screening results as notes | No |
| Move a candidate you shortlist later to your shortlist stage | Yes |
| Search your Gem history with Lisa | Yes |
Not confirmed means we have not yet confirmed whether this works with Gem through the integration Alfa uses.
What Alfa writes back to Gem
- Applicants. When screening finishes, Alfa sends each applicant whose status you map to a Gem stage, with their name, email address and, where Alfa has them, phone number and LinkedIn profile. Their resume goes with them.
- Notes. Gem does not accept notes through this integration, so the score and screening results stay in Alfa.
- Stages. Candidates you have already shortlisted when Alfa sends them go to the stage you map for Shortlisted. Applicants marked Suitable or Not suitable go where Gem puts new applications: mapping their status to a stage tells Alfa to send them to the linked job, but does not place them in that stage. When a job has its own pipeline, Alfa uses the stage with the same name in that job.
- Later changes. If you shortlist a candidate after Alfa has sent them, Alfa moves them to your Shortlisted stage in Gem.
- Applicants you do not sync. In Alfa's ATS settings you can choose a Gem job for applicants who are not synced. Alfa then adds applicants whose status is set to Don't sync to that job, where Gem puts new applications, so you keep them in Gem. Only applicants who apply after you choose the job are added. If you later shortlist one of them and Shortlisted is mapped to a stage, Alfa also sends them to the job they applied for.
- Sourced candidates. If you map Sourced potential candidates to a stage, Alfa also sends sourced candidates who have an email address, in that stage. Rejected and removed candidates are not sent, and sending them does not start any outreach.
What Alfa reads from Gem
- Open jobs. Alfa lists your open Gem jobs, up to the 250 most recently opened, so you can link each Alfa job to its Gem job.
- Pipeline stages. Alfa reads your Gem stages so you can choose where each Alfa status goes.
- Your hiring history. If you turn on Search your ATS history, Alfa copies the candidates and applications in Gem, with their resumes, so you and Lisa can search everyone you have considered before. The first copy can take a few hours.
How to connect Gem
- Open Settings. Sign in as an Owner or Admin on a computer, select your name at the bottom of the sidebar, then Settings.
- Go to ATS integrations. Under Workspace, select ATS integrations.
- Choose Gem. Open Select your ATS, pick Gem, then select Connect Gem.
- Approve access. A secure connection page opens in a new tab. Sign in to Gem there, approve the access it asks for, then return to Alfa.
- Wait for the first sync. The first import usually takes a few minutes. When it finishes, the status reads Connected.
- Map your stages. Under Stage mapping configuration, pick a stage for each Alfa status, or choose Don't sync to keep it in Alfa. Then select Save ATS settings.
- Link your jobs. In a draft job's Basics, open Advanced and choose the matching job under ATS job. You can also ask Lisa to link a job, including one that is already published.
Limits
- Your organization connects one ATS at a time.
- Only Owners and Admins on a paid plan can connect an ATS, on a computer. The integration is not available during a trial.
- Alfa sends each candidate to a job once, after screening finishes, and checks for new candidates every 20 minutes.
- Alfa only sends candidates who have a valid email address.
- Rejecting a candidate in Alfa does not change their stage in Gem.
- If Gem reports that a linked job is closed or no longer accepts candidates, Alfa unlinks the job and stops sending candidates to it.
- Moving or rejecting a candidate in Gem does not change their status in Alfa.
Frequently asked questions
- Does Alfa AI integrate with Gem?
- Yes. An Owner or Admin connects Gem in Settings > ATS integrations. You then link each Alfa job to its Gem job, and Alfa sends the candidates you choose after screening.
- What does Alfa send to Gem?
- The candidates whose status you map to a Gem stage, with their resume. If you choose a job for applicants who are not synced, Alfa also adds applicants whose status is set to Don't sync to that job. Alfa sends each candidate to a job once, after screening finishes.
- Can Alfa move candidates between stages in Gem?
- Yes, in one case: if you shortlist a candidate after Alfa has sent them, Alfa moves them to your Shortlisted stage. Other changes, such as rejecting a candidate in Alfa, are not sent to Gem.
- Can I keep applicants I do not sync in Gem?
- Yes. In Alfa's ATS settings, choose a Gem job under Job for applicants who are not synced. Alfa then adds applicants whose status is set to Don't sync to that job, so you keep them in Gem. Only applicants who apply after you choose the job are added.
- Can I search my Gem history in Alfa?
- Yes. Turn on Search your ATS history in Settings > ATS integrations. Alfa copies the candidates and applications in Gem, with their resumes, and you and Lisa can then search them. The first copy can take a few hours.
- Does connecting Gem email candidates?
- No. Connecting Gem does not email anyone, and sending sourced candidates to your ATS does not start any outreach.
- What happens if the Gem connection stops working?
- Alfa emails your company's Owners and Admins when the connection expires, or when Gem turns down candidates because the connection is missing a permission. The email has a button to reconnect or to open your ATS settings.

