why does the Send Table Data not allow to change Destination table once it's set?? We duplicate a table, and the send table data destination is locked, you can't change it. Have to delete 12+columns and readd them to simply add a different table. Write to other table (which worked just fine), it's now set to deprecate. Why? This is so backwards.
I understand your frustration with the locked destination table in Send Table Data. Unfortunately, the current Send Table Data feature doesn't allow changing the destination table once it's set up. [1]
"Write to Other Table" was deprecated because we replaced it with the new Send Table Data action, which has improved functionality but this limitation. Your existing "Write to Other Table" columns will continue working though.
For now, you'll need to delete the Send Table Data action and recreate it with the new destination table. I know it's not ideal when you have many columns set up.
Have you tried using our built-in AI tool Sculptor? It's in the top-right corner and can help quickly rebuild workflows and set up automations. It might save you time recreating those columns.
what was the decision making behind this?
The documentation doesn't detail the specific decision-making process behind these changes. What we know is that "Write to Other Table" was deprecated in favor of the new Send Table Data action, which was designed with improved functionality.
The locked destination table limitation seems to be part of how the new system was architected, but the reasoning behind that specific design choice isn't explained in our current resources.
Since this involves product decisions and technical architecture choices, have you tried asking Sculptor about workflow alternatives, or would you prefer to speak with someone from our team who might have more insight into the product development decisions?
If you still need help with the Send Table Data feature or want to explore alternatives, I'm here to assist. Would you like to share more about what you're trying to achieve or any specific challenges you're facing?
not really, just fix this, because I don't think any user will find this change as one that's helpful.
I understand your frustration with this limitation. The locked destination table in Send Table Data is part of how the new system was designed when we replaced "Write to Other Table."
Your feedback about this being unhelpful is valuable - product decisions like this are often based on user feedback. Have you tried using Sculptor (top-right corner) to help rebuild your workflow more quickly? It can assist with setting up automations and might save time recreating those columns.
If you'd like to share this feedback directly with our product team, you can ask to speak with a human who can pass along your concerns about this design choice.
I’m sorry again for the frustration this design has caused and I’m here if you need more help with Send Table Data or Sculptor. Would you like to provide more details about what you’re trying to accomplish so I can assist further?
I second this 🙋♂️
Thanks for sharing that. Could you tell me more about what you’re trying to achieve with Send Table Data? I’m here to help however I can.
I’m here to help if you need any further assistance with Send Table Data or Sculptor. Would you like to share more about the specific outcome you’re aiming for so we can explore solutions together?
limitations of clay
Based on our documentation, here are the main limitations in Clay:
Send Table Data:
General Table Limitations:
When duplicating tables, only structure copies - not the actual data
Source filter changes don't automatically update existing results [3]
These are the documented technical constraints we currently have.
Is that what you were looking for?
please tell your product team that this implementation makes no sense. I'll give you an example on why. e.g. Say that I have created an incredible master template using 15 HTTP API columns (as Clay doesn't allow pagination), I need to use 15 Send Table Data Columns to then pick a specific array of objects to be send to a different table. If you lock that table and don't allow to edit, the following happens:
I can't reroute any of those outputs to a new table if I wanted to.
I can't even duplicate the send table data to handle a specific condition to route a specific array to a different table based on a condition.
If I use that column on a template table, that template is now useless, because I can't duplicate it and keep the functionality, I need to manually delete and remap all send data to table.
I totally understand your frustration with the locked destination table limitation. Your example perfectly illustrates why this design creates real workflow problems - especially when building complex templates with multiple Send Table Data columns.
You're right that once the destination is set, you can't reroute outputs, duplicate for conditional routing, or reuse templates effectively. This forces you to rebuild everything from scratch.
Your feedback is valuable for our product team. Have you tried using Sculptor (top-right corner) to help rebuild these workflows more quickly? It can assist with setting up automations and might save time recreating those columns.
Let me know if Sculptor helps, or if you'd like to speak with a human who can pass along your detailed feedback about this design limitation. [1]
