Optimizing Workflow to Avoid Duplicate Posts from C-Suite | Clay

Optimizing Workflow to Avoid Duplicate Posts from C-Suite

Hi All, not sure if someone can help. I setup a workflow where we pull posts from a companies c-suite on a schedule. When i asked in help I was told on scheduled runs, it would only pick up new posts. ( i have it set to grab 5 posts at a time) but its repeating posts. I am not sure if setting it to 1 post and running it daily is a good solution or if there is a better way to prevent it from picking up the same posts 2x.

5 comments

Clay
APP
·
·
Use conditional runs to prevent duplicate posts. Set up a conditional formula that checks if a post already exists in your table before enriching it. You can also enable auto-dedupe in your table settings to automatically delete duplicate records, which keeps data clean and reduces spend on accidentally enriching the same record twice. For social media workflows, add a Lookup action to check if content already exists by matching key fields like post ID or URL, then use conditional formulas to prevent the enrichment from running if duplicates are found. Setting to 1 post daily isn't the optimal solution - using conditional logic is more effective.
Sources: AI Formulas + Conditional Runs [Clay 101] - Clay University AI Formulas + Conditional Runs [Clay 101] - Clay University New at Clay | Clay.com Smartlead integration overview | Documentation | Clay University
Peter S.
·
·
Am i able to set it to auto dedupe columns?
Clay
APP
·
·
Yes, you can set auto-dedupe for specific columns. To enable auto-dedupe: 1. Click the Auto-dedupe icon at the bottom right of your table 2. Select Enable automatic deduplication 3. Choose the specific column to dedupe (like post ID or URL) 4. Click Save Changes Auto-dedupe continuously monitors your specified column and automatically deletes duplicate rows while keeping the oldest entry. This prevents duplicate posts from being processed in your workflow. You can also manually dedupe existing data by right-clicking any column header and selecting Dedupe > Delete Duplicate Row.
Sources: Table management settings | Documentation | Clay University Auto-update and Auto-dedupe Table Table columns | Documentation | Clay University
Peter S.
·
·
Is there a limit on the amount of sources. this is a bit manual and could be cumbersome if monitoring 50 -100 profiles.
Clay
APP
·
·
Yes, there's a limit of 100 scheduled sources per plan (Starter, Explorer, Pro, and Enterprise all have the same 100-source limit). For managing 50-100 profiles efficiently with auto-dedupe: Set up auto-dedupe once per table: 1. Click the Auto-dedupe icon at bottom right of your table 2. Select "Enable automatic deduplication" 3. Choose your key column (like post ID or URL) 4. Click Save Changes Auto-dedupe continuously monitors your specified column and automatically deletes duplicate rows while keeping the oldest entry. This works across all profiles in that table, so you don't need to set it up individually for each of the 50-100 profiles you're monitoring. The auto-dedupe feature helps keep data clean and reduces spend on accidentally enriching the same record twice.
Sources: Scheduled sources | Documentation | Clay University Scheduled sources | Documentation | Clay University Scheduled sources | Documentation | Clay University Table management settings | Documentation | Clay University Auto-update and Auto-dedupe Table