What it does
Custom Object Fields extends the Field Browser to every custom object in a sub-account. If the account has objects like Equipment, Properties or Policies, each appears as its own group with its own filter chip and count. Every field shows its name, type and merge tag, and the detail panel gives you the field key, ID, folder name and dropdown options.
You get the same search, keyboard navigation and one-click copy as for contact fields, so a custom object stops being the part of the account nobody can find their way around.
Why it matters
Custom objects let you store records that aren't contacts or deals: a vehicle, a property, a piece of equipment. They're useful, and they add a second layer of fields that most agency tooling ignores. In GoHighLevel you manage them from the sub-account's object settings, and each object has its own field list. Finding a key means going into that object, finding the field and opening it.
When you build a workflow or a webhook that touches a custom object, you need those keys exactly. A typo in custom_objects.equipment.serial_number fails quietly. And when someone asks "which fields does the Properties object have?", the native answer is a click-through. If you're new to the feature, our guide to custom objects and their fields covers the native setup.
How it works
- Pick a sub-account in Field Finder. It reads contact, opportunity and custom object fields together.
- Look at the filter chips at the top. Each custom object has a chip named after it, with a field count.
- Click an object's chip to show only its fields, or search across everything at once.
- Click a field to open its details. Copy the merge tag, key or ID.
- For dropdown-type fields, the panel lists every option, each with its own copy button.
- Export the object's fields with the CSV button. The export follows the current filter, so with one object's chip selected you get just that object.
Good to know
- Folder names show. Custom object folders come back with names, so you'll see them in the panel and the CSV. Contact and opportunity folders still show IDs.
- Read-only. Field Finder doesn't create objects or fields. For bulk creation on a custom object, the Bulk Field Creator accepts a custom object key.
- Comparisons include objects. Sub-account Compare matches custom object fields by object and key, so you can check that a client's Equipment object matches your template.
- If an object can't be read, the rest still loads and a note at the top says what was skipped.
- Same shortcuts. Press
/to search, use the arrow keys to move through fields, andcto copy the selected merge tag. - Object labels. Each group is labeled with the custom object's name from the sub-account, so you aren't guessing from internal keys.
Questions
Which custom objects does Field Finder show?
Every custom object it can read in the sub-account. Each one gets its own group and filter chip, labeled with the object's name.
Do custom object folders show real names?
Yes. Unlike contact and opportunity fields, custom object folders come back from HighLevel with their names, so Field Finder shows them.