Managing New Contacts and Company Updates Between Pipedrive and Clay

I am building an automation where new people in Pipedrive get pushed into Clay, what happens if they’re already in the Clay table? Also, if I am pushing the companies the people work at to a new table in clay, and I enrich the companies, what if I want to update all of the companies at a later date (say 6 month) and push them back into Pipedrive with the updates? This means the people and companies will also be in seperate tables, but both connected to pipedrive

2 comments

Bo (.
·
·
Great questions about managing your data flow between Pipedrive and Clay! Let me help you understand how duplicates and updates work. For contacts from Pipedrive: To prevent duplicates, I recommend using the Auto-Dedupe function right after your Pipedrive import. You can set it up to match based on email or another unique identifier. This will automatically delete the variation 2 of every rows. For companies and enrichment updates: You have a few options to handle the 6-month refresh cycle: 1. Create a new table for the refresh: - Import companies from Pipedrive - Run enrichment - Use the Update function to update Pipedrive 2. Update your existing table: - Add a "Last Updated" column - Filter for companies older than 6 months - Run enrichment on those specific rows - Push updates back to Pipedrive I suggest option 2 as it helps maintain data consistency and makes tracking updates easier. Let me know if you need help with the specific functions or have questions about preventing duplicates.
Channeled
APP
·
·
Hi Nicolas B.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:

Managing New Contacts and Company Updates Between Pipedrive and Clay | Clay