3件の承認済みベストアンサー
You can definitely enroll based on a property update, just set the enrollment to "Call and meeting type" is known. This will trigger every time the property has been updated. The trickier piece is that you don't want to be notified the first time a value gets added. There's a few ways to do this, are you using calls or if this is a contact property? You could say something like "call date is more than 1 day ago & call and meeting type has been updated in the last 1 day"
If you're using contact properties for this you could use a custom property to get around notifying the first time. Set up a custom property with some thing like "is first value?" or whatever you want to call it. It could be like a single checkbox. I would enroll contacts in the workflow based on the call meeting type property being updated. Then branch on the "is first value" being known or unknown. If it's unknown the branch just checks that checkbox and does nothing. If it is known the known branch triggers a notification to you.
| | Tom Mahon |
-1.jpeg?width=160&height=38&name=Baskey-Logo-%20%281%29-1.jpeg){kind=logo}
 | Did my post help answer your query? Help the community (and me) by marking it as a solution. |
Hey @AStretten there's no way to do that unfortunately. I wish there was though!
It may be possible by pinging the get all contacts api and using the value and history query within it:
I'm not sure if this returns the user who edited it though but worth a shot!
| | Tom Mahon |
| | Did my post help answer your query? Help the community (and me) by marking it as a solution. |
Hi @AStretten , you’ve already hit the core limitation, and Tom is right about it. HubSpot does store “updated by” in property history, but that metadata is not queryable in workflows and can’t be used as an enrollment condition or filter. That’s a platform constraint, not something you’re missing.
The workaround HumbleTinker shared is honestly about as good as it gets natively. Using associated Meeting properties like “Updated by User ID” in a notification is one of the very few places where HubSpot surfaces that information in a usable way. It won’t give you perfect governance or historical reporting, but it does give near-real-time visibility and a human-readable trail. For deeper auditing, the only fully reliable place is still the record’s History view. HubSpot confirms that property history is view-only and not exposed for automation logic (https://knowledge.hubspot.com/records/view-record-property-history )
If you need something more systematic, the only real path is outside workflows. The CRM APIs do return property history, including timestamps and user IDs, but you’d need to poll or subscribe externally and store that data yourself, then trigger alerts from there (https://developers.hubspot.com/docs/api/crm/understanding-the-crm).
Small disclosure since I’m close to this: I work on Stacksync, and one pattern we see teams use is syncing record changes and property history into a warehouse or logging system, where “updated by” becomes queryable and alertable without fighting HubSpot workflow limits. Not a HubSpot-native fix, but it closes the audit gap cleanly.
Hope this helps set expectations and options a bit more clearly.
Did my answer help? Please mark it as a solution to help others find it too.
 | Ruben Burdin HubSpot Advisor Founder @ Stacksync Real-Time Data Sync between any CRM and Database |
 | |
You can definitely enroll based on a property update, just set the enrollment to "Call and meeting type" is known. This will trigger every time the property has been updated. The trickier piece is that you don't want to be notified the first time a value gets added. There's a few ways to do this, are you using calls or if this is a contact property? You could say something like "call date is more than 1 day ago & call and meeting type has been updated in the last 1 day"
If you're using contact properties for this you could use a custom property to get around notifying the first time. Set up a custom property with some thing like "is first value?" or whatever you want to call it. It could be like a single checkbox. I would enroll contacts in the workflow based on the call meeting type property being updated. Then branch on the "is first value" being known or unknown. If it's unknown the branch just checks that checkbox and does nothing. If it is known the known branch triggers a notification to you.
| | Tom Mahon |
| | Did my post help answer your query? Help the community (and me) by marking it as a solution. |
Hey @AStretten there's no way to do that unfortunately. I wish there was though!
It may be possible by pinging the get all contacts api and using the value and history query within it:
I'm not sure if this returns the user who edited it though but worth a shot!
| | Tom Mahon |
| | Did my post help answer your query? Help the community (and me) by marking it as a solution. |
