Skip to main content

Workflow Automation -Automatically create candidate-job match fit % using OpenAI when new candidates apply to jobs in Recruit CRM

Written by Likhitha Satya Maansi Rudra

Save time and gain deeper insights into candidates with automatically generated summaries, making it easier to review talent quickly.

Apps that are required to be connected for the recipe



🔗 How to connect your Recruit CRM app in Workflow Automation


2. Click on the Connections tab under the 'Workflows' section and click on the 'Create' button >>> 'Connection'.

3. Use the search bar to search for the Recruit CRM app and connect it by selecting it and entering the API key.

Screen Recording 2025-05-04 at 6.48.38 PM.mov [video-to-gif output image]

Once the app is successfully connected, you will be able to see a message as 'Connection Established'.


🔗 How to connect your OpenAI app in Workflow Automation


1. Click on the Connections tab under the 'Workflows' section and click on the 'Create' button >>> 'Connection'.

2. Use the search bar to search for the 'Open AI' app and connect it by selecting it and allowing the required permissions.

Screen Recording 2025-06-27 at 10.37.50 AM.mov [video-to-gif output image]

Once all the required apps are connected, you can select the connected account inside the related steps of the recipe from here.


📋 Overview of each step in the Recipe


1. Trigger: New candidate applied through external forms in Recruit CRM

This is the starting point of the automation. It gets triggered when a new candidate applied through external forms in Recruit CRM.

2. Actions:

  • Monitor step:

    It helps in monitoring the following actions for errors. This makes the automation more reliable.

  • Log message to Job report:

    This is a logger of the prompt for context. This step is not needed in the workflow. You can skip this step after pasting the prompt in the next step once your OpenAI account is connected successfully

  • Send messages to Open AI models:

  • Create note in Recruit CRM

  • Error Handler:

    If something fails within the Monitor block, then this step is triggered. The Retry Logic ensures that if the errors match those specified (429, 500–504), it retries the monitored actions up to 3 times. If the error continues after 3 retries, or if the error doesn’t match the handled types, the automation stops.

Hope this helps!😊

Did this answer your question?