Creating a Unique Table of LinkedIn Post Reactions Without Duplicates

Aditya K. · 2025-04-28 16:48:20.180607+00

Hello all, I need some help with a table. So i have a table with multiple rows of LinkedIn post urls, • I enriched the posts to find who liked it, commented on it and shared it. • Then consolidate all this information for one post like in the first image, so there are no duplicate names between who has liked it, Commented on it, shared it. • I did the same thing for the next two rows on linkedin post url's. when i tried a "write to table" function individually for each row, multiple people got duplicated as they are present in multiple LinkedIn urls. As they have commented/liked/shared another post. Is there a solution to go about with this where I can have a table with just the names of the people and no duplicates, Basically, is it possible to have a table by names of people who have reacted instead of posts like i have right now. Thanks in Advance!

Creating a Unique Table of LinkedIn Post Reactions Without Duplicates | Clay

10 comments

· Sorted by Oldest

Channeled
APP
·
·
To create a table with unique names of people who've reacted across multiple LinkedIn posts, you can use our "Find Post Audience" action and then use the "write to table" feature. Here's how: 1. Use the "Find Post Audience" action for each LinkedIn post URL. 2. Set "Reaction type" to retrieve all reactions (likes, comments, shares). 3. Use the "write to table" feature to consolidate results into a single table. 4. Remove duplicates using Clay's data cleaning tools. This approach will give you a table of unique individuals who've engaged with your posts, regardless of which specific post they interacted with or how they reacted.
Sources: LinkedIn integration | Documentation | Clay University LinkedIn integration | Documentation | Clay University
Aditya K.
·
·
no, since that is only application to my own posts, I just need help with re arranging by clay table.
Aditya K.
·
·
https://app.clay.com/workspaces/575662/workbooks/wb_kAzT26sGN39X/tables/t_pVA7tYMnmVfT/views/gv_k6kbkmC8MAEg
Smit V.
·
·
Hi Aditya, Thank you for reaching out! If I understand correctly, you’d like a list of people who have interacted with the posts in one table, without any duplicates. You can achieve this by using the Write to Table action and enabling the Auto-dedupe feature on the 'LinkedIn Profiles' column in the new table where all the entries are being written.
(521 kB)
With Auto-dedupe turned on in the new table, any duplicate entries will be automatically removed, keeping only the first entry for each person. I hope this solves your issue, but please let me know if I’ve misunderstood or if you need any further help!
Aditya K.
·
·
Hi Smit, Thank you for getting back to me. The issue is a bit more complex than it initially seemed. Here's the background: I have a table organized by LinkedIn profile URLs. I enriched these URLs to retrieve comments, likes, and shares, which I placed into three additional columns. Then, I used an AI agent to consolidate these columns into a single nested structure (as shown in the attached image). The purpose of this consolidation was to have each person's name and LinkedIn URL listed only once, with their associated reactions (like, comment, share) attached accordingly. Now, the main issue: Some individuals have interacted with multiple posts — meaning the same person appears across multiple rows in the consolidated column. However, when I use "Write to Columns," the output splits into a new table where each interaction is recorded separately. Although auto-deduplication is enabled, it doesn't solve the problem because each row corresponds to a different post URL. As a result, it's difficult to accurately track how frequently a particular individual has interacted across different posts.
Loading attachments
Smit V.
·
·
I understand what you’ve done so far and the reasoning behind it. If your goal is to have a consolidated list of unique people, you should run auto-dedupe on the person’s LinkedIn URL (rather than the post’s URL). This will ensure each individual only appears once in the table. However, you mentioned that it’s difficult to accurately track how frequently a particular individual has interacted across different posts. If your goal is to see how many times-and on which posts-a person has interacted, you’ll actually need to keep those multiple entries, with each row linking the person to a specific post. Could you clarify your main objective? Are you looking for a unique list of people, or do you want to track all interactions each person has had across different posts?
Aditya K.
·
·
My aim is to basically get a list of unique people who have interacted with the posts, while tracking if they have interacted with multiple posts, and if yes, which posts. Right now, when I write to table i have names of people in one column and the linkedin post url in another column. I dedupe them, but if the person was there beause he had interacted with another post, I loose that information.
Smit V.
·
·
Got it. I recorded a quick loom video for you. I hope this helps. Let me know if you have any further questions.
Aditya K.
·
·
Thank you so much Smit! Really appreciate the help on it, this is exactly what i was struggling with. 🙏
Smit V.
·
·
Happy to help :)

Channeled
APP
·
·
To create a table with unique names of people who've reacted across multiple LinkedIn posts, you can use our "Find Post Audience" action and then use the "write to table" feature. Here's how: 1. Use the "Find Post Audience" action for each LinkedIn post URL. 2. Set "Reaction type" to retrieve all reactions (likes, comments, shares). 3. Use the "write to table" feature to consolidate results into a single table. 4. Remove duplicates using Clay's data cleaning tools. This approach will give you a table of unique individuals who've engaged with your posts, regardless of which specific post they interacted with or how they reacted.
Sources: LinkedIn integration | Documentation | Clay University LinkedIn integration | Documentation | Clay University
Aditya K.
·
·
no, since that is only application to my own posts, I just need help with re arranging by clay table.
Aditya K.
·
·
https://app.clay.com/workspaces/575662/workbooks/wb_kAzT26sGN39X/tables/t_pVA7tYMnmVfT/views/gv_k6kbkmC8MAEg
Smit V.
·
·
Hi Aditya, Thank you for reaching out! If I understand correctly, you’d like a list of people who have interacted with the posts in one table, without any duplicates. You can achieve this by using the Write to Table action and enabling the Auto-dedupe feature on the 'LinkedIn Profiles' column in the new table where all the entries are being written.
(521 kB)
With Auto-dedupe turned on in the new table, any duplicate entries will be automatically removed, keeping only the first entry for each person. I hope this solves your issue, but please let me know if I’ve misunderstood or if you need any further help!
Aditya K.
·
·
Hi Smit, Thank you for getting back to me. The issue is a bit more complex than it initially seemed. Here's the background: I have a table organized by LinkedIn profile URLs. I enriched these URLs to retrieve comments, likes, and shares, which I placed into three additional columns. Then, I used an AI agent to consolidate these columns into a single nested structure (as shown in the attached image). The purpose of this consolidation was to have each person's name and LinkedIn URL listed only once, with their associated reactions (like, comment, share) attached accordingly. Now, the main issue: Some individuals have interacted with multiple posts — meaning the same person appears across multiple rows in the consolidated column. However, when I use "Write to Columns," the output splits into a new table where each interaction is recorded separately. Although auto-deduplication is enabled, it doesn't solve the problem because each row corresponds to a different post URL. As a result, it's difficult to accurately track how frequently a particular individual has interacted across different posts.
Loading attachments
Smit V.
·
·
I understand what you’ve done so far and the reasoning behind it. If your goal is to have a consolidated list of unique people, you should run auto-dedupe on the person’s LinkedIn URL (rather than the post’s URL). This will ensure each individual only appears once in the table. However, you mentioned that it’s difficult to accurately track how frequently a particular individual has interacted across different posts. If your goal is to see how many times-and on which posts-a person has interacted, you’ll actually need to keep those multiple entries, with each row linking the person to a specific post. Could you clarify your main objective? Are you looking for a unique list of people, or do you want to track all interactions each person has had across different posts?
Aditya K.
·
·
My aim is to basically get a list of unique people who have interacted with the posts, while tracking if they have interacted with multiple posts, and if yes, which posts. Right now, when I write to table i have names of people in one column and the linkedin post url in another column. I dedupe them, but if the person was there beause he had interacted with another post, I loose that information.
Smit V.
·
·
Got it. I recorded a quick loom video for you. I hope this helps. Let me know if you have any further questions.
Aditya K.
·
·
Thank you so much Smit! Really appreciate the help on it, this is exactly what i was struggling with. 🙏
Smit V.
·
·
Happy to help :)