Custom Fields

Add your own fields to any object — capture the data that matters to your MSP without being constrained by the built-in schema.

What custom fields are

Custom fields extend the built-in data model. Every MSP tracks slightly different things — some need an "Executive Sponsor" text field on accounts, others need a "Hardware Budget" number on leads. Custom fields let you add those without any code.

Custom field values appear inline on record detail pages and can appear as columns in list views, filter options, and workflow conditions.

Supported objects

Account

Client/prospect org records

Contact

Individual people

Deal

Pipeline opportunities

Lead

Unqualified prospects

Contract

Agreements & service lines

Field types

Type	Input	Example use
Text	Single-line text box	Executive sponsor name, office location, ticket queue prefix
Number	Numeric input (supports decimals)	Hardware budget, seat count override, tech count
Date	Date picker	Last audit date, equipment refresh target date
Boolean	Toggle / checkbox	Has dedicated IT contact, cyber insurance purchased
Select	Single-choice dropdown	MSP tier, support model, account region
Multi-Select	Checkbox list (multiple choices)	Compliance frameworks, vendor relationships, service flags

Creating a custom field

1Go to Settings → Custom Fields.
2Select the object type tab (Account, Contact, Deal, Lead, or Contract).
3Click Add Field.
4Enter a label — this is the display name shown on records (e.g., "Hardware Budget").
5The field key is auto-generated from your label (e.g., "hardware_budget"). You can edit it before saving — it cannot be changed after.
6Choose the field type.
7For Select and Multi-Select types: add the available options in the options builder.
8Configure the four flag checkboxes (see below).
9Click Save. The field appears immediately on all records of that object type.

The auto-generated field key

Each custom field has an internal key used in API calls and workflow conditions. The key is derived from your label — spaces become underscores, special characters are removed, and everything is lowercased. For example:

"Hardware Budget" → hardware_budget

"Executive Sponsor (Primary)" → executive_sponsor_primary

"Has Cyber Insurance?" → has_cyber_insurance

Important: The field key is permanent after saving. Workflow conditions and API references use the key — changing it would break existing workflows. Choose carefully.

Field flags

Show in list view

showInList

Adds a column for this field to the list/table view for this object type. Users can toggle column visibility. Keep this off for rarely-used fields to avoid cluttering the table.

Show in filter bar

showInFilter

Adds this field as a filter option in the list view filter bar. Works for Select, Multi-Select, Boolean, and Number types. Text and Date filters are available separately.

Searchable

showInSearch

Includes this field's value in full-text search (Cmd+K global search). Best for Text fields where the value is a name, ID, or code that users might search for.

Required

required

Makes this field required when creating a new record. Users cannot save without providing a value. Use sparingly — too many required fields slow down record creation.

Select / Multi-Select options

When creating a Select or Multi-Select field, define the allowed options in the options builder:

Click Add Option to add each choice.
Drag to reorder options — the order here is the order in the dropdown.
To rename an option: edit it in Settings → Custom Fields. Existing values on records update automatically.
To remove an option: existing records that had that value will show it as a plain text label (the value is preserved, just no longer selectable).

Ordering and managing fields

In Settings → Custom Fields, drag fields within an object type tab to reorder them. The order here controls the order they appear on record detail pages.

To delete a custom field, click the trash icon. This permanently deletes all values stored for that field across all records. A confirmation dialog warns you before proceeding.

Using custom fields in workflows

Custom fields are available as trigger conditions and action targets in the playbook system:

As a trigger: Field Changed

Select "Field Changed" as the trigger type, then pick your custom field from the field dropdown. The trigger fires when that field's value changes on any record.

Example: When Account "Has Cyber Insurance?" changes to true → create a compliance task

As a condition

In the Condition step, filter by custom field values. Combine with built-in fields for complex targeting.

Example: If Deal "Hardware Budget" > 50000 AND stage = Discovery → assign to senior rep

As an action: Update Property

The "Update Property" action lists both built-in fields and custom fields. Set a custom field to a static value or copy it from another field.

Example: When deal closes → set Account "Account Region" = deal's region custom field

← Roles & Permissions Pipeline Stages →