I use HubSpot and have the Clay integration setup. When creating objects (contacts), some of them won't "create" but do not produce an error. It attempts to run and then appears to time-out and defaults back to "Click to run". Why would some contact objects be created and others wouldn't? Also, why won't it produce an error so I can diagnose the issue?
When contacts appear to time-out and revert to "Click to run" without errors, this typically indicates a run condition issue rather than a true failure.
Common causes:
• Run conditions not met - The action may be configured with conditions that aren't satisfied for certain rows, causing the system to skip execution
• Missing required data - If the email address or Contact ID field is empty for some rows, the action won't execute [1]
• Duplicate prevention - If you're using conditional runs to avoid duplicates, contacts that already exist in HubSpot may be skipped [2]
To diagnose:
Check if run conditions are set on your HubSpot column - click the "explain" button to see why conditions weren't met
Verify that all required fields (email or Contact ID) contain valid data for the rows that won't create
Review your workflow configuration to ensure conditions align with your requirements
If you need further help troubleshooting, click "Talk to a person" for human assistance.
Did that answer your question?
If you still need help with the contact creation issue or have more questions, I’m here to assist. Would you like to provide more details about what you’re trying to resolve or understand?
I have no run conditions to create the object
The only required field is that I select the object type (i.e. Contact). Confirmed it is selected and that this column is working for most of the column.
Reviewed and same conditions for other "create object" cells apply
Since the "Create Object" action is working for most rows but timing out on others without errors, this suggests the issue may be with the specific data in those rows rather than your configuration.
For HubSpot contact creation, the action requires either an Email Address or HubSpot Contact ID as input. [1] Even though object type is the only field you configure in the action settings, the underlying data being passed must include valid email addresses or contact IDs.
Check these for the failing rows:
• Verify the email field contains valid, properly formatted email addresses
• Ensure there are no empty cells in the email column for those specific rows
• Look for any special characters or formatting issues in the email data
If the data appears correct and the issue persists, click "Talk to a person" for human assistance to investigate the specific rows that are timing out.
The "Create or Update Contact" action requires either an Email Address or HubSpot Contact ID as input. [1] If your rows lack both fields, the action cannot execute.
For contacts without emails, you'll need to provide an existing HubSpot Contact ID instead. If you're creating entirely new contacts without either identifier, this won't work through the standard create action.
To troubleshoot the specific rows failing:
• Verify each row has either a valid email OR an existing Contact ID
• Check for formatting issues in the email/ID fields
• Ensure the column mapped to "Email Address or Hubspot Contact Id" contains data for those rows
If valid data exists and rows still time out, click "Talk to a person" for help investigating the specific failures.
Is that what you were looking for?
https://app.clay.com/workspaces/730475/workbooks/wb_0t4n34rbragj4hSbuRg/tables/t_0t4n34rNk6YJ9EVTPGS/views/gv_0t4n34rMo9Y2thJRvqP The "Create Contact" is not running for the records that say "Click to run" (just spins and reverts back to "Click to run")
Hi John - you'll notice a red alert icon in a bunch of your columns (attaching a small sample of them below). The parent column from which these columns have been extracted seems to have been deleted. These column won't map correctly in your hubspot "Create Contact" column because of this. You'll have to recreate these columns and then remap the newly created columns in the Create Contact field mapping for the enrichment to work correctly. Please try this and let us know if it helps solve the issue here. Thank you!
Hello Yash, the reason the columns get deleted is because Clay puts a cap on how many columns I can have. What's the best way to deal with this (i.e. if I don't delete the waterfalls, I can't run additional enrichments)? Thanks!
Ah I see. Yeah that makes sense in terms of column limit conservation. So before you delete the waterfall, I would duplicate the waterfall output columns so they are their own standalone columns. They no longer depend on the waterfall. Then if you delete the waterfall and the final outputs columns attached to the waterfall, you'll be good.
Another alternative is to send the waterfall final output columns along with any other data you need to to create a hubspot contact into a separate clean table using the send table data action.
Ok, I like the send table idea (learned about this after I already began working on this table). Thanks for explaining
Yeah this is what we generally recommend to stay under the column limit. One table for enrichment actions/ orchestration. Separate table for writing back to CRM/ email sequencer - sending data out of Clay.
Ok, sounds good, I'm all set
Sweet! I will go ahead and close this conversation now but please feel free to reach out if you need help in the future - thank you!
