Distinguishing Could Not Find Company from Error in Apollo Column | Clay

Distinguishing Could Not Find Company from Error in Apollo Column

I’ve got an Apollo company enrichment column and I’m trying to tell the difference between “Could not find company” and “Error” in a formula so I can send an API alert when an error occurs. Using !{{Enrich Company}} returns the same result for each outcome. Anyone have any ideas?

10 comments

Channeled
APP
·
·
👋 Hey there! Our support team has got your message - we'll be back in touch within 24 hours (often sooner!). If you haven't already, please include the URL of your table in this thread so that we can help you as quickly as possible!
Tanvi R.
·
·
Hi Matt, thanks for reaching out! Do you mind sending the link to the table so we can take a look? https://downloads.intercomcdn.com/i/o/1171717996/ac7729f84b426e1d0358af02/image.png?expires=1728427500&signature=2c795a51ab307d854eb54394107f83946a3ba36ec738721932015974cdb4fa6f&req=dSEgF85%2FmohWX%2FMW1HO4zYTywCP4BJAT2BKsam%2FhVPuB0A%3D%3D%0A
Matt L.
·
·
https://app.clay.com/workspaces/11327/tables/t_r7mny72dfZZF/views/gv_9iDmS4zASxza
Bo (.
·
·
Hey Matt, thanks for reaching out! 😊 Currently, in conditional formulas, it’s not possible to directly distinguish between “Could not find company” and “Error” messages. Both situations are treated as a false condition when using !{{Enrich Company}}. This is a known limitation, and while it’s on our radar for improvement, we don’t have a specific timeline for when this feature might be available. If you could share more about why you’re looking to detect the error message specifically, we might be able to explore some alternative solutions or workarounds for your API alert needs! 🚀
Matt L.
·
·
Okay thank you, the main reason is so that we can know when we’ve reached our daily Apollo credit limit. The API alert will stop the process that’s adding rows to the sheet but right now when there’s no company data available, it’s stopping the entire process unnecessarily.
Bo (.
·
Hey Matt, I understand the frustration, and I’m sorry for the inconvenience this causes. Unfortunately, there isn’t a way to bypass this issue right now. The good news is that our team has been looking into improving this, and it’s something they’re aiming to address in the next quarter. Thanks for your patience, and if you have any other questions or need help in the meantime, I’m here for you! 😊
Matt L.
·
·
Thank you, I appreciate it. It’d be nice to note for what ever the feature becomes, that having a function available in templates for is_error, or the ability to get the error message would be fantastic!
Bo (.
·
·
Hey Matt - Great idea, thanks for sharing this! We’re always looking to improve the product, and your feedback is super helpful. I’ve sent this over to our product team so they can evaluate it and see if it might fit into the roadmap as a future improvement.
Channeled
APP
·
·
Hi Matt L.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Channeled
APP
·
·
Thank you so much for sharing your feedback Matt L.!