Help Center · Integrations
Zapier Recipe: PlacementFlow to Bullhorn
Put shortlisted candidates, submissions and erasure requests into Bullhorn with the PlacementFlow Zapier app and Bullhorn's own Zapier connector.
6 min readOn this page
This recipe files PlacementFlow activity in Bullhorn:
- a shortlisted candidate becomes a note on their Bullhorn record (or a new Bullhorn candidate)
- a submission becomes a note
- an erasure becomes a task for a person to delete the Bullhorn record
How the connection works. The Bullhorn side uses Bullhorn's own Zapier connector, under your own Bullhorn contract and your own Bullhorn login. PlacementFlow never calls Bullhorn: the Zap does, as you.
What we have not verified. We have not tested Bullhorn's connector ourselves, because it runs under each agency's own Bullhorn contract. Before you start, check with Bullhorn which Bullhorn edition and which Zapier plan the connector needs. The Bullhorn step names below (Find Candidate, Create Candidate, Create Note, Create Task) describe what to look for; your version of the connector may name them slightly differently.
What you need
- A Zapier account. Every Zap here is multi-step (a filter plus Bullhorn steps). 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.
- Bullhorn's Zapier connector, connected to your Bullhorn account.
If you have never built a PlacementFlow Zap before, start with the Google Sheets recipe. It shows every screen, and you can see the results in a sheet before you touch Bullhorn.
Zap 1: Candidate Shortlisted → Bullhorn note
-
Trigger. Choose 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 to pull the sample (Sample Candidate, candidate@example.com, score 78). The sample is made-up data.
-
Filter. Continue only if:
- Test is false, and
- the representation consent field does not exactly match
withdrawn.
If your clients can see Bullhorn records (for example through a Bullhorn client portal), use the stricter rule: consent exactly matches
given. -
Find the Bullhorn candidate. Add Bullhorn's candidate search (usually Find Candidate), searching by email with Candidate Email.
- To create a Bullhorn candidate when none is found, turn on the search's "create if not found" option and map Candidate First Name, Candidate Last Name, Candidate Email, Candidate Phone and Candidate LinkedIn URL, one field per box.
- If you would rather not create Bullhorn candidates automatically, leave that option off. The Zap then stops when there is no match.
-
Add a note. Add Bullhorn's Create Note action on the candidate from step 3. A useful note body:
- Score: Score (advisory, 0 to 100, can be empty)
- Summary: Summary
- Strengths: Strengths
- Concerns: Concerns
- Link: Candidate PlacementFlow URL
-
Write the Bullhorn id back. Add PlacementFlow, action Set Candidate External ID:
- Candidate ID: the trigger's Candidate ID
- CRM: Bullhorn
- External ID: the Bullhorn candidate id from step 3
-
Test each step, then Publish. A draft Zap never runs.
- Testing the Bullhorn steps with the sample may create a "Sample Candidate" record in Bullhorn; delete it afterwards.
- Testing step 5 with the sample says no PlacementFlow candidate with that id exists. That is expected: the sample is not a real candidate. Real runs work.
The score and summary are advisory. PlacementFlow never rejects anyone on a score; a recruiter made this shortlist.
Zap 2: Submission Sent → Bullhorn note
- Trigger. PlacementFlow, event Submission Sent. It fires once per client, when the submission email actually leaves your mailbox.
- Filter. Test is false, and the representation consent field does not exactly match
withdrawn. - Find the Bullhorn candidate. Once Zap 1 has written the Bullhorn id back, Candidate CRM ID holds it, so you can look the candidate up by id. Otherwise search by Candidate Email.
- Add a note. Bullhorn Create Note: "Submitted to Client Name, contact Recipient name (Recipient email), on Sent at." Add Candidate PlacementFlow URL as the link.
- Test, then Publish.
Zap 3: Candidate Erased → Bullhorn task
PlacementFlow never deletes anything in Bullhorn for you. When a candidate is erased in PlacementFlow, this Zap creates a task so a person deletes or anonymises the Bullhorn record.
- Trigger. PlacementFlow, event Candidate Erased. It carries only Candidate ID, CRM source, CRM ID, Erased at and Reason (
requestorretention), never a name or email. - Filter. Test is false, and CRM source exactly matches
bullhorn. - Create a task. Bullhorn Create Task, assigned to whoever handles data requests: "Delete or anonymise Bullhorn candidate CRM ID: erased in PlacementFlow on Erased at (reason: Reason)."
- Test, then Publish.
A candidate erased before you wrote their Bullhorn id back arrives with an empty CRM ID. Route those to a person too (for example an email with the Candidate ID), because the event deliberately carries no name or email to search by.
What the external-ID write-back gives you
- Later events about the same candidate carry Candidate CRM source =
bullhornand Candidate CRM ID = the Bullhorn id, so a Zap can update the right record without searching by email. - Candidate Erased carries the Bullhorn id, so the deletion task points at the right record.
- Writing it back sends no webhook, so Zap 1 cannot trigger itself.
- If another PlacementFlow candidate already holds that Bullhorn id, the step fails with a message naming that candidate. That usually means a duplicate in one of the two systems.
Your duties
A Bullhorn record created or updated from PlacementFlow is a copy of personal data your agency is responsible for. The consent filter keeps candidates who withdrew consent out of Bullhorn, and the erasure Zap makes sure an erasure in PlacementFlow reaches Bullhorn. Keep Zap 3 on for as long as Zaps 1 and 2 are on. More in Connect Your CRM.
Troubleshooting
"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 PlacementFlow account in the trigger step.
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.
The Bullhorn step cannot find the connector's action, or asks for a different plan Bullhorn's connector and its requirements depend on your Bullhorn contract. Ask Bullhorn support which edition and Zapier plan you need.
"Already linked to another PlacementFlow candidate" The Bullhorn id already belongs to another PlacementFlow candidate. Merge or fix the duplicate in one of the two systems, then replay the Zap run.
A candidate's details landed in one field as a block of text Map one PlacementFlow field per Bullhorn box. Never drop the whole record into one box.
Real events are not arriving
- Is each 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.
- For shortlists, did you wait about 45 seconds? That is the undo window; a shortlist that was undone sends nothing.
- Did a 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.