Set up custom fields

A custom field is a slot for information Exabloom doesn’t track out of the box. Every field is defined by four things: the object it attaches to, its type, a name, and an optional group it sits in. Once defined, the field becomes available to fill in on every record of that object, and to filter, display and automate on.

Custom fields live in one place, and it’s two clicks from anywhere in the app. Whether you see the page at all depends on your role: Custom Fields only appears in Settings if your role includes it, so if it’s missing, ask an admin.

The first and most important choice is which object the field describes. There are five: Contact, Appointment, Calendar, Lead and Organisation. For most teams the live decision is between the first and the fourth.

A reliable test: would the answer be the same across every opportunity this person ever has? If yes, it belongs on the Contact (preferred language, postal code). If it changes per deal, such as the treatments they’re enquiring about or a per-quote budget, it belongs on the Lead. Appointment, Calendar and Organisation fields work the same way for those records.

The type decides how the field is entered and read. There are eight, listed here in the order the dropdown shows them:

Two of them, Single Select and Multi Select, let you define a fixed list of options. Single Select allows one choice; Multi Select allows several on the same record. Choose these whenever the answer should come from a tidy menu rather than free text, so it stays consistent and easy to filter.

Every input in the dialog, in order:

• Field Name: what your team reads. It must be unique for that object (the check ignores capital letters) and cannot contain a comma. The box turns red and says “Name already exists.” or “Name cannot contain commas.”
• Object: from Step 1. Editable while creating, locked after.
• Group: which section it sits in. Defaults to None (Unassigned).
• Unique Key: generated for you from the name and read-only. It follows the name, so renaming a field later changes its key too.
• Type: from Step 2.
• Options: only for the two select types.
• Description: optional, and worth writing. AI agents read it to decide which field to fill from a conversation, so “The lead’s maximum purchase budget in SGD.” beats an empty box.
• Required Field: “Prevent saving records without this field.”

Groups are named sections that keep related fields together, and they’re how lead fields get organised in the Lead Info panel. Every workspace starts with default groups: Contact Info for contacts; Appointment; Calendar; Lead Info, Product, Note and Others for leads; and Organisation. New workspaces also arrive with four lead fields already in Lead Info: Note, Source, Appointment Status and Appointment Date & Time.

You don’t have to use groups: a field can stay None (Unassigned) and still works everywhere. Groups are about tidiness. When you have a dozen lead fields, sorting them into Product, Note and so on keeps the panel readable instead of one long list.

A field you create doesn’t just sit in Settings; it threads through the product. Once defined, the same field can show up in four places:

• The Lead Info panel beside every conversation, where its group becomes a section. See Customise the Lead Info panel.
• A pipeline’s Data Fields: each pipeline chooses which lead and contact fields reps see. See Build your sales pipeline & stages.
• Forms and the create dialogs: add a contact custom field to a capture Form, or to the Create contact and Create lead forms, to collect it at the source.
• Workflow filters and update steps: automations can branch on a field’s value, or write to it.

Hover any row on All Fields and two icons appear at the end of it: a pencil to edit and a bin to delete.

A few fields most teams end up wanting, with the object and type that fit best.

• Object first, and forever. The object can’t be changed after you save. Decide contact-vs-lead before you create the field.
• No commas in names. The form blocks them, and a duplicate name on the same object is rejected too.
• Required can block saves. A required field must be filled on the Create contact and Create lead forms. Require sparingly.
• Renaming changes the key. The Unique Key follows the name, so update anything you typed by hand with the old one.
• Groups are optional. A field works fine as None (Unassigned); groups just keep the panel tidy.
• Deleting is destructive. It wipes every stored value and removes the field from forms and pipelines. Hide instead of delete when in doubt.
• Pick the tightest type. Numbers and dates compare and filter; the same data as Text doesn’t. Selects keep answers consistent.