Replacement of Write to Table with Send Table Data Function

Assad A. · 2026-01-08T06:35:27.022Z

I received an email yesterday that Write to Table function is now replaced by Send Table Data function. There reason I preferred it over Send Table Data is that it creates no connection between the two tables and hence a destination table can receive data from any number of tables, this is severely restricted by Send table Data action.

Replacement of Write to Table with Send Table Data Function | Clay

Clay Support
APP
·
·
You're right that Send Table Data has connection limits - there's a maximum of 20 tables that can be connected (including across workbooks), and data can only flow in a linear direction (A → B → C, no loops). [1]
However, your existing Write to Table columns will continue working even though the function is deprecated. We recommend transitioning to Send Table Data when possible, but you can keep using your current setup if the connection restrictions don't work for your workflow.
If you need data to flow back to a source table, you can use "Lookup Multiple Rows in Other Table" or "Lookup Single Row in Other Table" actions instead. [2]
Clay Support
APP
·
·
Is that what you were looking for?
Assad A.
·
·
I want to keep using the functionality of Write to Other Table, I have a lot of other workflows to make that will become impossible without Write to Other Table functionality.
Clay Support
APP
·
·
Good news - your existing Write to Other Table columns will continue working even though it's deprecated. You can keep using all your current workflows without any changes.
The deprecation just means no new features will be added to Write to Other Table, but all existing functionality remains intact. You can even still create new Write to Other Table columns using the "Add Enrichment" button - we're keeping that option available.
So your workflows are safe and you can continue building new ones with Write to Other Table for now. [1]
Clay Support
APP
·
·
Is that what you were looking for?
Clay Support
APP
·
·
If you need any more help with your workflows or have questions about the Write to Other Table functionality, I’m here to assist. Would you like to share more details about what you’re trying to achieve or any challenges you’re facing?
Assad A.
·
·
Please connect me to a human about this.
Clay Support
APP
·
·
Got it — I’m connecting you to a human teammate now.
Clay Support
APP
·
·
Our support team has got your message and we'll get back to you soon! We're currently outside of our standard office hours (9 AM to 9 PM EST, Monday through Friday), so it may take a little longer for us to respond.

If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!

image.png(93 kB)
Mayato (.
·
·
Hi Ali, thank you for reaching out and for sharing such thoughtful feedback.
I’m sorry that the depreciation of Write to Table has caused limitations in your workflow. I’m happy to pass your feedback along to the team that owns this feature.
To make sure we fully understand your use case, could you please share more details on how you were using Write to Table? In particular, when do you need more than 20 table sources? Are there other workflows that are no longer possible with the current Send to Table action?
Thank you so much for taking the time to share this. We truly appreciate your feedback and hope to improve the feature based on it.
Assad A.
·
·
We basically had central tables for data enrichment, this was to ensure global deduping and no enrichment was done repeatedly is different tables. We made pre-set templates, where the data would be written to the single processing table, enriched and then we get it back via lookup.
Assad A.
·
·
This feature of being able to write data to another table without establishing any connections is extremely useful and also critical in our use case. Without this, our whole pipeline comes down. Is Clay planning on an alternate similar solution, when can we expect it? Or is it a complete loss of functionality in this case?
Yash M.
·
·
Hi Ali. This is Yash from Clay Product Support. Thank you for sharing all the context. I hear you completely and this is definitely a use case worth considering on our end. Let me write to our engineering team. I wonder if we have workarounds built in for this. We will get back to you on this shortly.
Yash M.
·
·
In the mean time could you also share a couple of examples of your source table and the central processing table just so I can see what your existing flow looks like with the write to table functionality? Thank you!
Assad A.
·
·
Sure, This is a processing table https://app.clay.com/workspaces/723992/workbooks/wb_0t299skgRyic6DbjAPZ/tables/t_0t2ub76pxaWP4eXqZpM/views/gv_0t2ub77QDWQNWoBA8WZ And this is a table utilizing the function with 'Write to Other Table' https://app.clay.com/workspaces/723992/workbooks/wb_0t42fqxWUNMVDsxtsCf/tables/t_0t42fqxPHvubqWSBfWy/views/gv_0t42byfdRgvurHXfMEP

19 comments