Skip to main content

Workflow Automation -Create signature requests in DocuSign when new hiring stages are updated for Recruit CRM candidates

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

Written by Likhitha Satya Maansi Rudra

Streamline candidate onboarding by automatically sending DocuSign signature requests when hiring stages are updated, reducing paperwork delays.

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 DocuSign 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 DocuSign app and connect it.

Screen Recording 2025-06-05 at 3.10.40 PM.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 for deals won


1. Trigger: New Candidate hiring stage Updated in Recruit CRM

This is the starting point of the automation. It gets triggered whenever a candidate's hiring stage is updated in Recruit CRM.

2. Actions:

  • Monitor step:

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

  • IF Condition:

    Checks whether if the hiring stage is according to your requirement and

    If yes, it continues to the next step, which is sending a document using the template in DocuSign.

Note: Prefill the fields in the template

If no, then no further action is taken.

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