Skip to main content

Workflow Automation - Create documents in PandaDoc when deal stages are newly updated in Recruit CRM

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 Sanjana Panigrahi

With this recipe, you can automatically generate PandaDoc documents based on updated deal stages in Recruit CRM, helping you speed up paperwork and reduce manual effort.

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 PandaDoc account 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 PandaDoc app and connect it by selecting it and entering the API key.

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


📋 Overview of each step in the Recipe


1. Trigger: New deal stage updated in Recruit CRM:

This is the starting point of the automation. It gets triggered whenever a deal 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 the updated deal stage matches your requirements, and :

    • If yes, it continues to the next step, which is to create a record in PandaDoc.

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

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?