Clay Icon

Managing Row Limits in CRM Automation: Solutions and Strategies

ยท
ยท

Hey! I saw in the Slack Channel that the row limit is 50k rows per Table. So right know we have an automation in place that pulls leads from our CRM, pushes it to clay and clay pushes it back into our CRM with the enriched data. But we got more that 50k Leads in the CRM so the row limit would be extended even before the whole CRM got enriched. What would be the best solution here? Is there a way to automaticly push the data to another table when this table is full? I saw at the pricing page that there is a feature named "Unlimited rows (API)" is this our only solution here? Really dont need all the other stuff on enterprise, just more rows. So would be great to not have to buy it just for the feature. Anyone ever got the same situation and could help me out?

  • Avatar of Channeled
    Channeled
    APP
    ยท
    ยท

    ๐Ÿ’ค 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!

  • Avatar of Tom W.
    Tom W.
    ยท
    ยท
  • Avatar of Muhammad S.
    Muhammad S.
    ยท
    ยท

    You will need to have another table receive data from CRM and keep distributing it to multiple tables for enrichment so you do not overload one table.

  • Avatar of Bo (.
    Bo (.
    ยท
    ยท

    Hey Tom, thanks for reaching out! ๐Ÿ˜Š Yes, Enterprise is definitely your best option here. The only alternative would be to use multiple different tables and segment your HubSpot data that way. Let me know if you need more details or have any questions!

  • Avatar of Channeled
    Channeled
    APP
    ยท
    ยท

    We haven't heard back from you in a bit, so we're going to go ahead and close things out here - feel free to let us know if you still need something!

  • Avatar of Channeled
    Channeled
    APP
    ยท
    ยท

    Hi Tom W.! This thread was recently closed by our Support team. If you have a moment, please share your feedback: