HighLevel Conditional Custom Fields: Require the Right Deal Data

Key Takeaways

• Conditional custom fields let an opportunity form change with the deal. Fields show up, or become required, based on pipeline, stage, status, owner or the value of another field.
• Every rule has two halves. Triggers are the conditions. Outcomes are Show field, Show folder or Make mandatory.
• Make mandatory does not reveal a hidden field. If a Show rule is hiding it, the required check never fires.
• The validation runs when someone adds, edits or bulk edits a deal on web or mobile. Public API and workflow updates skip it.
• Only admins can build these rules, and they live in each sub-account, not at the agency level.

A deal gets dragged to Won. Everybody celebrates. Then somebody goes looking for the amount, the close date and who signed off, and the fields are blank. Or the opposite problem: every opportunity shows twenty fields that have nothing to do with where the deal is, so the team learns to skip all of them. This post walks through HighLevel's Content Army tutorial on conditional custom fields for opportunities, rewritten for owners who want their pipeline to hold real data. On Point Tech Solutions is a Go High Level consultant in Los Gatos, and we build pipelines like this for Go High Level Bay Area clients every week, so here is how the feature works and where it bites.

What conditional custom fields actually do

Out of the box, every custom field on an opportunity shows up all the time. A brand new lead and a signed job carry the same form. Conditional rules change that. You decide which fields appear, and which ones must be filled in, based on what is true about the deal right now.

The example in the video is a sales pipeline. Proposal amount, expected close date and decision maker only matter once a deal is Won, so the presenter sets them to appear and become required only at that point. Before Won, the form stays clean. At Won, nobody can save the deal without the three answers.

One setup note from HighLevel's help doc. If you do not see the feature, go to Settings, then Labs, and turn on Show and Require Opportunity Fields Conditionally. Nothing changes until an admin creates and saves the first rule.

Triggers and outcomes, in plain words

There are two ways in. Go to Settings, then Custom Fields, pick Opportunity, and open the Conditional Rules tab. Or go to Settings, then Opportunities and Pipelines, find the pipeline, click its three dots and choose Manage Conditional Rules. Same place either way.

Triggers are the conditions that start the rule. You can trigger on opportunity name, value, pipeline, stage, status, owner, follower and supported custom fields. Outcomes are what happens when the conditions are met, and there are three:

• Show field displays one field that is otherwise hidden.
• Show folder displays a whole folder of fields at once.
• Make mandatory blocks the save until a visible field is filled in.

Stack more than one condition and you choose And or Or. And means every condition has to be true, like pipeline is Sales and status is Won. Or means any one of them fires the rule, like stage is Proposal or status is Won.

Building the Won rule on a Go High Level Bay Area pipeline

Here is the rule from the tutorial, step by step. Click Create Conditional Rule. Set the first trigger to pipeline is any of, and pick the one pipeline you want it on, so it does not leak into your other pipelines. Click Add Condition and set status is any of Won. That is an And rule. Both have to be true.

Now the outcomes. Add three Make mandatory outcomes, one each for proposal amount, expected close date and decision maker. Before you save, use the live preview on the right side of the builder. Flip the status and watch the form react. It is the fastest way to catch a rule that does the wrong thing.

In the demo those three fields were already visible, so mandatory was all they needed. Which leads to the trap.

The traps worth knowing before you build

Mandatory does not unhide. If a Show rule is hiding a field and its conditions are not met, Make mandatory will not turn it on. The required check just never fires. If you hide a field and also want it required, make sure the Show rule's conditions put it on screen at the moment it needs to be filled.

Automations skip the check. Validation applies when a person adds, edits or bulk edits a deal in the web app or the mobile app. Public API calls and workflow updates bypass it. So if a workflow moves deals to Won, it can land a deal there with the fields empty. Plan for that.

Admins only, per sub-account. Only admins can create, edit or delete rules, and they are set up inside each sub-account. An agency running ten clients builds them ten times, or ships them in a snapshot.

Why This Matters for Bay Area and San Jose Businesses

Think about a Campbell remodeling company or a San Jose roofing crew. The estimator marks the job won from a truck. Six weeks later the owner wants to know what the average job sold for and how long quotes take to close, and the CRM cannot say, because nobody had to type it in. A required field at Won fixes that at the source, with no spreadsheet and no Friday reminder text.

It also makes the CRM easier for the people who use it. Office managers and field techs ignore busy forms. A form that only asks for what matters at each stage gets filled in. And because the rules live in your own sub-account, the data and the logic stay with the business. When On Point Tech builds a pipeline for a Bay Area client, the account is theirs, and we hand over the rules so the office can change them later.

Practical Steps

1. Write down which fields matter at which stage. Start with Won: amount, close date, decision maker.
2. If the feature is not showing, turn it on under Settings, then Labs.
3. Go to Settings, then Custom Fields, select Opportunity, and open Conditional Rules.
4. Create a rule. Add a pipeline trigger first so it stays on the right pipeline, then add the stage or status condition.
5. Add outcomes. Show the fields or folder, then make the ones you need mandatory.
6. Test in the live preview, then save.
7. Check any workflow that moves deals into that stage, since workflow updates skip the rule.

Watch the HighLevel tutorial

Final thoughts

Conditional custom fields are a small setting that fixes a big habit. The pipeline asks for the right information at the right moment, and a deal cannot be called Won with the important parts blank. On Point Tech Solutions is a Go High Level Bay Area consultant in Los Gatos serving San Jose and the whole Bay Area. We build pipelines like this done for you, or teach your team with an SOP, and either way the account and the data stay in your name.

Want to build this yourself? Join the On Point Tech Academy. It's free, and we build live every Tuesday and Thursday.