Best practices for comparing outbound list (sent outside Pipedrive) with Pipedrive
Hi everyone, we have ca. 100K companies in our CRM and would like to check from an outbound list which leads might already be customers or prospects. We have several ideas, but they don’t seem like best practices yet - maybe you can advise a better workflow:
- Exporting Pipedrive deals through Coupler to Google Sheet and then running different index match formulas to spot overlaps. This often crashes for the 100,000 records.
- Calling a Zapier Zap (e.g. from Google Sheet) to look up the value with a custom API call from Zapier. This is tedious and costs a lot of Zap tasks.
- Using Google Sheet app scripts. Here it is a challenge, how we can build a scalable workflow that does not hit Pipedrive’s usage limits. Manually dragging down formulas for many cells and waiting is one approach, but not efficient and can fail due to several reasons.
- Using Clay and lookup person / deal, but I currently face some difficulties with that approach as the matched results do not make sense and I sometimes seem to hit the Pipedrive API rate limit.
Thus, I would be very curious if you can help point to a more effective workflow for checking a list of leads against our existing Pipedrive data.
Thanks a lot in advance!
Answers
-
- Coupler is a good option but will work if it is only a one-time process.
- The cost for using Make/Integromat or Zapier or Relay will be based on how many leads you need to check in your outbound process. A 'search' step will remove the existing number of contacts inside Pipedrive as a factor.
- Pretty much a combination of 1 and 2 without the use of Make/Integromat or Zapier or Relay.
- Clay now has OAuth based connection with Pipedrive that allows for higher rate limits.
0 -
Thanks @Amit Sarda (AmitSarda.xyz)!
I am still looking for the most effective set-up, do you possibly have another idea?
Also, have you ever set up a custom HTTP action in Clay to search Pipedrive deals? I was struggling to do so.
0 -
Send me a screen recording of where you're struggling.
0 -
I believe that the endpoint URL might be incorrect? Currently, it seems that any entry returns a 200 return code with such a list of items / deals as you can see on the screenshots attached:
0 -
Also came here looking for a tool to easily compare an external list with what we already have in Pipedrive.
0 -
Orchestrating the campaign in Clay may be your best bet. You can have direct integrations with Pipedrive, or via API calls to see if a particular email already exists in Pipedrive.
0