Pipedrive Deal Stage: Zapier Automation

​

What is Zapier?

​

Import stage of a deal from Pipedrive into CloudTalk

Note:  Three-step zaps like the one detailed below require a premium
Zapier account.

1. As a trigger in the Zap editor, select Pipedrive from the list of apps.
2. For Trigger Event, select Updated Deal Stage. This trigger will be set off any time a Deal Stage is updated in the Pipedrive app.
   
3. You will be prompted to connect your Pipedrive account before continuing.
4. Under Set up trigger, you will need to choose a Stage in Pipeline, which will be Lead In (Pipeline).
   
5. Running the Test trigger step is usually recommended, but it requires there to be at least one real instance where the trigger occurs, as sample data.
6. For the next step, Set up action, our goal is to set up the action which will detonate every time an Updated Deal Stage occurs in Pipedrive.
7. For the Choose account prompt, you will need to link your CloudTalk account if you haven’t done so already. Select +Add new account and use the API keys generated from the CloudTalk dashboard via Settings > API Keys as your login Access Key ID and Access Key Secret.
   
8. As an Action Event, we will choose Find Contact.
   
   Note:  This Event type assumes the contact already exists in
   CloudTalk. Contacts could be imported via integration beforehand.
   
9. Define a Keyword in the Set up action section**.** Click into the box to see a dropdown list of dynamic values derived from the trigger step**.** Decide whether to choose a phone number or email to be the Keyword which the algorithm will search for.
   
10. It is recommended to test this step. If the Find Contact action is working correctly, the test should return customer data currently present within the associated CloudTalk account.
    
11. Now we must make another action step. This action will require us to choose Webhooks by Zapier (premium) as the app.
12. Select Custom Request as the Action Event.
    
13. The Method will be PUT. This type of API method is used mostly in instances where we want to insert new data into a database, replacing old data if the data parameters already exist. In our example, we are using this method to either “put” a new deal stage into a client’s profile, or update a deal stage which already exists for that client.
14. Under URL, we will enter the URL contact id retrieved in our Find Contact action. This sets the destination of the requested action to the desired client within each iteration of the Zap.
15. Leave the Data Pass-Through? default set to False, as this option is not relevant to our task.
16. In the Data box, you can paste in the data structure below, replacing the quoted text “Lead” with the word or phrase you would like the CloudTalk tag alligned to your Pipedrive deal status to be called:
    {
      "tags": [
        "Lead"
      ]
    }
    
17. The Unflatten default Yes can be left as is.
    
18. Authorization is once again required in the Basic Auth box, which asks for “A pipe ( | ) separated username, password combo.” This username | password should be the same CloudTalk API KEY | API KEY SECRET previously retrieved from Dashboard Settings > API Keys.
19. Finally, we need at least one entry for Headers, which will have the key Content-Type and the value application/json. Click Continue and test the action**.** Zapier should notify if the test was successful, and once the Zap is activated, you will be able to access the new tag within your CloudTalk profile.
    

Remember:  The purpose of this automation was not just to make a new tag
in CloudTalk (which can be done right from Dashboard Settings). Tags
created from this Zap will specifically be aligned with meaningful 
data stored on your Pipedrive account (or from another CRM).