Need to trigger a workflow when a custom column updates

Smart CRM & Sales Hub CRM
1

I need to trigger a workflow when a custom column updates, I would really rather like an external POST webhook to tell the app to trigger a notification, but it did not work. So the alternative is trying to

"has completed: property value changed, contains {

But seems to not do that I would like either

2

Hey @neatdevrefactor, thank you for posting in our Community!

To trigger a workflow when a custom column updates in HubSpot, set the enrollment trigger to “Property value changed.” This should help you start the workflow when the custom column updates. If you prefer using an external POST webhook and it doesn’t work, ensure your webhook URL is correct and accessible.

To our top experts @Anton and @danmoyle do you have any recommendations for @neatdevrefactor?

Thank you,

Pam

3

Thanks for the tag @PamCotton. I agree with Pam, setting a trigger for when a property is updated seems like the logical answer, @neatdevrefactor. Do you mean custom property when you’re describing a column being updated? You wouldn’t be able to have a workflow for a column, as that’s just a “view.” But in that column is its property, which would work.

Here’s a little more detail that might help unlock what you’re looking for.

You could create a custom object-based workflow:

  • Create a “custom object-based workflow”
  • Set the trigger to be when a specific custom property “is known”
  • Enable re-enrollment for when that property changes

This allows the workflow to trigger each time the custom property value changes. However, there are some limitations:

  • You can’t easily trigger on any field change - you have to specify individual fields
  • Some fields like “Object last modified date/time” can’t be used for re-enrollment

Alternatively, you could use a webhook trigger (Operations Hub Professional/Enterprise only):

  • Set up a webhook event as the workflow trigger
  • Send a POST request to the webhook URL when your external system updates the custom property
  • Map the webhook data to HubSpot properties

This allows an external system to trigger the workflow, but requires Operations Hub.

Here’s a possible workaround using lists and date stamps:

  • Create a list using custom object fields
  • Use list membership to create a date stamp on a contact
  • Use that date stamp field as the workflow trigger

This is a more complex workaround but may work in some cases.

To improve your current setup, you may want to:

  1. Ensure you’re using a custom object-based workflow if possible
  2. Specify individual important fields as triggers rather than trying to catch all changes
  3. Consider upgrading to Operations Hub if webhook triggers are critical
  4. Explore workarounds using lists and date stamps if needed

Hope that helps!