How Do I Create a Custom Field?

About

Custom fields let you capture data unique to your workflow beyond Goliath’s built-in contact properties (name, phone, email, address). Common examples include Lead Source, Motivation Level, Last Contact Date, or Preferred Channel. Once created, the custom field appears on every contact record (both existing and new contacts), and can be used in filters, workflows, exports, and outreach templates.

Admin Only

Creating, editing, or deleting custom fields requires admin permissions. Non-admin team members can view and populate custom field values on contacts, but cannot manage the field definitions themselves.

Step-by-Step Guide

1. Navigate to Settings

   From the main navigation, open Settings and select the Custom Fields section. This is where all org-wide contact custom fields are managed.

2. Click the Create Custom Field button

   Look for a button labeled Add Custom Field, Create Field, or a similar action button. Click it to open the custom field creation dialog.

3. Enter the field name

   Type a descriptive name for your custom field (e.g., Lead Source, Motivation Level, Referred By). This name will appear in contact detail panels, filters, and export headers. Use clear, consistent naming across your team.

4. Select the field type

   Choose the data type that matches how you’ll use the field:

   • Text — Free-form text entry (names, notes, short descriptions)
   • Number — Numeric values (years, square footage, price ranges)
   • Date — Calendar dates (last contact, follow-up due)
   • Dropdown — Single-select from predefined options (lead source, status)
   • Multi-Select — Multiple choices (tags, interests)
   • Checkbox / Boolean — Yes/no toggle (qualified, VIP)
   • Currency — Formatted money values (budget, max offer)

   The type affects filtering, sorting, and how the data exports.

5. Configure field options (if applicable)

   For Dropdown or Multi-Select types, define the list of options users can choose from (e.g., Referral, Cold Call, Website, Direct Mail for a Lead Source dropdown). For other types, set any formatting preferences (decimal places for numbers, date format, etc.).

6. Set the field as required (optional)

   Toggle the Required option if you want Goliath to prevent saving a contact without a value for this field. Use this sparingly — only for truly essential data.

7. Save the custom field

   Click Save, Create, or Continue to finalize. The custom field immediately appears in the custom fields section of every contact’s detail panel (existing contacts show the field as empty until populated).

Pro Tips

• Choose the right type upfront — changing a field type later may require re-entering data or converting values, which can be disruptive.
• Use dropdowns for consistency — if the data has a fixed set of options (e.g., property types, lead sources), a dropdown prevents typos and makes filtering easier.
• Avoid duplicate field names — clear naming prevents confusion in filters, exports, and workflow conditions.
• Consider bulk updates — after creating a field, you can populate values across many contacts at once using filters + Actions → Update Field, or by re-uploading a CSV with the new field mapped.

Where Custom Fields Work

Custom fields integrate throughout Goliath:

• Filters — Build saved searches (e.g., “show contacts with Lead Source = Referral”)
• List memberships — Trigger workflows or campaigns based on custom field criteria
• Exports — CSV and XLSX downloads include custom fields as columns
• Workflow automation — Set triggers like “when Motivation Level is set to High, start the drip sequence”
• Outreach templates — Insert custom field values using template variables (e.g., {{customField.leadSource}})

Frequently Asked Questions

Q: Can I bulk-update a custom field across many contacts?

Yes. Apply a filter to narrow down the contacts, select them, then use Actions → Update Field to set the custom field value in bulk. Alternatively, export to CSV, fill in the values offline, and re-upload with the custom field column mapped.

Q: Is there a limit on the number of custom fields I can create?

Goliath supports dozens of custom fields per organization. For very large custom field needs (50+), contact support to discuss best practices and performance considerations.

Q: Can I make a custom field required when creating new contacts?

Yes. During field creation (or when editing an existing field), toggle the Required option. Goliath will prevent saving a contact record without a value for that field.

Q: What happens to the data if I delete a custom field?

Deletion is irreversible and permanently removes all stored values for that field across every contact. Goliath typically requires confirmation before deleting. If you might need the data later, consider hiding the field or renaming it instead.

Q: What’s the difference between contact custom fields and pipeline custom fields?

Contact custom fields are org-wide and appear on every contact (people and companies). Pipeline custom fields apply to deals and are specific to each pipeline (e.g., Acquisitions vs. Dispositions). See Pipeline Fields for deal-side customization.

Q: Will the custom field appear on contacts I created before adding it?

Yes. Custom fields are applied retroactively to all existing contacts. The field shows up immediately, with values initially empty until you populate them.

---

Related Articles:

• Custom Fields for Contacts (feature overview)
• Pipeline Fields (deal custom fields)
• Bulk Actions on Contacts (updating many records at once)