Custom Fields How to add your own fields to any record type, choose the right type, and scope them to a single pipeline or board.

Operations, Data, Custom Fields. Add fields the platform does not ship with, to any record type. You need the internal operations capability.

This is the first thing to set up in a new workspace. Imports map to these fields, automations set them, boards display them, and filters use them - so a field added later means revisiting all four.

The Layout

A rail of record types on the left, the fields for the selected one on the right. The rail shows how many fields each type already has, and is searchable.

Fields can be added to around twenty-five record types, including Deals, Contacts, Companies, Invoices, Employees, Expenses, Products, Tasks, Leave Requests, Attendance, Issues, Support Tickets and Goals.

Field Types

Eleven types. Picking the right one matters more than it looks, because the type determines how the field can be filtered, displayed and reported on.

Type	For
Text	Free text
Number	Quantities and counts
Currency	Money, with currency handling
Select	One choice from a fixed set
Multi-select	Several choices from a fixed set
Date	A date
Boolean	Yes or no
Email	An email address
Phone	A phone number
URL	A link
Lookup	A reference to another record

Lookup is the one that unlocks the most. It stores a reference to another record and displays its name, so a deal can point at a real supplier record rather than carrying its name as text.

Currency rather than Number for money. It carries currency handling, which matters the moment you trade in more than one.

Adding A Field

1. Select the record type in the rail.
2. Add a field.
3. Name it as a question the person filling it can answer. "Renewal month" beats "Field 3".
4. Pick the type.
5. For Select or Multi-select, define the options. Deliberately - adding options later is easy, cleaning up wrong values is not.
6. Decide whether it is required. Required fields block saving without them, which is right for genuinely mandatory data and irritating for anything else.
7. Decide whether it shows on the card, so it is visible without opening the record.
8. Save.

Scoping

Not every field belongs on every record of a type.

• Deals can be scoped per pipeline, so a field appears on your enterprise pipeline and not on your self-serve one.
• Board items can be scoped per view, so a custom board has its own fields.

Use scoping rather than adding a field everywhere and asking people to ignore it. Fields that do not apply are the fastest way to train a team to skip fields entirely.

Sections

Fields can be grouped into sections, so a record with twenty custom fields reads as organised groups rather than one long column. Worth doing past about six fields.

Before You Import

Create your fields first. The import mapping step lets you map a spreadsheet column to any existing custom field - but only if it exists. A column with no target is a column you re-import later. See Apps and Import.

Common Questions

Can I change a field's type after creating it? Treat it as no. Existing values may not convert. Create the field with the right type, or create a new field and migrate.

Will a custom field appear in filters? Yes. Custom fields are first-class in the advanced filters and in reporting, which is why the type matters.

Can an automation set one? Yes, with the Set Custom Field action. The field must exist first, and the table must be allowlisted for automated writes. See Automation Actions and What They Need.

How many is too many? When people start leaving them blank. That is the signal that the form is asking for more than the work needs.