How to Prevent Duplicate Actions in Excel Workbooks with Multiple Tables

Alex K.

What's the best way to delay potential duplicate actions between tables in a workbook?

Context

I have one inbound workbook with 5/6 tables to monitor signals and route leads
We have two primary sources: Demo requests & Docs access

What's happening --

A prospect will try to access our docs, triggering the Docs access table
The same prospect will then soon after submit a demo request, triggering the Demo request table
Both of these tables run at the same time (great response times!) however it's creating duplicate Account records in SFDC while also notifying 2 AEs that they have a new lead

What's the fix?

I'd like to have the tables in the same workbook as they push the same data to a table
I also prefer to keep the tables consolidated

Workbook

6 comments

Channeled
APP
·
·
Here's how you can prevent duplicate records when handling multiple data sources:1. Use Clay as a data cleanroom by routing all your data (both docs access and demo requests) through a single consolidated table first. 2. Before creating new records: • Add a Lookup Records action to check if the contact/account already exists in Salesforce • Use AI formulas and conditional runs to only create records that are confirmed as net new 3. Best practices for implementation: • Turn off auto-update when setting up this new workflow • Manually test a few rows to verify everything works correctly • Only enable automatic uploads once you've confirmed the process 4. If needed, you can enable "Duplicate Rule Override" in the Create Record enrichment, but by default, Clay will not create duplicate records in Salesforce. Sources: Salesforce integration overview | Documentation | Clay University Intro to CRM Data Enrichment [CRM Enrichment] - Clay University Push Data To Your CRM [CRM Enrichment] - Clay University Salesforce Integration Guide
Channeled
APP
·
·
Looks like you're still looking for help. We're escalating this over to our support team and someone should be in touch soon. In the meantime, feel free to include any other information that may be helpful in solving your issue!
LuisArturo
·
·
Hey there Alex thanks for reaching out, noticed that you are using Zapier to receive these requests. Within Zapier you can add a delay to the second table to not run immediately after the first, so if the Demo table is usually the second table to run, just make sure to add a delay to this part of the Zap so that after the delay is over it, the Demo table can run its workflow, which should find these newly created values with the "Salesforce Lookup" integration you already have, thus preventing you create Account integration in the same table from running as well and creating the duplicate account.
Alex K.
·
·
Ah thank you! So smart
Channeled
APP
·
·
Hi Alex K.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Channeled
APP
·
·
Thank you so much for sharing your feedback Alex K.!