Dominic G.

Feedback/Idea -- a big pain point is merging lists into Salesforce. For example if we go to an event and get a lead list, some will exist already, some will not, and then ones that do exist will have varying levels of data quality so a simple email lookup might not always work. If there's a way for clay to hook into salesforce's dupe prevention rules that would be amazing. They always find the right contact ID right after I hit run on the create contact column. So concretely -- it might be a Salesforce function "Lookup Record Using Fuzzy Matching/Duplicate Rules" that returns the ID using fuzzy lookup. This would be incredible IMO

what is the functions feature that Eric is talking about here?

Question -- is it possible to save sets of columns/enrichments for quick use across multiple Clay tables? e.g. I have a set of columns that merges a contact list into Hubspot by first checking if the contact & account already exists, and then uses Apollo to enrich data to then create any Contacts/Accounts that don't already exist. I use this semi-frequently across multiple tables & use cases. What is the best practice to make reusing this set of columns quick and easy?

I'd love to be able to import Users from Hubspot to help me build tables for understanding who is assigned to which records, run round robins etc. As the screenshot shows I can only see Company/Contact/Deal/Lead objects available