Custom Fields

Custom fields let each workspace define its own data model. Add fields like "Contract Type", "Annual Budget", or "Industry Segment" to contacts, deals, and companies — then use those fields in forms, detail views, and webhook integrations.

Why Custom Fields?

Every business tracks different data. Workestra ships with a standard set of fields (name, email, phone, etc.), but your workflow likely needs more:

• A real estate agency needs Property Type and Budget Range on deals
• A SaaS company needs Contract Length and MRR on contacts
• A recruiting firm needs Specialization and Rate Card on companies

Custom fields solve this without modifying the database — they're stored in a flexible JSONB column and rendered dynamically based on your definitions.

Supported Field Types

Managing Custom Fields

Creating a Field

1. Go to CRM > Settings > Custom Fields
2. Select the entity tab: Contacts, Deals, or Companies
3. Click Add Field
4. Configure:

5. For Select and Multi Select types, add options:

   • Type each option and press Enter
   • Reorder or remove options as needed

6. For Number and Currency types, optionally set:

   • Min / Max constraints

7. Configure visibility:

8. Click Create Field

Editing a Field

1. Click the pencil icon on any field
2. Modify label, description, options, validation, or visibility
3. Click Save Changes

Reordering Fields

Fields appear in the order they're listed. To change the order:

1. Use the up/down arrows on each field card
2. Order saves automatically

Fields within the same Section Group are displayed together.

Deleting a Field

1. Click the trash icon on the field
2. Confirm deletion

Using Custom Fields

In Edit Dialogs

When editing a contact, deal, or company, custom fields appear below the standard fields. They're grouped by section and show validation errors inline.

In Detail Views

Custom field values display in the entity's detail sidebar, grouped under their section headings. Each type renders appropriately:

• URLs are clickable links
• Emails are mailto links
• Ratings show as star icons
• Multi Select values show as badges
• Currency values show with formatting
• Dates are formatted in your locale

In Webhook Integrations

Custom fields integrate with the inbound webhook pipeline. When configuring a webhook source's field mapping, use the cf. prefix to map incoming data to custom fields.

Example payload map:

{
  "email": "data.email",
  "first_name": "data.contact.first_name",
  "cf.contract_type": "data.contract",
  "cf.annual_budget": "data.budget",
  "cf.industry": "data.organization.industry"
}

Any field in the map prefixed with cf. will be stored in the entity's custom fields. The part after cf. must match the field key defined in Custom Fields settings.

In Routing Rules

You can route inbound items based on custom field values. When creating routing rule conditions, reference custom fields with the cf. prefix:

Validation

Custom fields enforce validation at multiple levels:

1. UI validation — Required fields, min/max, format checks shown inline
2. Webhook validation — Incoming data is coerced to the correct type (e.g., string "42" becomes number 42)
3. Select validation — Values must match defined options

Type Coercion for Webhooks

When data arrives via webhooks, values are automatically coerced:

Section Groups

Use section groups to organize related fields visually. Fields with the same Section Group name are displayed together under a shared heading.

Example:

This creates three collapsible sections in the detail view and edit forms.

Best Practices

• Use descriptive labels — "Annual Contract Value" is clearer than "ACV"
• Group related fields — Use section groups to keep forms organized
• Keep it minimal — Only create fields you actually need. Too many fields slow down data entry
• Use Select for constrained values — Prefer dropdowns over free text when options are known
• Set required sparingly — Only mark truly essential fields as required
• Plan field keys carefully — They can't be changed after creation, and webhook mappings reference them

Next Steps

• CRM Settings — Pipeline stages and price books
• Contacts — Where custom fields appear
• Deals — Deal-specific custom fields
• Companies — Company-specific custom fields