Organizing HubSpot Data: Best Practices for Clay Enrichment Tables | Clay

Organizing HubSpot Data: Best Practices for Clay Enrichment Tables

·

·

Hi! I’m pretty new to Clay - I’ve spent the last month playing around with enriching companies, finding what works best for my exact use case. The tables I’ve created are pretty messy - tons of different enrichments in 1 table. I’m now trying to make this into a more scalable process, so trying to figure out the best day to organize tables within a workbook. Some context: for this workbook (for right now at least) the source I’m starting with is imported companies from HubSpot - and the goal is to update existing companies in HubSpot with each piece of enriched data. All of the enrichments I’m running are dependent on having the company domain (about half of the companies already have domains, and the other half I need to find them as step 1). I think I’m going to start with the 'source table' of companies imported from HubSpot and add all of the relevant HubSpot properties [that I will need to reference for enrichments later] as columns so I can easily write to other table as needed. Then create a separate table for each enrichment (lets call these 'enrichment tables'), where I will write to table a 'key' (HubSpot company ID), domain, and other relevant properties needed for that specific enrichment. If my goal is to update a HubSpot property with each of these enriched data points from each enrichment table, do you recommend adding the enrichment column "Create or Update HubSpot Company" individually on each of the 'enrichment tables', OR writing to table all the final (enriched, clean) results to a separate table ('final table' that has ONLY the final result columns for the different enrichments) and updating the HubSpot update all properties at once? I'm not exactly sure how often I am going to want this data to be refreshed in Clay - it's possible that I will want some enrichments to refresh more often than others - if that changes anything.

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!
Bo (.
·
·
Hi Eden! 😊Can you tell me more about those enrichments? It's great to see you’re putting in the effort to create a more scalable process with Clay! Based on the info you shared: 1. Start with Your Import Table: You don’t need to add all HubSpot properties as columns right away. Just import your companies from HubSpot into this table. 2. Enrich Companies in the Same Table: Perform the necessary company enrichments directly in this table, especially since half of your companies already have domains. This will keep things simple and organized. 3. Separate Table for People (If Needed): If you also need to enrich data related to people, move that process into a new, separate table. 4. Export Back to HubSpot: Once your enrichments are done, you can export the updated data back from these tables into HubSpot. While there are many ways to structure this, the 1-2-3-4 approach above is the most straightforward and avoids unnecessary complexity. Some users might separate enrichments into new tables when things get more complex, but starting simple often works best. You’re doing great with this! If you need further clarification or want to explore other options, feel free to reach out. 😊
Eden G.
·
·
Bo (. thank you for getting back to me so quickly! Could I share you on a table where I did all of the enrichments in 1 table (import, enrich, export) so you can see if it would be worth separating out? I found that when I went to go back to reference certain things, it was difficult to find the right column as there were 60 different columns
Bo (.
·
·
Of course! Please send me the URL, and I’ll take a look. 😊
Jonny C.
·
·
Idk why you want to make separate tables for each enrichment, just run them all in one with filters
Channeled
APP
·
·
Hi Eden G.! This thread was recently closed by our Support team. If you have a moment, please share your feedback: