Skip to content
Opportunities & Pipelines

Conditional Custom Fields for Opportunities

Learn how to use Conditional Custom Fields for Opportunities in GHL Customer Care to control field visibility and requirements based on pipeline, stage, status, and field values.

4 min read942 words7 explained imagesUpdated Tue, 1 Sep at 4:09 PM
View as markdownOpen in ClaudeOpen in ChatGPT
Each image has a one line explanation. Switch to full detail for the step it belongs to, the fields and buttons involved, examples and the whole procedure.
On this page
  1. How Conditional Rules Work
  2. How to Enable Conditional Custom Fields
  3. How to Create a Conditional Rule
  4. Using AND and OR Conditions
  5. Showing Fields and Folders
  6. Making Fields Mandatory
  7. How to Manage Existing Rules
  8. How to Manage Rules from the Pipelines Page
  9. Important Notes and Limitations
  10. Frequently Asked Questions

Conditional Custom Fields let Admins control which opportunity fields appear and which fields must be completed based on a deal’s pipeline, stage, status, or other field values.

This keeps opportunity forms focused and helps teams collect the right information at the right point in the sales process.


TABLE OF CONTENTS


How Conditional Rules Work

Each conditional rule contains:

  • Triggers: The conditions that activate the rule.
  • Outcomes: The fields or folders that appear or become mandatory when the conditions are met.

Supported triggers include:

  • Pipeline
  • Pipeline Stage
  • Status
  • Dropdown fields
  • Radio fields
  • Checkbox fields
  • Multi-select fields

Available outcomes include:

  • Show field: Displays an individual opportunity field.
  • Show folder: Displays an entire folder of opportunity fields.
  • Make mandatory: Requires a visible field to be completed before the opportunity can be saved.

For example, you can show additional onboarding fields when an opportunity is Won or require proposal details when it reaches a particular pipeline stage.

How Conditional Rules Work (image 1 of 7) What this shows For example, you can show additional onboarding fields when an opportunity is Won or require proposal details when it reaches a particular… What this shows Illustrates the "How Conditional Rules Work" section of "Conditional Custom Fields for Opportunities". This screenshot appears in the "How Conditional Rules Work" section of "Conditional Custom Fields for Opportunities". The text alongside this image reads: For example, you can show additional onboarding fields when an opportunity is Won or require proposal details when it reaches a particular pipeline stage. This part of the guide covers 7 fields, listed below. Immediately after, the guide continues: If the feature is not already enabled. Image 1 of 7 What this coversFor example, you can show additional onboarding fields when an opportunity is Won or require proposal details when it reaches a particular pipeline stage.
Fields in this part of the guide PipelinePipeline StageStatusDropdown fieldsRadio fieldsCheckbox fieldsMulti-select fields
Next stepIf the feature is not already enabled:
All 2 steps in this procedure
  1. Triggers: The conditions that activate the rule.
  2. Outcomes: The fields or folders that appear or become mandatory when the conditions are met.

How to Enable Conditional Custom Fields

If the feature is not already enabled:

  1. Go to Settings → Labs.
  2. Find Show & Require Opportunity Fields Conditionally.
  3. Enable the feature for the sub-account.
How to Enable Conditional Custom Fields (image 2 of 7) What this shows Go to Settings → Labs. What this shows Illustrates the "How to Enable Conditional Custom Fields" section of "Conditional Custom Fields for Opportunities". This screenshot appears in the "How to Enable Conditional Custom Fields" section of "Conditional Custom Fields for Opportunities". The text alongside this image reads: Go to Settings → Labs. Find Show & Require Opportunity Fields Conditionally. Enable the feature for the sub-account. Immediately after, the guide continues: Enabling the feature does not change existing opportunity forms. Conditional behavior begins after an Admin creates and saves the first rule. Image 2 of 7 Where to goGo to Settings → Labs. Find Show & Require Opportunity Fields Conditionally. Enable the feature for the sub-account.
Buttons and menus referenced Settings → Labs
Next stepEnabling the feature does not change existing opportunity forms. Conditional behavior begins after an Admin creates and saves the first rule.
All 3 steps in this procedure
  1. Go to Settings → Labs.
  2. Find Show & Require Opportunity Fields Conditionally.
  3. Enable the feature for the sub-account.

Enabling the feature does not change existing opportunity forms. Conditional behavior begins after an Admin creates and saves the first rule.


How to Create a Conditional Rule

  1. Go to Settings → Custom Fields.
  2. Select Opportunity.
  3. Open the Conditional Rules tab.
  4. Click Create conditional rule.
  5. Select the field that should trigger the rule.
  6. Choose an operator and trigger value.
  7. Add more conditions if needed.
  8. Connect multiple conditions using AND or OR logic.
  9. Add one or more outcomes.
  10. Review the rule using the live preview.
  11. Click Save rule.

The rule becomes active immediately after it is saved.

How to Create a Conditional Rule (image 3 of 7) What this shows The rule becomes active immediately after it is saved. What this shows Illustrates the "How to Create a Conditional Rule" section of "Conditional Custom Fields for Opportunities". This screenshot appears in the "How to Create a Conditional Rule" section of "Conditional Custom Fields for Opportunities". The text alongside this image reads: The rule becomes active immediately after it is saved. Immediately after, the guide continues: Use AND when every condition must be met. Image 3 of 7 What this coversThe rule becomes active immediately after it is saved.
Buttons and menus referenced Settings → Custom FieldsOpportunityConditional RulesCreate conditional ruleANDORSave rule
Next stepUse AND when every condition must be met.
All 11 steps in this procedure
  1. Go to Settings → Custom Fields.
  2. Select Opportunity.
  3. Open the Conditional Rules tab.
  4. Click Create conditional rule.
  5. Select the field that should trigger the rule.
  6. Choose an operator and trigger value.
  7. Add more conditions if needed.
  8. Connect multiple conditions using AND or OR logic.
  9. Add one or more outcomes.
  10. Review the rule using the live preview.
  11. Click Save rule.

Using AND and OR Conditions

Use AND when every condition must be met.

Example:

  • Pipeline is Sales Pipeline
  • AND Pipeline Stage is Closed

Use OR when any condition can activate the rule.

Example:

  • Pipeline Stage is Proposal Sent
  • OR Pipeline Stage is Closed

Use the live preview to confirm the expected behavior before saving the rule.


Showing Fields and Folders

Fields and folders included in a Show outcome are hidden by default. They appear only when the rule’s trigger conditions are met.

Fields that are not included in a Show rule remain visible as usual.

To show a field or folder conditionally:

  1. Configure the rule’s trigger conditions.
  2. Under Outcomes, select Show field or Show folder.
  3. Select the field or folder.
  4. Review the live preview.
  5. Save the rule.
Showing Fields and Folders (image 4 of 7) What this shows Configure the rule’s trigger conditions. What this shows Illustrates the "Showing Fields and Folders" section of "Conditional Custom Fields for Opportunities". This screenshot appears in the "Showing Fields and Folders" section of "Conditional Custom Fields for Opportunities". The text alongside this image reads: Configure the rule’s trigger conditions. Under Outcomes, select Show field or Show folder. Select the field or folder. Review the live preview. Save the rule. Immediately after, the guide continues: A Make mandatory outcome requires users to complete a visible field before saving an opportunity. Image 4 of 7 What to chooseConfigure the rule’s trigger conditions. Under Outcomes, select Show field or Show folder. Select the field or folder. Review the live preview. Save the rule.
Buttons and menus referenced OutcomesShow fieldShow folder
Next stepA Make mandatory outcome requires users to complete a visible field before saving an opportunity.
All 5 steps in this procedure
  1. Configure the rule’s trigger conditions.
  2. Under Outcomes, select Show field or Show folder.
  3. Select the field or folder.
  4. Review the live preview.
  5. Save the rule.

Making Fields Mandatory

A Make mandatory outcome requires users to complete a visible field before saving an opportunity.

Example:

  • Trigger: Pipeline Stage is Closed
  • Outcomes:
    • Make Proposal Amount mandatory
    • Make Expected Close Date mandatory
    • Make Decision Maker mandatory

When a user moves an opportunity to the Closed stage, the applicable fields must be completed before the change can be saved.

Important: A mandatory outcome does not automatically display a hidden field. If a field is controlled by a Show rule, make sure its visibility conditions allow it to appear when required.

Making Fields Mandatory (image 5 of 7) What this shows Important: A mandatory outcome does not automatically display a hidden field. What this shows Illustrates the "Making Fields Mandatory" section of "Conditional Custom Fields for Opportunities". This screenshot appears in the "Making Fields Mandatory" section of "Conditional Custom Fields for Opportunities". The text alongside this image reads: Important: A mandatory outcome does not automatically display a hidden field. If a field is controlled by a Show rule, make sure its visibility conditions allow it to appear when required. This part of the guide covers 2 fields, listed below. Immediately after, the guide continues: Go to Settings → Custom Fields → Opportunity → Conditional Rules. Image 5 of 7 What this coversImportant: A mandatory outcome does not automatically display a hidden field. If a field is controlled by a Show rule, make sure its visibility conditions allow it to appear when required.
Fields in this part of the guide Trigger: Pipeline Stage is ClosedOutcomes:
Buttons and menus referenced Make mandatory
Next stepGo to Settings → Custom Fields → Opportunity → Conditional Rules.
All 2 steps in this procedure
  1. Trigger: Pipeline Stage is Closed
  2. Outcomes:

How to Manage Existing Rules

Go to Settings → Custom Fields → Opportunity → Conditional Rules.

From this page, Admins can:

  • View a rule’s triggers and outcomes.
  • Search for an existing rule.
  • Edit a rule.
  • Delete a rule.
  • Create additional rules.

Changes take effect as soon as the rule is saved.

How to Manage Existing Rules (image 6 of 7) What this shows Changes take effect as soon as the rule is saved. What this shows Illustrates the "How to Manage Existing Rules" section of "Conditional Custom Fields for Opportunities". This screenshot appears in the "How to Manage Existing Rules" section of "Conditional Custom Fields for Opportunities". The text alongside this image reads: Changes take effect as soon as the rule is saved. Immediately after, the guide continues: Pipeline-specific rules can also be managed from the Pipelines page. Image 6 of 7 What this coversChanges take effect as soon as the rule is saved. Next stepPipeline-specific rules can also be managed from the Pipelines page.
All 5 steps in this procedure
  1. View a rule’s triggers and outcomes.
  2. Search for an existing rule.
  3. Edit a rule.
  4. Delete a rule.
  5. Create additional rules.

How to Manage Rules from the Pipelines Page

Pipeline-specific rules can also be managed from the Pipelines page.

  1. Go to Settings → Opportunities & Pipelines.
  2. Find the required pipeline.
  3. Open its Actions menu.
  4. Select Manage conditional rules.
  5. Create or update the rule.
  6. Review the live preview.
  7. Click Save rule.
How to Manage Rules from the Pipelines Page (image 7 of 7) What this shows Go to Settings → Opportunities & Pipelines. What this shows Illustrates the "How to Manage Rules from the Pipelines Page" section of "Conditional Custom Fields for Opportunities". This screenshot appears in the "How to Manage Rules from the Pipelines Page" section of "Conditional Custom Fields for Opportunities". The text alongside this image reads: Go to Settings → Opportunities & Pipelines. Find the required pipeline. Open its Actions menu. Select Manage conditional rules. Create or update the rule. Review the live preview. Click Save rule. Immediately after, the guide continues: Only Admins can create, edit, or delete conditional rules. Rules are configured separately for each sub-account. Rules work when users add, edit, or bulk-edit opportunities on web and mobile. Fields and folders included in a Show outcome…. Image 7 of 7 Where to goGo to Settings → Opportunities & Pipelines. Find the required pipeline. Open its Actions menu. Select Manage conditional rules. Create or update the rule. Review the live preview. Click Save rule.
Buttons and menus referenced Settings → Opportunities & PipelinesActionsManage conditional rulesSave rule
Next stepOnly Admins can create, edit, or delete conditional rules. Rules are configured separately for each sub-account. Rules work when users add, edit, or bulk-edit opportunities on web and mobile. Fields and folders included in a Show outcome remain hidden until the conditions are met. Fields not included in a Show rule remain visible. Hidden fields retain their existing values. Hidden fields are excluded from mandatory validation. If multiple rules apply, their mandatory requirements are combined. Conditional validation does not apply to Public API or workflow-based updates.
All 7 steps in this procedure
  1. Go to Settings → Opportunities & Pipelines.
  2. Find the required pipeline.
  3. Open its Actions menu.
  4. Select Manage conditional rules.
  5. Create or update the rule.
  6. Review the live preview.
  7. Click Save rule.

Important Notes and Limitations

  • Only Admins can create, edit, or delete conditional rules.
  • Rules are configured separately for each sub-account.
  • Rules work when users add, edit, or bulk-edit opportunities on web and mobile.
  • Fields and folders included in a Show outcome remain hidden until the conditions are met.
  • Fields not included in a Show rule remain visible.
  • Hidden fields retain their existing values.
  • Hidden fields are excluded from mandatory validation.
  • If multiple rules apply, their mandatory requirements are combined.
  • Conditional validation does not apply to Public API or workflow-based updates.

Frequently Asked Questions

Q. Why is a field still visible when the rule conditions are not met?

A field is hidden by default only when it is included in a Show field or Show folder outcome. Fields not included in a Show rule remain visible.

Q. What happens to an existing value when its field becomes hidden?

The value is retained. Hiding a field does not remove or change its existing data.

Q. Are hidden fields included in mandatory validation?

No. A hidden field is excluded from mandatory validation until it becomes visible.

Q. What happens when multiple rules apply to an opportunity?

The applicable outcomes are combined. Users must complete all visible fields made mandatory by those rules.

Q. Why is a conditional field not appearing?

Confirm that:

  • The feature is enabled.
  • The rule has been saved.
  • The opportunity matches the rule’s trigger conditions.
  • The correct pipeline, stage, status, or field value is selected.
  • The field or folder is included in a Show outcome.

Q. Do conditional rules apply to API and workflow updates?

Conditional validation applies to supported saves on web and mobile. It does not apply to Public API or workflow-based updates.

Was this guide helpful?

Related guides