When Duplicating Workbook Do Send Table Data Destinations Change?

Petar R. · 2026-01-19T18:16:24.109Z

hey guys, one question: When duplicating the workbook are 'send table data' destination tables fixed to the previous tables from the original workbook, or are they switched to the corresponding destination tables in the new workbook (copied)

When Duplicating Workbook Do Send Table Data Destinations Change? | Clay

9 comments

· Sorted by Oldest

Clay Support
APP
·
·
The workbooks feature is still in its first release and doesn't yet support duplicating workbooks with preserved relationships. [1] Currently, when you duplicate tables individually, the 'send table data' connections would need to be reconfigured manually to point to the new destination tables. [2]
We're actively working on adding workbook duplication functionality where relationships across tables will be preserved automatically. This means in future updates, duplicated workbooks should maintain their 'send table data' connections to the corresponding tables in the new workbook rather than staying linked to the original ones.
Are you looking to duplicate a specific workbook setup, or just planning ahead for when this feature becomes available?
Clay Support
APP
·
·
If you need any more help with duplicating workbooks or configuring 'send table data' connections, I’m here to assist. Would you like to share more details about the workbook setup you’re working on or any specific questions you have?
Petar R.
·
·
Can you please connect me to a human agent. I think this is big Clay limitation. If I were able to re-configure and to change the destination table that would be fine. But I need to delete the 'send table data' enrichment and create a new one with new destination table. Major question: Why is Clay not supporting changing destination table from a drop-down on send table data. To me, it seems super logical for this functionality to exist. But there might be something behind the curtain that I don't understand.
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!
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)
Petar R.
·
·
no specific table, i'd like to discuss with someone from your team
Bo (.
·
·
Hey,
Good question, and the feedback makes sense.
Right now, Send table data doesn’t allow changing the destination table after creation. That’s intentional. Under the hood, that column is tightly bound to the destination table’s schema and internal IDs. If we allowed switching the destination from a dropdown, it could easily break mappings, create silent data mismatches, or send partial data without being obvious. So the safe option today is to delete the column and recreate it with the new destination.
That said, your point is valid. From a user perspective, being able to reselect the destination feels logical, especially when iterating on workflows. We’ve shared this feedback with the team already, and it’s something we’re actively aware of. It’s more a product constraint than a conceptual one.
If you want to talk this through live, the escalation is already in motion and someone from the team will follow up.
Let me know if you have more questions.
Petar R.
·
·
got it Bo (. I expected answer like that. Good to know that you are aware of that. Not a big deal, just wanted to ask! 🙂
Clay Support
APP
·
·
We haven't heard back from you here, so we're going to go ahead and close this thread out.

Still need help here? Reply back and someone will jump back in.

Have a question thats not related to this thread? We recommend kicking off a new ticket in the support channel!

Clay Support
APP
·
·
The workbooks feature is still in its first release and doesn't yet support duplicating workbooks with preserved relationships. [1] Currently, when you duplicate tables individually, the 'send table data' connections would need to be reconfigured manually to point to the new destination tables. [2]
We're actively working on adding workbook duplication functionality where relationships across tables will be preserved automatically. This means in future updates, duplicated workbooks should maintain their 'send table data' connections to the corresponding tables in the new workbook rather than staying linked to the original ones.
Are you looking to duplicate a specific workbook setup, or just planning ahead for when this feature becomes available?
Clay Support
APP
·
·
If you need any more help with duplicating workbooks or configuring 'send table data' connections, I’m here to assist. Would you like to share more details about the workbook setup you’re working on or any specific questions you have?
Petar R.
·
·
Can you please connect me to a human agent. I think this is big Clay limitation. If I were able to re-configure and to change the destination table that would be fine. But I need to delete the 'send table data' enrichment and create a new one with new destination table. Major question: Why is Clay not supporting changing destination table from a drop-down on send table data. To me, it seems super logical for this functionality to exist. But there might be something behind the curtain that I don't understand.
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!
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)
Petar R.
·
·
no specific table, i'd like to discuss with someone from your team
Bo (.
·
·
Hey,
Good question, and the feedback makes sense.
Right now, Send table data doesn’t allow changing the destination table after creation. That’s intentional. Under the hood, that column is tightly bound to the destination table’s schema and internal IDs. If we allowed switching the destination from a dropdown, it could easily break mappings, create silent data mismatches, or send partial data without being obvious. So the safe option today is to delete the column and recreate it with the new destination.
That said, your point is valid. From a user perspective, being able to reselect the destination feels logical, especially when iterating on workflows. We’ve shared this feedback with the team already, and it’s something we’re actively aware of. It’s more a product constraint than a conceptual one.
If you want to talk this through live, the escalation is already in motion and someone from the team will follow up.
Let me know if you have more questions.
Petar R.
·
·
got it Bo (. I expected answer like that. Good to know that you are aware of that. Not a big deal, just wanted to ask! 🙂
Clay Support
APP
·
·
We haven't heard back from you here, so we're going to go ahead and close this thread out.

Still need help here? Reply back and someone will jump back in.

Have a question thats not related to this thread? We recommend kicking off a new ticket in the support channel!