im attempting to push new contact records into Hubspot from a Clay table but im getting 'run condition not met'. everything appears to match how I've done this in the past. any easy way to get a more specific reason as to what condition is not being met?
To determine why you're getting a 'run condition not met' error, check these key areas:1. Data Type Matching: Ensure the data types in your Clay table columns match the corresponding field types in Hubspot. Mismatched data types will cause the export to fail. 2. Run Conditions: Check if you have any specific formulas set up that trigger the column. The action will only run when these formula conditions are true. You can review your formulas in the column settings. 3. Required Fields: Verify that all required Hubspot fields are properly mapped and contain valid data.For a cleaner troubleshooting process, you can:** Create a test export with a smaller dataset ** Double-check your field mappings * Confirm that your data formats align with Hubspot's requirements Sources: Hubspot integration overview | Documentation | Clay University Download as a CSV [Clay 101] - Clay University
To resolve the 'run condition not met' error when pushing contacts to Hubspot, check these key areas:1. Data Type Matching: Ensure your Clay table column data types match the corresponding Hubspot field types. Mismatched data types will cause the export to fail. 2. Field Mappings: Verify that you've correctly mapped your Clay table fields to the corresponding Hubspot properties. 3. Run Conditions: If you've set up specific formulas to trigger the action, the action will only run when these formula conditions are true. Review your column settings to check any conditional formulas.For easier troubleshooting:** Create a test export with a smaller dataset ** Double-check your field mappings * Note that integration fields showing "run condition not met" will appear blank in CSV exports Sources: Hubspot integration overview | Documentation | Clay University Download as a CSV [Clay 101] - Clay University
Hey there David thanks for reaching out, David - Do you mind sending the link to the table so we can take a look? https://downloads.intercomcdn.com/i/o/1171717996/ac7729f84b426e1d0358af02/image.png?expires=1735668000&signature=c916b9eecd8d9fdc94f9abd71f9b4384a51b706bc7eb6087736b581eac5135a3&req=dSEgF85%2FmohWX%2FMW1HO4zYTywS76AJ8W2BKsam%2FhVPsi4Q%3D%3D%0A
Hey there David taking a look at this the reason this occurring is due to the run conditions you have setup, that is not allowing these rows to run since they do not meet the listed requirements. https://downloads.intercomcdn.com/i/o/w28k1kwz/1317163885/bf26cd6f4887e1f1a3c93e23573f/image.png?expires=1735668900&signature=a5ea7f45453c5e1b2c60fa893db501ac1f32f7dab9a718a3f47c6eea135fdc28&req=dSMmEch4nolXXPMW1HO4zb%2FFWZf1ZtBDk5hXKHyBKC2Un7q1CtLQkyYcfq1C%0AOw04%0A
we got it to work. Something on our end broke when the Clay <>Hubspot integration was updated. its working now, thanks!
.png&w=3840&q=75){kind=logo}
