Hi I wonder if there is a size limit on the table if we continues to import leads into one. In addition, if somehow a same person is imported (through webhook) again into the existing table, it will not create a new row and consume credits right?
💤 You've caught us outside of our support hours (9am-9pm EST), but don't worry - we'll be back in touch within 24 hours (often sooner!). If you haven't already, please include the URL of your table in the thread below so that we can help you as quickly as possible!
Thanks for jumping in Muhammad! Hey Jinghang! That's correct. The current table limit is 50k, and if you have auto-dedupe enabled, it will delete any duplicate entries as they are added to the table. You can enable this at the bottom of your table (see screenshot below). Let me know if this helps! https://downloads.intercomcdn.com/i/o/w28k1kwz/1217766913/536b06049f7ebe5f4e9785884b78/CleanShot+2024-10-16+at+10_37_12%402x.png?expires=1729073700&signature=d0293ed34105a3a0e56e74a9528365dd20507ef347b1a9482347783cfec986b6&req=dSImEc54m4heWvMW1HO4zZhiJVCyI3htZI1119JU2NqCIjQRqmA5CO7nVTD5%0AKPAs%0A
What happens when it reach 50k? First in first out? Or simply cannot be added anymore?
Hey! Thanks for. the message. When the table reaches the 50k limit, you won't be able to add more rows. Can you share a bit more info about the workflow you're trying to implement? Happy to share suggestions.
We will try to enrich our leads from crm (hubspot for example) and the total number will continue to grow. If we continue to import into clay table, it might reach 50k limit. What’s the best practice to achieve this?
Thanks for the reply! Here's what I recommend for your workflow. In Hubspot, you can create lists for records in your CRM and split them based on specific criteria. If you have access to Hubspot's webhook feature, those lists can be imported into separate tables (to webhooks generated in Clay), but in the same workbook in Clay. I made a quick video explaining that here: https://share.cleanshot.com/w6KHXcM2 Clay webhook docs: https://docs.clay.com/en/articles/9730014-import-data-to-clay-using-webhooks Hubspot webhook: https://knowledge.hubspot.com/workflows/how-do-i-use-webhooks-with-hubspot-workflows Create lists in Hubspot: https://knowledge.hubspot.com/lists/create-active-or-static-lists Let me know if this helps!
Splitting total contacts into different list can reduce the count a single table has. That being said, for a single table, we cannot do anything if it hits 50k, except manually deleting some of rows?
We are about to upgrade pro plan but we don’t have hubspot webhook feature. Clay has native hubspot integration, can it pull contacts from list in hubspot incrementally, i.e. when new contacts are added to a hubspot contact list, clay will automatically pull it?
Circling back to previous discussion on deduplication, what would happen if the new row indeed is an existing person based on some primary key like “Email” but with additional information? Will it be treated as a new row? If not, will the additional info be kept?
and if you have auto-dedupe enabled, it will delete any duplicate entries as they are added to the table
Hi Jinghang! Happy to assist with your questions one by one! 😊 Regarding the row limit of 50k for a single table: If you reach the limit, one solution is to segment the lists based on criteria like region (e.g., EMEA, APAC, North America) to stay within the row limit. That way, you have one workbook with all your Hubspot enrichments! On Clay automatically pulling new contacts from a HubSpot list: Yes, Clay will automatically fetch new leads added to a HubSpot list every 24 hours. You can also manually trigger a data refresh by selecting "update now" in the source column header. For more real-time updates, consider using webhooks through tools like Zapier and make.com. Regarding new rows with existing person based on a primary key like "Email" with additional information: If auto-dedupe is on, duplicates based on the primary key will be removed when importing new files. If a new row with additional info is identified as a duplicate, the extra information won't be added to the existing row to avoid redundancy. If you want to merge new info without auto-dedupe, upload the new file to a separate table and use Lookup to check for existing leads before merging. Here's a guide on using Lookup in Clay: Lookup Video. I know this is all overwhelming. Hope this info helps. Feel free to reach out again if something is unclear. You can also book a support call with our CX team here- https://meetings.hubspot.com/meet-clay/cx-support-call to discuss the solutions in detail. Have a great one!
Hi Jinghang Hu! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Thanks! We've reopened this thread. You can continue to add more detail directly in this thread.
What about the webhook? If data imported through webhook accumulates to 50k rows, what’s the best practice for this.
.png){kind=logo}
