Help Center · Integrations
Zapier Recipe: PlacementFlow to Atlas
Create or update Atlas people and file a screening note when a candidate is shortlisted, using the PlacementFlow Zapier app and a Code by Zapier step that calls Atlas's API.
8 min readOn this page
This recipe puts shortlisted candidates into Atlas (the recruitment CRM at recruitwithatlas.com). For each shortlist it:
- creates the person in Atlas, or finds the one that already exists
- files a note with the screening outcome
- optionally adds the person to an Atlas project
- writes the Atlas id back to PlacementFlow
Atlas has no Zapier app of its own, so the Atlas side runs in a Code by Zapier (JavaScript) step that calls Atlas's API with your own Atlas API key. PlacementFlow never calls Atlas: the Zap does, with your key.
What we have not verified. The Atlas calls below follow Atlas's public API reference (https://api.recruitwithatlas.com/api/v1/docs) as of September 2026. Atlas has no test environment, and we have not run this code against a live Atlas account. Check the endpoints and field names against that reference, and try the Zap on one test candidate, before you switch it on for real. Atlas can change its API.
What you need
- A Zapier account. This recipe is multi-step and uses Code by Zapier. Multi-step Zaps need a paid Zapier plan or a Zapier trial, and Code steps have run-time limits that depend on your plan. Check Zapier's current plans.
- Access to PlacementFlow's Zapier app. The app is invite-only; ask us for the invite link.
- A PlacementFlow API key made with the Automation (Zapier/Make) preset. See Connect Your CRM for how to create one and connect it.
- An Atlas API key with read and write access to People (and to Projects, if you use the optional project step). An Atlas admin creates it in Atlas's settings, under Integrations, API Keys.
If you have never built a PlacementFlow Zap before, start with the Google Sheets recipe. It shows every screen, and you can check the results in a sheet first.
How Atlas avoids duplicates
Atlas's create call (POST /api/v1/people) never merges into an existing record. When the person already exists, it answers 409 Conflict with the existing personId. Atlas matches on, in order: source.system plus source.externalId, then email, then LinkedIn URL, then phone.
This recipe sends source.system = "placementflow" and source.externalId = <the PlacementFlow candidate id>, so the same candidate always matches the same Atlas person. A 409 is the normal "already exists" path, not an error: the code takes the personId from it and updates the person instead.
The Zap: Candidate Shortlisted → Atlas person + note
Step 1: Trigger
- In Zapier, create a new Zap.
- Trigger: PlacementFlow, event Candidate Shortlisted.
- Connect your account with the API key. It appears as your agency's name, for example Acme Recruiting (live).
- Click Test trigger. Zapier pulls a sample: Sample Candidate, candidate@example.com, score 78. This is made-up data.
Step 2: Filter
Add a Filter step. Continue only if:
- Test is false, and
- the representation consent field does not exactly match
withdrawn.
If your clients can see Atlas records, use the stricter rule: consent exactly matches given.
Step 3: Code by Zapier
-
Add Code by Zapier, event Run JavaScript.
-
Under Input Data, add these names on the left and map one PlacementFlow field per row on the right:
Input name Value atlasKeyyour Atlas API key (typed in) candidateIdCandidate ID firstNameCandidate First Name lastNameCandidate Last Name emailCandidate Email linkedinUrlCandidate LinkedIn URL scoreScore summarySummary strengthsStrengths concernsConcerns pfUrlCandidate PlacementFlow URL projectIdoptional: the Atlas project id to add the candidate to -
Paste this code:
const ATLAS = "https://api.recruitwithatlas.com/api/v1"; const headers = { Authorization: `Bearer ${inputData.atlasKey}`, "Content-Type": "application/json", }; // Check these field names against Atlas's API reference. const person = { firstName: inputData.firstName, lastName: inputData.lastName, email: inputData.email, linkedinUrl: inputData.linkedinUrl, }; // 1. Create, or learn the existing personId from the 409. const created = await fetch(`${ATLAS}/people`, { method: "POST", headers, body: JSON.stringify({ ...person, source: { system: "placementflow", externalId: inputData.candidateId }, }), }); const createdBody = await created.json().catch(() => ({})); let personId; if (created.status === 409) { personId = createdBody.personId; // 2. Already exists: update it. const patched = await fetch(`${ATLAS}/people/${personId}`, { method: "PATCH", headers, body: JSON.stringify(person), }); if (!patched.ok) throw new Error(`Atlas PATCH failed: ${patched.status}`); } else if (created.ok) { personId = createdBody.personId ?? createdBody.id; } else { throw new Error(`Atlas POST failed: ${created.status}`); } // 3. File the screening note. const note = [ `PlacementFlow shortlist. Score (advisory): ${inputData.score || "n/a"}`, inputData.summary, inputData.strengths ? `Strengths: ${inputData.strengths}` : "", inputData.concerns ? `Concerns: ${inputData.concerns}` : "", inputData.pfUrl, ].filter(Boolean).join("\n\n"); const noted = await fetch(`${ATLAS}/people/notes`, { method: "PUT", headers, body: JSON.stringify({ personId, note }), }); if (!noted.ok) throw new Error(`Atlas note failed: ${noted.status}`); // 4. Optional: add to a project (lands in its first stage by default). if (inputData.projectId) { await fetch(`${ATLAS}/projects/${inputData.projectId}/candidates`, { method: "POST", headers, body: JSON.stringify({ personId }), }); } return { personId }; -
Click Test step. With the sample, this creates (or updates) a real "Sample Candidate" person in Atlas. Check the person and the note look right, then delete the sample person in Atlas.
Step 4: Write the Atlas id back
- Add PlacementFlow, action Set Candidate External ID.
- Candidate ID: the trigger's Candidate ID. CRM: Atlas. External ID: the personId returned by the Code step.
- Test it. With the sample candidate, PlacementFlow answers that no candidate with that id exists in your account. That is expected: the sample is not a real candidate. Real runs work.
Step 5: Publish
Click Publish. A draft Zap never runs. From now on, a shortlist reaches Atlas about 45 seconds after the recruiter clicks. That delay is the undo window: an undone shortlist sends nothing.
The score and summary are advisory. PlacementFlow never rejects anyone on a score; a recruiter made this shortlist.
Erasure Zap
Add a second Zap so an erasure in PlacementFlow reaches Atlas:
- Trigger: PlacementFlow, event Candidate Erased. It carries only ids, never a name or email.
- Filter: Test is false, and CRM source exactly matches
atlas. - Action: notify the person who handles data requests (email, Slack, or a task in your task tool) to delete Atlas person CRM ID, erased on Erased at (reason: Reason).
- Test, then Publish. Keep it on for as long as the shortlist Zap is on.
What the external-ID write-back gives you
- Later events about the same candidate carry Candidate CRM source =
atlasand Candidate CRM ID = the AtlaspersonId, so other Zaps can file notes straight onto the person. - Candidate Erased carries the Atlas id, so the deletion request points at the right person.
- Writing it back sends no webhook, so this Zap cannot trigger itself.
- If another PlacementFlow candidate already holds that Atlas id, the step fails with a message naming that candidate.
Notes
- Your Atlas key is visible to anyone who can edit the Zap, because Code step inputs are shown in the editor. Give the key only the Atlas permissions this recipe needs, and limit who can edit the Zap.
- Atlas rate limit: Atlas publishes about 400 writes per minute per agency. Each run makes two to four writes, so everyday shortlisting is fine, but do not replay months of history in one go.
- A record created in Atlas from PlacementFlow is a copy of personal data your agency is responsible for. More in Connect Your CRM.
Troubleshooting
"Your PlacementFlow API key was rejected" (401) The PlacementFlow key was revoked or pasted incorrectly. Generate a new key with the Automation (Zapier/Make) preset and reconnect the PlacementFlow account in the trigger step.
"Atlas POST failed: 401" (or 403)
Atlas rejected your Atlas key, or the key lacks People write access. Create a new Atlas key with People read and write, and paste it into atlasKey.
"Atlas POST failed: 400" or "Atlas note failed: 400" Atlas did not accept a field name or value. Compare the field names in the code with Atlas's API reference and adjust them.
"Atlas ... failed: 429" You hit Atlas's rate limit. Wait a minute and replay the run. The 409 path makes a replay safe: it updates the same person instead of creating a second one.
The Code step timed out Atlas was slow, or your Zapier plan's Code step limit is short. Replay the run from the Zap's history.
No sample found The sample comes from PlacementFlow, not from your real candidates. Check the trigger uses your PlacementFlow connection, then click Test trigger again. If it still fails, reconnect with a fresh key.
Real shortlists are not arriving
- Is the Zap published? A draft never runs.
- Is the PlacementFlow key still active? If it was revoked before you published, the Zap could not register its webhook. Reconnect with a new key, then turn the Zap off and on again.
- Did you wait about 45 seconds? A shortlist that was undone sends nothing, by design.
- Did the filter stop it? Open the Zap's history: a run marked as filtered did arrive and was stopped by your consent or test rule.