I have a Table A with a "Send table data" action sending each item from a list of all 5 recent sessions from Clay Web Intent to a Table B. What happens if the recent 5 sessions get updated? My aim was to send all 5 new rows to Table B and auto-dedupe by Session ID, but now i am not sure if "Send table data" will detect that these 5 items in a list have changed.
When the 5 recent sessions get updated, "Send table data" will detect the change and re-run. By default, it updates existing rows in Table B instead of creating duplicates. [1]
The key setting is "Update existing rows on re-run" - when enabled (default), it matches and updates the same rows rather than creating new ones. You can disable this if you want new rows each time. [2]
For your Session ID deduplication goal, the default behavior should work perfectly - it'll update the existing rows in Table B when the source list changes, maintaining one row per session. [3]
Was that helpful?
but it takes a list and it sees "5 items". Are you sure it will send new rows and detect any changes? Because now i dont see any new sessions appearing
You're right to question this. When "Send table data" processes a list, it sees the list as one item containing 5 sessions, not 5 separate items. [1]
If the content of those 5 sessions changes but the list structure stays the same, Clay won't automatically detect this as a change that triggers a re-run. [2] Clay doesn't reprocess data automatically when underlying source data changes - you'd need to manually re-run the action or set up a scheduled run. [3]
For your use case, you might need to restructure this to send each session individually rather than as a list, or set up a scheduled run to periodically check for updates.
Is that what you were looking for?
but itndoesnt solve the issue as it might happen that a company will have more than 5 session per day so i wont save them all. Scheduled runs can be ran daily at minimum
You're right - scheduled runs have a daily minimum, which won't capture all sessions if a company has more than 5 per day. [1]
For real-time session capture, consider these alternatives:
Auto-update approach: Enable auto-update on your Web Intent source table so it automatically processes new sessions as they come in, then use "Send table data" to push each new session individually to Table B. [2]
Custom signals workflow: Set up a system that compares current vs previous runs to detect new sessions, then only sends the truly new ones to Table B. [3]
Before we dive deeper into setup, have you tried using Sculptor? It's our built-in AI tool in the top-right corner that can help you build this exact workflow automatically. It's free and might save you time setting this up. Give it a try and let me know if it helps solve your session tracking issue.
If you still need help with setting up your session tracking or using Sculptor, I’m here to assist. Would you like to share more details about what you’re trying to achieve or any specific challenges you’re facing?
