Why does Lookup table require a "Clay" API key which is necessarily linked to a individual's account? Removing that person from the workspace breaks all the automation where they used their "Clay account" API key!
Context:
1.
A member of my team (A) had created this automation.
2.
Clay forces us to create an "Clay" API key (which I've not been able to get a clear reason why that is absolutely necessary).
3.
(A) used his key to setup this Lookup table.
4.
The team member left my company, so I removed his account from the client workspace.
5.
All automation where the key was being used broke.
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!
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!
🔗Merged conversation
This thread has been merged into your main conversation.
To keep the discussion going and see all replies, please continue in the main conversation.