Skip to main content

Workflow Automation: Create Contacts in Recruit CRM from Dripify

This article will guide you on how to connect the apps used in the automation and provide an overview of each step involved in the recipe.

Written by Sanjana Panigrahi

This recipe will automatically create new contact records in Recruit CRM whenever leads are captured in Dripify.

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 Dripify app in Workflow Automation


In your Dripify app, set up your webhook events to be sent to the Workato webhook address for this recipe, then proceed to the next step to listen for a sample event.


📋 Overview of each step in the Recipe


1. Trigger: New contact received via a webhook from Dripify:

This is the starting point of the automation. It gets triggered whenever a new contact is received via a webhook from Dripify.

2. Actions:

  • Monitor step:

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

  • Search Contacts in Recruit CRM:

    When a new contact is received via a webhook from Dripify, the recipe searches for the contact in Recruit CRM using the LinkedIn URL.

  • IF Condition:

    Checks whether the contact exists in Recruit CRM:

    • If yes, then no further action is taken.

    • If no, it continues to the next step, which is to create a new contact record with the provided details such as city, email, LinkedIn link, location, last name, first name, position, and phone number.

  • 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.

That's it! I hope this helps.

Feel free to reach out if you have any questions, or run into any errors! Happy recruiting :)

Did this answer your question?