Implementation
GoHighLevel Naming Conventions for Workflows, Tags, Fields, and Funnels
Use names that identify business area, asset purpose, trigger or audience, lifecycle status, and version only when version matters. A useful pattern is AREA — PURPOSE — DETAIL. Avoid owner initials, vague words such as “new,” and dates that do not communicate operational meaning.
The short answer
Use names that identify business area, asset purpose, trigger or audience, lifecycle status, and version only when version matters. A useful pattern is AREA — PURPOSE — DETAIL. Avoid owner initials, vague words such as “new,” and dates that do not communicate operational meaning.
The governing principle
A name should help an unfamiliar administrator predict what an asset does and where it belongs without opening it. Names are navigation and risk controls, not decoration.
Recommended architecture
Maintain a short controlled vocabulary for areas such as LEAD, SALES, OPS, REVIEW, BILLING, and CLIENT. Apply it consistently across folders, workflows, forms, calendars, fields, and reports while keeping customer-facing labels natural.
Prerequisites
Do not configure the production change until these inputs are known and recorded.
- Inventory current assets and identify duplicates before renaming.
- Choose controlled terms for business areas, lifecycle states, locations, and channels.
- Separate internal names from customer-visible labels.
- Record integrations or formulas that may depend on field, tag, or asset identifiers.
Implementation procedure
Build in the smallest independently testable increments. Record the reason for each decision, not only the final setting.
- Publish a one-page convention with examples and forbidden patterns.
- Rename low-risk folders and unused assets first.
- Rename active assets in batches, checking references after each batch.
- Mark deprecated assets clearly before archive rather than silently deleting them.
- Add naming review to the release and snapshot process.
Acceptance tests
A published asset is not necessarily a working system. Test normal, exception, duplicate, delayed, and recovery paths with traceable records.
- A new administrator can locate the active asset from a business request.
- Alphabetical sorting groups related assets predictably.
- Customer-facing text remains unchanged.
- Integrations, filters, reports, and workflow references still resolve.
- Deprecated and test assets cannot be mistaken for production.
Rollback and recovery
Export the inventory and capture old-to-new names. If a dependent process fails, restore the affected name or reference from the mapping before continuing the batch.
Operating the system
Assign one vocabulary owner, review new asset names during changes, and run quarterly searches for TEST, COPY, NEW, FINAL, initials, and unexplained numeric suffixes.
Failure modes to prevent
Overly elaborate codes become tribal knowledge, while vague names produce duplicates and unsafe edits. The convention fails if it is difficult to type, not documented, or applied only to workflows.