Account admin
Custom fields and objects
The fields and records your niche needs, created correctly the first time.
What you'll get
- The fields this business actually needs on a contact: treatment interest, referral source, next review date, whatever the niche runs on.
- Custom records for the things that are not people, like a piece of equipment, a property, or a policy, and the link between those records and the contact.
- The field list read back to you, which is what every workflow you build afterwards depends on.
Say this
What custom fields exist in this account?
Create a dropdown field called Treatment Interest with four options.
Add a date field for Next Review.
The pro prompt
The exact ask we run on real client accounts
Proven liveIn my [MCP Testing] account, first list the custom fields that already exist so we do not duplicate anything. Then create these on the contact record: [Treatment Interest] as a dropdown with the options [body contouring, injectables, skin, not sure]; [Referral Source] as a dropdown with [Google, Instagram, friend, walk in]; [Next Review Date] as a date. Read them back to me afterwards with their exact names and types, and tell me which ones I can now use as a condition inside a workflow.
Click the box to select it, then press ⌘C (or Ctrl+C)
Everything in [brackets] is yours to change. Ask for the existing list first. Half the messy GHL accounts in the world have three fields that mean the same thing.
What happens when you ask
- Claude lists what already exists so you can see the duplicates before you make more.
- It creates the fields with the right types and options.
- It reads them back, and from then on every form, workflow, and branch you build can point at them properly.
Good to know
- Fields are the foundation. Build them before the forms and workflows that use them, and everything downstream stops failing silently.
- Dropdowns beat free text for anything you will filter on. Free text is where segmentation goes to die.
- Renaming a field is safe. Deleting one is not: anything pointing at it goes quiet. If a field is retired, leave it and stop using it.
- Custom objects are for things that are not people. Most accounts never need one, and that is fine.
- Needs the full license. Reading the field list is free.
Where people go wrong
| What happened | The fix |
|---|---|
| "A workflow condition on my field never matches." | The field is free text and the values are spelled four different ways. Make it a dropdown and set the options. |
| "I deleted a field and workflows broke." | Deleting a field kills anything referencing it, silently. Run an audit, and retire fields instead of deleting them. |
| "There are three fields that mean the same thing." | List first, create second. Ask Claude which ones look like duplicates and it will tell you. |