Clay Icon

Bulk Update HubSpot Records Based on Condition Without Auto Update

Β·
Β·

team quick question - so the logic I'm trying to set up is this: When Clay returns no profiles for a company, I want to update a field on Hubspot to indicate its not been found - for this I have set up a hubspot update company column and configured the field to update etc and set auto update to off Now 100 records have this condition met - which means I'm having to manually click on each record for it to update Is there a way I can do a coniditonal bulk operation? Without having the auto update ON and prevent 1000 odd records from re reunning? thanks so much! πŸ™‚

  • 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 Muhammad S.
    Muhammad S.
    Β·
    Β·

    Yes, you can. Set a run condition for HubSpot column to run only if enrich person is empty OR any field within enrich person is empty like linkedin url and you should be good

  • Avatar of Muhammad S.
    Muhammad S.
    Β·
    Β·

    When the profile gets enriched the URL is returned by the enrichemnt, the hubspot column will check if the URL was returned OR not and it will run based on that.

  • Avatar of Bo (.
    Bo (.
    Β·
    Β·

    Hey, thanks for reaching out! 😊 Yes, Muhammad is correct! Adding a conditional formula to the enrichment will allow it to run only when certain conditions are met. If you prefer not to activate auto-update, you can manually run it by going to the column header, clicking Run column, and selecting Run all rows that haven’t run or have errors. Let me know if you need any further help with this! 😊

  • Avatar of Shwetha R.
    Shwetha R.
    Β·
    Β·

    thanks simple_smile

  • Avatar of Channeled
    Channeled
    APP
    Β·
    Β·

    Hey there - just wanted to check in here to see if you needed anything else! Feel free to reply back here if you do.

  • Avatar of Shwetha R.
    Shwetha R.
    Β·
    Β·

    hi team - the email waterfall used to auto update the work email field - now even when an email is identified it isnt getting updated final people table there are ~3220 records where work email is empty - but some should have been updated because an email address was found - thanks!

  • Avatar of Shwetha R.
    Shwetha R.
    Β·
    Β·

    https://app.clay.com/workspaces/243239/workbooks/wb_nUk3RQ7zb3NQ/tables/t_obomcDE6oBWq/views/gv_TXN33S8exbuj - this is the table with the filters ON 2817 records need to have the work email updated (ie for cases that actually have returned an email) how can I fix this column?

  • Avatar of Daniela D.
    Daniela D.
    Β·
    Β·

    Hey Shwetha! Thanks for reaching out. Happy to help. Here's an explanation for how the email waterfall validation works: The email waterfall gives you the option to add a validation provider to check results from each email finder (Zerobounce in your table). When the validation tool determines the email is invalid, the next email finder tries to find a new one, but if it finds the same email as the previous column it won't try to validate it again because it already tried to validate once before, and this could result in no final output because none of the emails returned were valid. We automatically hide validation columns helping keep tables clean and that's why it's not evident at first glance. Let me know if you still have any questions though! Also sharing an example and explanation video: https://www.loom.com/share/e79acd92841a4706b1710c4ce1bddaa4 Let me know if this helps!

  • 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 Shwetha R.! This thread was recently closed by our Support team. If you have a moment, please share your feedback: