.png){kind=logo}
Improving Clay's Lookup Functionality to Enhance Business Processes
We have a big issue with Clay affecting our business:
We're trying to not send emails from Clay table A to people who already replied (the replies end up in another table B) and are trying to lookup using the native Clay lookup column types (Lookup Single Row or Lookup Multiple Rows in Another Table):
If the lookup doesn't run - it stays as empty string
But if the lookup runs and doesn't find anything - it returns empty string AS WELL
^^^ hence the issue -> if we compare for an empty string - we'll still send emails to people who already replied because Clay will simply bypass the check, sending before the lookup runs.
If the lookup runs and finds a row - it returns an object
Could Clay quickly implement the following functionality:
If it doesn't run - it stays empty
If it runs but doesn't find anything - it returns an object, but with "found": false for instance
if it runs and finds something - it returns "found": true + the data of the row.
This would save our day🙏🙏🙏 Thank you!