Custom Field Rules

Custom Field Rules let you automate field behaviour based on other field values. You can show or hide fields, auto-populate values, or map values from one field to another, all based on matching conditions in one or more other fields.

Where to find it: Go to Settings, then Custom Fields. The Field Rules section appears at the bottom of the Leads, Deals and Contacts tabs, and you can create rules on the Leads and Deals tabs.

How rules work

Each rule has three parts:

Source field: The field that triggers the rule. This can be a select, multi-select or number field, or a text-based field (Text, Long text, Email, Website or Phone).
Source value(s): What the source field must match for the rule to run. For most fields you pick specific values; for a number field you set a Condition (such as greater or equal to) and a Value to compare against.
Target field: The field that is affected by the rule.

A rule can also have extra conditions on other fields. Click Add condition to add one, then use the Match dropdown to choose whether All conditions or Any condition must match for the rule to run.

On the Deals tab a rule can also read fields that live on the deal's lead or on its partner. These appear in the source and condition lists prefixed Lead · and Partner · — for example "Lead · Number of rooms" or "Partner · Partner tier". The target is always a deal field: a rule never writes back to the lead or partner.

Action types

There are three types of actions a rule can perform:

Show Field

When the source field matches the selected value(s), the target field appears on the form. If the source field does not match, the target field is hidden. This is useful for conditional fields that only make sense in certain situations.

Set Value

When the source field matches the selected value(s), the target field is automatically set to a specified value. You can also lock the target field so it cannot be manually changed when the rule applies.

Map Values

Map each source value to a corresponding target value. When the source field is set to a value, the target field is automatically set to its mapped value. This is useful for translating between different field vocabularies.

Number fields can be sources too. Each row then pairs a condition and a threshold with a target value — for example, greater or equal to 200 sets "Enterprise". Rows are checked top to bottom and the first match applies, so order rows from the highest threshold down; use the arrows on each row to reorder.

Extra conditions work differently on a Map Values rule: they act as a gate. The mapping rows still match on the source field, and the mapped value is only applied while the extra conditions pass.

Creating a rule

Go to Settings, then Custom Fields, and select the Leads or Deals tab.
Scroll to the Field Rules section and click Add Rule.
Enter a rule name (for example, "Auto-set pipeline from region").
Choose the action type (Show Field, Set Value, or Map Values).
Select the source field — on the Deals tab this includes the deal's lead and partner fields, shown prefixed Lead · and Partner · — then the source value(s) that trigger the rule. For a number field, choose a Condition — greater or equal, less or equal, greater than, less than, equals or not equals — and enter the Value to compare against.
Optionally click Add condition to require more fields to match (up to 20 extra conditions), and set Match to All conditions or Any condition.
Select the target field.
For Set Value: choose the value to set. For Map Values: map each source value or condition to a target value.
Optionally enable "Lock target field" to prevent manual changes when the rule applies.
Save the rule.

Managing rules

Each rule shows a summary of its source and target fields, along with an action type badge. You can:

Toggle a rule between active and inactive using the switch.
Edit a rule by clicking the pencil icon.
Delete a rule by clicking the trash icon.

Where rules apply

Rules are per category (Leads or Deals) and per partner type. The target field always belongs to the rule's own category and partner type. Lead rules read lead fields only; deal rules can also read the deal's lead and its partner's fields of the same partner type. Rules apply on:

Lead sidebars (when creating or editing a lead, including from a campaign)
Deal sidebars (when creating or editing a deal, including from a campaign)
The partner portal, when partners create or edit leads and deals
Lead capture forms — a submission is checked against your rules when it arrives

A deal rule that reads a lead or partner field keeps running after the deal is saved: when that value changes — in your team, on the portal, through your CRM or the API — the deal's rule-driven fields update automatically.

Good to know

Select, multi-select, number and text-based fields can be source fields. For Map Values, only select and number fields can be sources.
A blank or non-numeric value in the source field never matches a number condition.
Rules are evaluated in real time as users fill in forms, so fields appear or values populate immediately.
Inactive rules do not run. Toggle a rule off if you need to temporarily disable it.
Lock target field prevents users from manually changing the target field value when the rule is active.
Every condition field must be different from the source and target fields. On a deal rule a condition can also read a lead or partner field of the same partner type.
Deleting a field that a rule's conditions use deletes the rule.
Partners see a rule run live only when every field in its conditions is visible to them. A deal rule that reads a lead or partner field partners cannot see still applies when the deal is saved, and whenever that field changes afterwards — so a partner may be able to infer the hidden value from the result. The editor warns you in both cases.