Issues with Missing Updated At Field in Clay Table for HubSpot Integration

Sean M. · 2025-02-27 16:37:53.721617+00

Is there any specific reason why I should expect to not see the Clay-created "Updated At" field from my , despite seeing the "Created At" field? I'm trying to use the "Updated At" field from the Clay row to import that specific date/time into a HubSpot Contact property.

Issues with Missing Updated At Field in Clay Table for HubSpot Integration | Clay

6 comments

· Sorted by Oldest

Sean M.
·
·
https://app.clay.com/workspaces/88408/workbooks/wb_X83oaUHmXcNa/tables/t_rSQ7r2SpsCbq/views/gv_Xxx86ucmsiKw
Channeled
APP
·
·
To successfully import date/time fields from Clay to HubSpot, there are a couple of important points to consider: 1. Date formats need to be compatible with your CRM. For dates to work properly, they should follow Unix time set to midnight. 2. You'll need to normalize the date format using the Format Date/Time formatter in Clay. Select Unix Timestamp as your output format, and keep the column type as text rather than date format to avoid formatting issues. 3. It's crucial to match the data type in your Clay table with the corresponding field type in HubSpot. Double-check the field types in your CRM to ensure successful data transfer, as the export will fail if the data types don't match. If you're still unable to see the "Updated At" field after implementing these changes, you may want to explicitly request human support to investigate your specific setup.
Source: Hubspot integration overview | Documentation | Clay University
Channeled
APP
·
·
Is that what you were looking for?
Sean M.
·
·
No - it's not a formatting issue, but rather the field not showing at all.
Channeled
APP
·
·
Looks like you're still looking for help.
If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!
Bo (.
·
·
Hi Sean, That's normal behavior in Clay. The "Updated At" field isn't available to reference directly because it would create an infinite loop - each time you'd reference it, the row would update, which would change the "Updated At" value, triggering another update. If you need to track when a row was last modified for your HubSpot import, you might want to create a custom date field with a formula. That'd be done like this: 1. Create a formula, reference a column and ask when was this last updated. 2. This will return right now but then every time you'll update it, you'll get the recent date. Let me know if you need any other help with this!

Sean M.
·
·
https://app.clay.com/workspaces/88408/workbooks/wb_X83oaUHmXcNa/tables/t_rSQ7r2SpsCbq/views/gv_Xxx86ucmsiKw
Channeled
APP
·
·
To successfully import date/time fields from Clay to HubSpot, there are a couple of important points to consider: 1. Date formats need to be compatible with your CRM. For dates to work properly, they should follow Unix time set to midnight. 2. You'll need to normalize the date format using the Format Date/Time formatter in Clay. Select Unix Timestamp as your output format, and keep the column type as text rather than date format to avoid formatting issues. 3. It's crucial to match the data type in your Clay table with the corresponding field type in HubSpot. Double-check the field types in your CRM to ensure successful data transfer, as the export will fail if the data types don't match. If you're still unable to see the "Updated At" field after implementing these changes, you may want to explicitly request human support to investigate your specific setup.
Source: Hubspot integration overview | Documentation | Clay University
Channeled
APP
·
·
Is that what you were looking for?
Sean M.
·
·
No - it's not a formatting issue, but rather the field not showing at all.
Channeled
APP
·
·
Looks like you're still looking for help.
If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!
Bo (.
·
·
Hi Sean, That's normal behavior in Clay. The "Updated At" field isn't available to reference directly because it would create an infinite loop - each time you'd reference it, the row would update, which would change the "Updated At" value, triggering another update. If you need to track when a row was last modified for your HubSpot import, you might want to create a custom date field with a formula. That'd be done like this: 1. Create a formula, reference a column and ask when was this last updated. 2. This will return right now but then every time you'll update it, you'll get the recent date. Let me know if you need any other help with this!