Help Center · Integrations
Zapier Recipe: PlacementFlow to Google Sheets
Log every shortlisted candidate (or every submission) in a Google Sheet with the PlacementFlow Zapier app, and delete the rows automatically when the candidate is erased.
8 min readOn this page
This recipe keeps a simple log in Google Sheets. Each time a recruiter shortlists a candidate, a new row appears with their name, contact details, score and summary. When the candidate is erased in PlacementFlow, a second Zap removes their rows again.
It is the easiest recipe to start with: you need no CRM, and you can see every result in the sheet.
A sheet is a new copy of personal data. Every row holds a candidate's name and contact details, and your agency is responsible for that copy: who the sheet is shared with, how long rows are kept, and answering access and erasure requests. Keep the sheet private to the people who need it, and keep the erasure Zap switched on for as long as the logging Zap is on.
What you need
- A Zapier account. This recipe has a filter step and a Google Sheets step, so it is a multi-step Zap. Multi-step Zaps need a paid Zapier plan or a Zapier trial. 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.
- A Google account connected to Zapier.
Step 1: Prepare the sheet (headers first)
Zapier builds its column boxes from the sheet's first row. If row 1 is empty, Zapier has no boxes to fill, and it writes a blank row instead.
-
Create a new Google Sheet, for example "PlacementFlow shortlist log".
-
Type these headers into row 1, one per cell:
A B C D E F G H I J K Name Email Phone LinkedIn Job Client Score Summary Consent PlacementFlow link Candidate ID -
Leave row 2 and below empty. Zapier adds each new candidate as the next row.
Keep the Candidate ID column. The erasure Zap uses it to find a candidate's rows.
Step 2: Set up the trigger
- In Zapier, click Create and start a new Zap.
- For the trigger, choose PlacementFlow, then the event Candidate Shortlisted.
- Connect your PlacementFlow account by pasting the API key. It appears as your agency's name, for example Acme Recruiting (live).
- Click Test trigger. Zapier pulls a sample record called "Candidate Shortlisted A" for Sample Candidate (candidate@example.com) with a score of 78. This is made-up data, not a real candidate.
Step 3: Add a filter
- Add a step and choose Filter.
- Set it to continue only if both rules are true:
- Test is false (Zapier's "(Boolean) Is false" condition)
- The representation consent field does not exactly match
withdrawn
- If anyone outside your agency can see the sheet (a client, a hiring manager), use a stricter rule instead: the consent field exactly matches
given. Only a candidate who agreed to be put forward to clients should ever reach an employer.
When you test the filter with the sample, Zapier says the Zap would not have continued. That is correct: the sample is a test event.
Step 4: Add the Google Sheets action
- Add a step and choose Google Sheets.
- For the action event, choose Create Spreadsheet Row.
Pick Create Spreadsheet Row, not Clear Spreadsheet Row(s)
The action list also offers Clear Spreadsheet Row(s), right next to Create Spreadsheet Row. Clear erases the contents of existing rows. Check the step name before you continue: it must say Create Spreadsheet Row.
- Choose your Google account, the spreadsheet, and the worksheet (usually "Sheet1").
- Zapier now shows one box per header from row 1. If you do not see the boxes, your headers are missing or you added them after choosing the sheet: add them, then click Refresh fields in the step's Configure tab.
Step 5: Map one field per box
Put one PlacementFlow field in each box. Do not drop the whole record into a single box: that writes a block of raw data (JSON) into one cell and the step can fail.
| Sheet column | What to put in the box |
|---|---|
| Name | Candidate First Name, then type a space, then Candidate Last Name |
| Candidate Email | |
| Phone | Candidate Phone (empty for many candidates; that is fine) |
| Candidate LinkedIn URL | |
| Job | Job Title |
| Client | Client Name |
| Score | Score |
| Summary | Summary |
| Consent | the representation consent field |
| PlacementFlow link | Candidate PlacementFlow URL |
| Candidate ID | Candidate ID |
If a label reads a little differently in your editor, type a word from it (for example "consent" or "linkedin") into the field picker.
A few notes on the values:
- Score is advisory, from 0 to 100, and can be empty (for example after a recorded phone screen). PlacementFlow never rejects anyone on a score; a recruiter made this shortlist.
- Job Title and Client Name are empty when the screening was not tied to a job.
- Candidate PlacementFlow URL opens the candidate in PlacementFlow. It only works for someone signed in to your PlacementFlow account.
Step 6: Test, then publish
- Click Test step. Zapier writes the sample (Sample Candidate) into your sheet as a real row. Check it landed in the right columns, then delete that row.
- Click Publish. A draft Zap never runs. Until you publish, real shortlists do not reach the sheet.
From now on, a new row appears about 45 seconds after a recruiter shortlists a candidate. That delay is the undo window: if the recruiter clicks Undo, no row is written.
Step 7: Add the erasure Zap
When a candidate is erased in PlacementFlow (on request, or by the retention schedule), their rows in the sheet must go too. This second Zap does that.
- Create a new Zap. Trigger: PlacementFlow, event Candidate Erased, same connection. It carries only ids and the reason, never a name or email.
- Add a Filter: continue only if Test is false.
- Add Google Sheets, search Lookup Spreadsheet Row. Choose the same sheet. Lookup column: Candidate ID. Lookup value: the trigger's Candidate ID.
- Add Google Sheets, action Delete Spreadsheet Row(s). Choose the same sheet, and use the row found in step 3.
- Test it, then Publish.
A candidate shortlisted more than once has more than one row, and a lookup returns one row per run. Either add a second Lookup and Delete pair, or use Lookup Spreadsheet Rows (Advanced) with Looping by Zapier to delete every match. After the first real erasure, check the sheet to confirm every row for that Candidate ID is gone.
Variant: log submissions instead of shortlists
To log each submission to a client instead, use the trigger Submission Sent. It fires once per client, when the submission email actually leaves your mailbox. Useful extra columns:
| Sheet column | Field |
|---|---|
| Client contact | Recipient name |
| Sent at | Sent at |
| Type | Submission type (cv or notes) |
| Consent basis | Consent authority (candidate for the candidate's own consent, attestation for a recorded recruiter attestation) |
The rest of the recipe (headers first, the filter, one field per box, publish, the erasure Zap) stays the same.
What the external-ID write-back gives you
A spreadsheet has no record id of its own, so there is usually nothing to write back here: the Candidate ID column is the link between the two. If you also run a CRM Zap (see the Bullhorn or Atlas recipes), the CRM id it writes back appears on later events as Candidate CRM ID, and you can add it as a column.
Troubleshooting
A blank row appeared in row 1 (or the row is empty) The sheet had no header row when you set up the step, so Zapier had no column boxes to fill. Delete the blank row, type the headers into row 1, open the Google Sheets step, and click Refresh fields in the Configure tab. Then map the fields again.
A whole block of text (JSON) landed in one cell, or the step errored More than one field, or the whole record, went into a single box. Clear that box and map one field per box, as in Step 5.
Rows disappeared from the sheet Check the Google Sheets step's action. If it says Clear Spreadsheet Row(s), it is erasing rows instead of adding them. Change it to Create Spreadsheet Row, then restore the lost data from the sheet's version history (File → Version history).
The Name column shows only the first name, or the names run together Put Candidate First Name, a typed space, and Candidate Last Name in the same box.
"Your PlacementFlow API key was rejected" (401) The key was revoked or pasted incorrectly. Generate a new key with the Automation (Zapier/Make) preset and reconnect the account in the trigger step.
No sample found The sample comes from PlacementFlow, not from your real candidates. Check the trigger step 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 API 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 in Zapier: a run marked as filtered did arrive and was stopped by your consent or test rule.