The new event trigger for workflows that is currently in beta requires you to build a company workflow when looking to trigger a workflow from a property change value on the company object. This is very limiting in that the update marketing contact read more
For workflows to display on the settings>property>used in view, the field has to be specifically looking at a present, existing value for that property. In other words, the workflows are relying on checking that current value. With t read more
The enrollment date should be its own field for each workflow. I cannot look for deals created after a contact was part of a nurture workflow. I am sure there are other performance and reporting use cases this solves for. Can also help to re-enroll read more
It is infuriating that the job to change to non-marketing contact status runs monthly, but contact tier calculations and subscription changes calcula...read more
The new event trigger for workflows that is currently in beta requires you to build a company workflow when looking to trigger a workflow from a property change value on the company object. This is very limiting in that the update marketing contact read more
For workflows to display on the settings>property>used in view, the field has to be specifically looking at a present, existing value for that property. In other words, the workflows are relying on checking that current value. With t read more
The enrollment date should be its own field for each workflow. I cannot look for deals created after a contact was part of a nurture workflow. I am sure there are other performance and reporting use cases this solves for. Can also help to re-enroll read more