Hey ​@MATTG68,

There is an Updated Candidate trigger but no Update Candidate action that I could see in Bullhorn Zapier integration- https://zapier.com/apps/bullhorn-crm/integrations so you may to want to look in Bullhorn API to achieve. After that you can send a POST request to the endpoint to update the candidate using Webhooks by Zapier action or API request action.

Hope it helps!

Hi ​@MATTG68 

If you are trying to update a Bullhorn Candidate, then this would be the correct Zap action to use: Bullhorn - API Request

Bullhorn API: https://bullhorn.github.io/rest-api-docs/

NOTE: You can also try creating a Custom Action with the help of AI (if available): https://help.zapier.com/hc/en-us/articles/16276574838925-Custom-Actions-in-Zapier

Other “update” Zap actions available for Bullhorn:

• Update Client Contact
• Update Lead
• Update Opportunity

Hi Troy,

Thank you for all the information.  I have followed your steps and used AI but I am still having issues as shown in the Screen shot below and was hoping you may be able to help.  I am a complete Novice when it comes to this and just trying to create a solution so that when someone fills out a registration form on our website that it updates the candidate information as much as poossible in Bullhorn.  

I am not sure what I am doing wrong?

Thanks

Matt

​@MATTG68 

For us to have context about the Zap step error, post screenshots showing how your Zap step 2 is configured in the CONFIGURE tab in EDIT mode with the field mappings visible.

When pasting this this I saw my lookup was incorrect as should be email.  I changed the lookup to Email and ran again.  This time I got the following error:

​@MATTG68 

See screenshot below.

If you change the field setting to True, then it will return found = true/false instead of an error.

The error means no existing Bullhorn Candidate was found for the supplied email to search by.

Troy you are a legend.

I did the final testing and it appears to passed all the tests so I published.  I then completed a registration form and it appears to have not done anything in Bullhorn?  Do you know if there is a delay or do I need to do something else?

Cheers

Matt

​@MATTG68 

Check the live Zap Run history details to see the DATA IN/OUT for each step to help you trace and troubleshoot: https://zapier.com/app/history/

If Zap step 2 is working as expected, then it is likely the API request in Zap step 3 is not configured correctly.

If you need to hire help, there is a directory of Zapier Partners: https://zapier.com/partnerdirectory

Thanks Troy for your assistance.

The history is telling me everything has been successful and in steps 2 and 3 a cadnidate was found and a new HTTP request sent to Bullhorn.

I will look at the partner directory as I am at a loss to what could be the issue.

Hey ​@MATTG68,

What error exactly are you getting for the API request action? You have to select the POST or PUT request in Http Method to method to update the candidate. Also check in the Bullhorn if the update is successful once the request is successful. If you are encountering errors through API request action, you can also try to use Webhooks by Zapier with a POST request. See more about it here- https://help.zapier.com/hc/en-us/articles/8496083355661-How-to-get-started-with-Webhooks-by-Zapier
 

Hope it helps!

PS: If you need more active help, I’m happy to connect through my Zapier Solution Partner page if you’d like to reach out here- https://zapier.com/partnerdirectory/automation-jinn