Issues with Unintentional Credit Consumption in Clay

Casper S. · 2026-01-12T14:09:39.705Z

Hey Clay team 👋 We have a team of several people working in clay. People of various experience and seniority. Every now and then we face a situation in which somebody from the team accidentally triggers an enrichment that devours a copious amount of credits. Our most recent achievement in this domain is going from 70K credits to zero at the beginning of the cycle, while preparing for a massive event. Is there a way of solving this problem currently within Clay or would this be a feature request 🤔

Issues with Unintentional Credit Consumption in Clay | Clay

9 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
·
·
Casper Sulisz clicked 'Talk with the team!'
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)
Ariana (.
·
·
Hi Casper, thanks for reaching out! I'm sorry to hear about the trouble with credit spend. Can you please share the link to the table where this happened along with some details around the scenario, and I'll be able to share some more specific insights into how you can build some guardrails? In general, I suggest: 1. Keeping tables and enrichments set to run manually (auto-update off) 2. When making changes to columns, choosing Save & Don't Run then run just a few rows to make sure the output is exactly what you're looking for before choosing to run a column. We do have workspace credit controls, however they are currently an enterprise-only feature. I am happy to share feedback to the team that this would be beneficial on Pro plans as well! Let me know if this helps, or if you have any more details you can share!
Casper S.
·
·
Thanks Ariana (. I and the team understands these best practices but despite best intentions things sometimes slip Marcelina J. can you chip in here please with the exact tables?
Quentin R.
·
·
Hi there, I can confirm that we have plans to extend workbook credit limits to annual Pro plans in the near future 💪🏼
🙏1
Marcelina J.
·
·
Ariana (. here's the link to the workbook https://app.clay.com/workspaces/48942/workbooks/wb_0t5nykzh3uwHfztFc7S?sidebarAction=openCommandCenter
Ariana (.
·
·
Thanks! Which table in this workspace specifically had the issue? Also, it sounds like my colleague Quentin pointed out the best case here - which would be expanding workbook credit limits to annual Pro plans. I think this would really help your team in the future!
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
·
·
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
·
·
Casper Sulisz clicked 'Talk with the team!'
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)
Ariana (.
·
·
Hi Casper, thanks for reaching out! I'm sorry to hear about the trouble with credit spend. Can you please share the link to the table where this happened along with some details around the scenario, and I'll be able to share some more specific insights into how you can build some guardrails? In general, I suggest: 1. Keeping tables and enrichments set to run manually (auto-update off) 2. When making changes to columns, choosing Save & Don't Run then run just a few rows to make sure the output is exactly what you're looking for before choosing to run a column. We do have workspace credit controls, however they are currently an enterprise-only feature. I am happy to share feedback to the team that this would be beneficial on Pro plans as well! Let me know if this helps, or if you have any more details you can share!
Casper S.
·
·
Thanks Ariana (. I and the team understands these best practices but despite best intentions things sometimes slip Marcelina J. can you chip in here please with the exact tables?
Quentin R.
·
·
Hi there, I can confirm that we have plans to extend workbook credit limits to annual Pro plans in the near future 💪🏼
🙏1
Marcelina J.
·
·
Ariana (. here's the link to the workbook https://app.clay.com/workspaces/48942/workbooks/wb_0t5nykzh3uwHfztFc7S?sidebarAction=openCommandCenter
Ariana (.
·
·
Thanks! Which table in this workspace specifically had the issue? Also, it sounds like my colleague Quentin pointed out the best case here - which would be expanding workbook credit limits to annual Pro plans. I think this would really help your team in the future!
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!