Recreating Lookup Table After User Removal: Issues Explained

Siddhant B. · 2025-12-16T10:16:45.890Z

"Lookup table" needs to be recreated completely if the user that created it is removed from the workspace. Context: 1. A member of my team (A) had created this automation. 2. He left, I deleted his account. 3. The automation stopped working (separate thread). 4. When I'm trying to get it working again, Clay is not allowing me to select any table (despite me changing the "Clay account" to my own).

Recreating Lookup Table After User Removal: Issues Explained | Clay

15 comments

· Sorted by Oldest

Clay Support
APP
·
·
Hi there, thanks so much for sharing this! We’ll be passing your feedback along to our product team, and any additional context you can provide will help us prioritize with your needs in mind as we shape the roadmap.
Want to chat with someone on the team? Feel free to hit the button below!
Clay Support
APP
·
·
Siddhant Bhansali (Certified Clay Expert) clicked 'Talk with the team!'
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)
Siddhant B.
·
·
https://app.clay.com/workspaces/685360/workbooks/wb_0szl7g4E96GrGgZZiFm/tables/t_0szl7gjRhWTvJwCEboA/views/gv_0szl7gj87wnHpYQEih3
Siddhant B.
·
·
Just in case it wasn't clear - its not possible for me to even create a NEW Lookup table because no table options appear in the dropdown!! The client workflow is completely blocked.
Kashif J.
·
·
Hi Siddhant, I'll look into exactly what is causing this behaviour further, but for now, I believe if you use the "test1-apikey" key in your lookup rows columns, you should be able to get the columns to work as expected. Let me know if this helps, or if you have any further questions.
Kashif J.
·
·
Siddhant - Sorry for this, it looks like we've got a bug on our hands. I've escalated this to our engineering team to help look into it. We'll follow up here as soon as we know more! For context, this isn't expected behaviour after a user has left a workspace and we're looking at exactly why your workflows seemed to have stopped behaving as expected.
Siddhant B.
·
·
😭 But thanks for looking into this.
Siddhant B.
·
·
BTW - its happened to me once before with another workspace, but I was able to edit the Lookup table enrichment at that time. It was a while back, so dont remember the details.
Kashif J.
·
·
Let me know if the API key mentioned above is working for you. The deleted user's API key not working is expected, but that a new replacement created by you is also not working is not expected.
Siddhant B.
·
·
sid-clay-api-key-2: already existed (22/Sep) - didn't work (the one with my email address): created today after this whole issue - didn't work either
Kashif J.
·
·
Yes, that's exactly what the bug report covers. However, I tested the API key "test-apikey1" and it seemed to be working correctly. I wanted to check whether you were able to use this key to unblock yourself and continue with your workflows!
Siddhant B.
·
·
Interesting - I didnt realize you were talking about "test-apikey1". It appears to be different from the other two I was referring to. This one seems to work, but... why?? 🙂 [Not complaining, just curious!]
Kashif J.
·
·
That's what we're currently looking into, and we'll hopefully be back to you with an answer soon! Hopefully we can get to the bottom of this soon, but in the meantime I think that API key should allow you to use your columns normally :)
🙏1
Kashif J.
·
·
Hi Siddhant, To be able to use your own API key again, I'd recommend that you firstly regenerate your existing key, by going into your account settings:
And then entering this new regenerated key into your Clay API connection, in the connections menu. Give this a try and let me know if it solves the issues you've been facing here!

Clay Support
APP
·
·
Hi there, thanks so much for sharing this! We’ll be passing your feedback along to our product team, and any additional context you can provide will help us prioritize with your needs in mind as we shape the roadmap.
Want to chat with someone on the team? Feel free to hit the button below!
Clay Support
APP
·
·
Siddhant Bhansali (Certified Clay Expert) clicked 'Talk with the team!'
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)
Siddhant B.
·
·
https://app.clay.com/workspaces/685360/workbooks/wb_0szl7g4E96GrGgZZiFm/tables/t_0szl7gjRhWTvJwCEboA/views/gv_0szl7gj87wnHpYQEih3
Siddhant B.
·
·
Just in case it wasn't clear - its not possible for me to even create a NEW Lookup table because no table options appear in the dropdown!! The client workflow is completely blocked.
Kashif J.
·
·
Hi Siddhant, I'll look into exactly what is causing this behaviour further, but for now, I believe if you use the "test1-apikey" key in your lookup rows columns, you should be able to get the columns to work as expected. Let me know if this helps, or if you have any further questions.
Kashif J.
·
·
Siddhant - Sorry for this, it looks like we've got a bug on our hands. I've escalated this to our engineering team to help look into it. We'll follow up here as soon as we know more! For context, this isn't expected behaviour after a user has left a workspace and we're looking at exactly why your workflows seemed to have stopped behaving as expected.
Siddhant B.
·
·
😭 But thanks for looking into this.
Siddhant B.
·
·
BTW - its happened to me once before with another workspace, but I was able to edit the Lookup table enrichment at that time. It was a while back, so dont remember the details.
Kashif J.
·
·
Let me know if the API key mentioned above is working for you. The deleted user's API key not working is expected, but that a new replacement created by you is also not working is not expected.
Siddhant B.
·
·
sid-clay-api-key-2: already existed (22/Sep) - didn't work (the one with my email address): created today after this whole issue - didn't work either
Kashif J.
·
·
Yes, that's exactly what the bug report covers. However, I tested the API key "test-apikey1" and it seemed to be working correctly. I wanted to check whether you were able to use this key to unblock yourself and continue with your workflows!
Siddhant B.
·
·
Interesting - I didnt realize you were talking about "test-apikey1". It appears to be different from the other two I was referring to. This one seems to work, but... why?? 🙂 [Not complaining, just curious!]
Kashif J.
·
·
That's what we're currently looking into, and we'll hopefully be back to you with an answer soon! Hopefully we can get to the bottom of this soon, but in the meantime I think that API key should allow you to use your columns normally :)
🙏1
Kashif J.
·
·
Hi Siddhant, To be able to use your own API key again, I'd recommend that you firstly regenerate your existing key, by going into your account settings:
And then entering this new regenerated key into your Clay API connection, in the connections menu. Give this a try and let me know if it solves the issues you've been facing here!