Trigger Workflow on a Customer object property added/created

[TitoRippin51]

How to trigger a Workflow when a Contact property was added/created? I found only instructions how to trigger on an existing property value change, but not when the Contact schema itself changed (someone added a new property on the Contact object).

Also, this could be avoided if Hubspot would allow to change permissions on different users what objects they may edit. In our situation we have Hubspot users from Marketing, Sales, Customer Success departments, besides developers, who are allowed to edit Contact. The only plausible solution I found was described here: https://community.hubspot.com/t5/HubSpot-Ideas/Restrict-users-from-Creating-new-Properties/idc-p/103...

suggesting to trigger an email notification to the Admin or a SuperAdmin about the newly added Customer property and mentioning the user who done that. Ugly workaround, but that would work for us for now. But I can't find how to trigger a Workflow on a Property added, not changed.

[karstenkoehler · Accepted solution]

Hi @TitoRippin51,

It's not possible to do this, there aren't property-based workflows, only contact-based workflows which reference existing properties.

Generally, in Enterprise portals, I'd limit "Edit property settings" permissions to a very small circle of people, I would typically not leave that to individual contributors. Currently, beyond this one settings, there aren't any ways to further limit which objects someone can create properties on.

You could request this in the HubSpot Ideas section of the community: https://community.hubspot.com/t5/HubSpot-Ideas/idb-p/HubSpot_Ideas

Best regards!

[MHolzer · Accepted solution]

Again, for my liking, instead of saying something is not possible we can just say its only possible with creativity + a developer! 🙂

but yea this idea is still mad:

https://developers.hubspot.com/beta-docs/reference/api/crm/properties#post-%2Fcrm%2Fv3%2Fproperties%...

idea thought process:
if you have 100 properties created and you schedule the workflow daily to see if one has been added
by first creating like a list of properties that are there and if you then log 101 you know someone created this new one you can prob then get the internal name of the property and the user who created it so yea

something like this could prob work...

but like karsten told you without a devolper probably not feasible

[MHolzer · Accepted solution]

Again, for my liking, instead of saying something is not possible we can just say its only possible with creativity + a developer! 🙂

but yea this idea is still mad:

https://developers.hubspot.com/beta-docs/reference/api/crm/properties#post-%2Fcrm%2Fv3%2Fproperties%...

idea thought process:
if you have 100 properties created and you schedule the workflow daily to see if one has been added
by first creating like a list of properties that are there and if you then log 101 you know someone created this new one you can prob then get the internal name of the property and the user who created it so yea

something like this could prob work...

but like karsten told you without a devolper probably not feasible

[TitoRippin51]

Thank you @MHolzer , looks like that's our way to go...

[karstenkoehler · Accepted solution]

Hi @TitoRippin51,

It's not possible to do this, there aren't property-based workflows, only contact-based workflows which reference existing properties.

Generally, in Enterprise portals, I'd limit "Edit property settings" permissions to a very small circle of people, I would typically not leave that to individual contributors. Currently, beyond this one settings, there aren't any ways to further limit which objects someone can create properties on.

You could request this in the HubSpot Ideas section of the community: https://community.hubspot.com/t5/HubSpot-Ideas/idb-p/HubSpot_Ideas

Best regards!

[TitoRippin51 · Accepted solution]

Thank you, I created an idea. Hopefully it will reach the product team.
https://community.hubspot.com/t5/HubSpot-Ideas/Trigger-a-Workflow-on-a-new-Object-Property-added/idi...