Make/Integromat Case Study: Pipedrive Mega Automations

***Please note that Integromat evolved into Make in February 2022. All content for Integromat is also valid for Make.***

The Problem

A client migrated to Pipedrive and they needed to replicate a series of custom automations via Integromat which were previously handled by custom made scripts in their old CRM system.

The requirements were to:

  1. Send out a document for e-signature on specific events – a specific stage entered in Pipedrive
  2. Tag deals with source information based on originating URL or phone number
  3. Pass the deals forward to another system when the deals are “WON” in Pipedrive
  4. Pass web submissions to Pipedrive as new deals
  5. Pass submissions from Facebook Lead Ads to Pipedrive as new deals
  6. Pass submissions from LinkedIn Lead Ads to Pipedrive as new deals
  7. Send SMS reminders to deals in a specific stage after a specific period of time has passed
  8. Assign owners to new deals to the first person who touches the deal
  9. Send confirmation emails when specific events happen

The Solution

This project could not be solved just with one scenario since different triggers and source systems are being used so I had to come up with 5 scenarios to cover all the requirements.

However, one of the scenarios is a master piece using over 100 modules in Integromat – this main scenario is listening for any deal events in Pipedrive which are received by the Webhook module. When a new ping is received, it’s routed to 10 possible routes by the Router module which is a killer feature in Integromat. Imagine it as IF-THIS-THEN-THAT in a very visual manner.

I specifically opted for this mega-scenario solution since I needed to minimize the number of consumed operations. If I had another scenario listening for the same events and using the same webhook, the number of consumed operations would be much higher.

The project took roughly 40 hours to complete and it it’s biggest project I have ever worked on.

The Scenario

This is how some of the scenarios look:

Integromat and Pipedrive 1

Integromat and Pipedrive 2

Integromat and Pipedrive 4

Integromat and Pipedrive 3

Integromat apps used: Webhooks, Pipedrive, Google Sheets, Break, Router, Iterator, Email, Phone Number, JustCall, Ignore, XML, HTTP, Facebook Lead Ads, LinkedIn Lead Ads

Conclusion

All client needs were successfully covered and all the scenarios have been running without major hiccups in Integromat since February 2021.

The only hiccups are generated by clunky Pipedrive webhooks which don’t always work properly (sometimes coming with 2 hour delays), but unfortunately those are not in my control. The only thing I can do is to complain to Pipedrive support which I do a lot.

Do you want to replicate this for your business yourself? 
GO TO MAKE

Or looking for someone to build your integrations?
HIRE ME

2 thoughts on “Make/Integromat Case Study: Pipedrive Mega Automations

  1. I have never ever had a scenario on make.com work. All walkthroughs online fail. Never met anyone that has achieved success. Help area is full of problems archived with no solutions. I see why it is underutilized, it just never finishes for anyone. If you got yours to work, more power to you. No files are created, no drive content exists, no emails are sent, no google sheets update, no google docs created. Just a constant set of failures.

    1. Sorry to hear… Maybe you could benefit from learning either via https://academy.make.com/ or more condensed https://partnertraining.make.com/? Once you get past the first hurdles, it becomes super powerful. Just refer to all the case studies I’ve published here. And I have published maybe 10-20% of all the stuff I have ever built since I don’t have much time to write these articles anymore.

      Ofc, you will mostly find users online complaining that it does not work – the happy users usually have no need to share their thoughts 🙂

Leave a Reply

Your email address will not be published. Required fields are marked *