Join the Community

Issue with Clay-Pipedrive Lead Routing Workflow Automation

·

Hi there, I'm facing an issue with our current Clay-to-Pipedrive lead routing workflow. For context, we're using Clay to identify potential leads from our website visitors and then routing them to Pipedrive for outreach campaigns. Here's how the workflow is set up:

1.
A new company is added in Clay
2.
Clay identifies 5 people from that company
3.
Clay also gathers relevant company news

Our tech team built an integration with Pipedrive to automatically create a deal in the 'Outbound Sales' pipeline once individuals are found. They implemented the following rules: #1 The first person identified from the company is set as the primary contact for the deal in Pipedrive. #2 If a deal for that company already exists (#1 rule), additional people from the same company are added as Participants to the existing deal. This worked well during manual testing, as we processed Clay rows individually. However, now that the workflow is automated, we're seeing an issue: multiple deals are being created in Pipedrive for the same company, each with a different individual as the primary contact. This suggests that the API isn't recognizing that a deal already exists when processing multiple leads from the same company simultaneously. Example: The initial tab where we set up the flow: https://app.clay.com/workspaces/367095/workbooks/wb_0swnqmvEtxQG9HXxd7D/tables/t_0swv2xvM2ijrzCpeupq/views/gv_0swv2xwsN7SWRupdtSW Here's what comes in Pipedrive (attached) Would love your input on how we can resolve this. Thanks!

5 comments

Channeled
APP
·
·
To prevent multiple deals from being created for the same company, you need to implement a lookup step before creating deals. Use Clay's Lookup action to check if a deal already exists for that company in Pipedrive before creating a new one. Set up conditional runs in Clay using conditional formulas to prevent your "Create Deal" integration from running if a deal for that company already exists. This approach ensures proper CRM hygiene by keeping records de-duplicated and maintaining data integrity when adding contacts. The Pipedrive integration in Clay supports lookup actions that can retrieve existing deals by searching for organization names or other identifying fields. What specific field are you using to identify companies in your workflow - company name, domain, or another unique identifier?
Sources: Smartlead integration overview | Documentation | Clay University Push Data To Your CRM [Clay 101] - Clay University Pipedrive integration overview | Documentation | Clay University
Laura L.
·
·
Okay great thanks a lot I'll try that. We're using the domain to identify companies
Laura L.
·
·
But companies are identified through a tool called Snitcher and listed in Clay with webhooks
Channeled
APP
·
·
To prevent duplicate deals when routing leads from Snitcher via Clay to Pipedrive, implement a lookup step before creating new deals: 1. Use Clay's "Lookup Organization with Pipedrive" action to check if the company already exists in Pipedrive using the domain as identifier. 2. Set up conditional runs in Clay with formulas that only trigger the "Create Organization" action when no matching organization is found. 3. For people from the same company, first look up the organization, then associate new contacts with the existing organization rather than creating new deals.
Sources: Lookup Person with Pipedrive | Clay.com Pipedrive x Clay integration | Clay.com Smartlead integration overview | Documentation | Clay University
Laura L.
·
·
yes thanksI'll try tha

Issue with Clay-Pipedrive Lead Routing Workflow Automation | Clay