Conditional Custom Fields for Opportunities

Opportunity forms can now automatically adapt based on each deal.

Admins have the capability to control which fields or folders are displayed, as well as which fields are mandatory, depending on an opportunity’s pipeline, stage, status, or other field values.

Create rules using single conditions or AND/OR logic.
Utilise pipeline, pipeline stage, status, dropdown, radio, checkbox, and multi-select fields as triggers.
Display individual fields or entire folders when conditions are met.
Make visible fields mandatory, preventing incomplete opportunities from being saved.

Preview each rule in real-time before saving.
Apply rules across Add, Edit, and Bulk Edit flows on both web and mobile.
Manage pipeline-specific rules directly from the Pipelines page.
Activate rules immediately after saving.

Go to
Settings → Labs

.
Enable
Show & Require Opportunity Fields Conditionally

for the sub-account.

Navigate to
Settings → Custom Fields → Opportunity → Conditional Rules

.

Click
Create conditional rule

.
Choose the trigger conditions and connect them using AND/OR logic.
Select an outcome:

– Show field

– Show folder

– Make mandatory

Review the live preview and click
Save rule

.

You can also navigate to

Settings → Opportunities & Pipelines

, open a pipeline or stage’s

Actions

menu, and select

Manage conditional rules

Keep opportunity forms focused on relevant information.
Collect necessary details at the appropriate stage of the sales process.
Enhance reporting accuracy and consistency.
Standardise data collection across pipelines and teams.
Prevent opportunities from being saved with missing mandatory information.

Fields and folders included in a
Show

rule remain hidden until their conditions are fulfilled.
Fields not included in a
Show

rule remain visible as usual.
If multiple rules apply, their mandatory requirements are combined.
Only Admins can create, edit, or delete rules.
Rules are configured separately for each sub-account.
No changes occur until an Admin creates the first rule.
Validation applies to saves on web and mobile, but not to Public API or workflow-based updates.