I see, thanks for the info, Daniel. I have to say none of those things make any difference to my workflow. Although I’m not sure I understand what you mean by “save config” for callbacks.
If I had to pick one thing I’d like changed, it would be (native) support for objects and lists.
I think Airtable does a decent job of balancing having a simple interface while still allowing technical users to write scripts and other more advanced features. Also, the way that columns and views are managed in their UI is something I dearly miss in Clay. For example, if you have multiple views, every time you add a column, it gets added to all the views. And you have to manually edit the visibility and order of columns in each of the individual views, which is a pain.
Sorry for the rant I just have I have a bit of a love/hate relationship with Clay 😅. And, unfortunately, I don’t see a roadmap that will improve my experience but that’s probably because the way I use it is atypical