Jeremy R.

Ok. What do folks discuss in “discuss anything”? :)

Thanks Muhammad! There’s no pricing, though. I likely won’t be applying this to Clayground. Just giving away access.

Ok. I’ll change it from “Error monitoring in Clay is finally possible” to “Error monitoring is finally possible with your Clay data (not a native feature)”

You’re right, it’s not native. I built a tool that monitors a Clay workspace for errors. Other things it can do:

Use https://datagen.dev inside Clay

The only problem with certs based on tables alone is that anyone can chat with sculptor to get a table in a few minutes that will pass. Also they could easily submit templates from a LinkedIn post.

I agree with Jordan that the salary should frame higher and that Clay should lead the charge.

I’d rather Clay change the monthly cost over the API. Otherwise, first it’s APIs… next it’s webhooks… then limited numbers of tables… etc. Hey, Clay: “Free” API calls are a massive draw! Customers need a firm base like that to experiment with—which leads to more usage and likely expands their downstream credit spend (bc they’re manipulating more and more data).