Fix Clay Workflow to Receive Only New LinkedIn Posts in Slack

Ashwin J. · 2025-07-15T17:42:25.518Z

Hi, I run a in Clay- a list from which whenever anyone posts on Linkedin, I get that Ln post on my slack channel. The issue- I am getting slack messages of new posts, but also posts from before. For example- I received 10 posts today, but I had already received most of them yesterday and day before. I want this workflow to work for new posts only.

Fix Clay Workflow to Receive Only New LinkedIn Posts in Slack | Clay

6 comments

· Sorted by Oldest

Clay
APP
·
·
To avoid duplicate notifications, adjust your signal's monitoring frequency. In your custom signal settings, you can set how frequently you want your signal to run - choose a shorter interval (like daily) instead of pulling historical data. When creating or editing your custom signal, configure the frequency to only capture new posts since the last run, which prevents receiving notifications for posts you've already been alerted about.
Sources: Custom Signals | Documentation | Clay University Custom Signals | Documentation | Clay University
Ashwin J.
·
·
Could you share more in this- When creating or editing your custom signal, configure the frequency to only capture new posts since the last run,
Clay
APP
·
·
To edit your custom signal frequency: 1. Click the column title of your signal (it has a toggle next to it) 2. Click Edit column 3. In the frequency settings, set a shorter interval like daily instead of longer periods 4. Click Save When you set the frequency to run more often (like daily), the signal only captures new posts since the last run, preventing duplicate notifications for posts you've already received.
Sources: Custom Signals | Documentation | Clay University Custom Signals | Documentation | Clay University
Ashwin J.
·
·
my frequency is already daily, yet i am receving posts from 1 month back
Ashwin J.
·
·
https://app.clay.com/workspaces/49237/workbooks/wb_0sxyr9sq7nUmwfzbFkz/tables/t_0sxyrajZBh6JR7HPAM5/views/gv_0sxyrajwA5QT3zy3Jn4
Bo (.
·
·
This is happening because the enrichment inside the table is retriggering, which can cause older posts to show up again. To fix this, you have two options: 1. Use this table as a source and create a new table to receive the data. That way, you can control what gets added and track only the new posts. 2. Use “Send Table Data” to push the posts to a new table. In that new table, turn on Auto-dedupe to filter out any duplicates. Let me know if you want help setting that up.

Clay
APP
·
·
To avoid duplicate notifications, adjust your signal's monitoring frequency. In your custom signal settings, you can set how frequently you want your signal to run - choose a shorter interval (like daily) instead of pulling historical data. When creating or editing your custom signal, configure the frequency to only capture new posts since the last run, which prevents receiving notifications for posts you've already been alerted about.
Sources: Custom Signals | Documentation | Clay University Custom Signals | Documentation | Clay University
Ashwin J.
·
·
Could you share more in this- When creating or editing your custom signal, configure the frequency to only capture new posts since the last run,
Clay
APP
·
·
To edit your custom signal frequency: 1. Click the column title of your signal (it has a toggle next to it) 2. Click Edit column 3. In the frequency settings, set a shorter interval like daily instead of longer periods 4. Click Save When you set the frequency to run more often (like daily), the signal only captures new posts since the last run, preventing duplicate notifications for posts you've already received.
Sources: Custom Signals | Documentation | Clay University Custom Signals | Documentation | Clay University
Ashwin J.
·
·
my frequency is already daily, yet i am receving posts from 1 month back
Ashwin J.
·
·
https://app.clay.com/workspaces/49237/workbooks/wb_0sxyr9sq7nUmwfzbFkz/tables/t_0sxyrajZBh6JR7HPAM5/views/gv_0sxyrajwA5QT3zy3Jn4
Bo (.
·
·
This is happening because the enrichment inside the table is retriggering, which can cause older posts to show up again. To fix this, you have two options: 1. Use this table as a source and create a new table to receive the data. That way, you can control what gets added and track only the new posts. 2. Use “Send Table Data” to push the posts to a new table. In that new table, turn on Auto-dedupe to filter out any duplicates. Let me know if you want help setting that up.