I am new to HubSpot and I have experience with salesforce.
What I want to do is, and I will give a simple example just to understand the need:
1. If the user Closed Lost a deal, I want him to fill also the Closed Lost Reason field.
In salesforce we can create a validation rule that checks that.
I understand that I need to do this with Workflow, I already have the branch that checks if the status = “closed lost” and the closed lost reason is empty. How do I add the action to the workflow to prevent the user from saving the record if he did not fill the closed lost reason? I also want the user to recieve an error message in the record page (It will be great to know if i can also prevent creation if someones manually creating the record stright to closed lost for documnetation).
2. Additional question, If I set that kind of custom validation in HubSpot, and we have a Form in our website that checks if the user fills a value for field A, then he must fill field B, If i have that kind of automation that prevent the creation of that scenario, what will happen if the user fills a form? will it prevent the record from being created or it will be created anyway in HubSpot? (Note: Let’s ignore the fact that we can handle this with set up the fields as mandatory in the form)
So I understand that it does not prevent from the user to save the record, just specified that there’s an issue with the record, same with creation from what I understand.
Hi guys!
I hope you don’t mind my asking a follow up question. Regarding Q1. My understanding is you want Closed lost reason to be filled up when deal is moved to closed lost.
My follow up question, is why not require it using the settings in the deal pipeline?
@karstenkoehler If I want to create records manually in the system, can I ask for the user to ask the First Name + Last name in the same time? if he did not fill it, I want the system to throw an error or not allow the user to create the record.
This functionality does not provide nearly the same support that Salesforce does. For the example OP gives, it is sufficient, but the logic only supports a limited number of fields. In my case, I wanted to create validation around a date field, not allowing it to be older than another date field and am not able to do so.
