Skip to main content
GHL MCP Guide
LCV

Location Custom Values

Location & Config · Intermediate · Updated March 2026

Manage custom values (variables) at the location level. These reusable values power templates, workflows, and dynamic content across the sub-account.

Custom values are location-level variables that inject dynamic content into templates, workflows, and messages. A location’s phone number, business hours, service area, tagline — anything that’s reused across multiple touchpoints should be a custom value. Managing them through MCP means you can update these variables from external data sources and keep dynamic content current across every surface automatically.

What This MCP Tool Does

CRUD on custom values within a location. Create reusable variables, list all defined values, update variable content, and delete values. Custom values are referenced in email templates, SMS messages, workflow actions, and any content that supports merge fields.

Endpoint Reference

List values: GET /locations/{locationId}/customValues Create a value: POST /locations/{locationId}/customValues Update a value: PUT /locations/{locationId}/customValues/{valueId} Delete a value: DELETE /locations/{locationId}/customValues/{valueId}

Authentication

Requires a Private Integration Token (PIT) with the locations scope enabled.

Key Parameters

  • name — the variable name (how it appears in merge field selectors)
  • value — the actual content the variable resolves to

Important Notes

Custom values are different from custom fields. Custom fields store data per record (per contact, per opportunity). Custom values store data per location — they’re the same for everyone. Think of them as global constants for the sub-account.

Common custom values: business name, phone number, address, hours of operation, service area description, review links, booking page URLs. Any piece of information that appears in multiple templates or messages.

Updating a custom value via MCP immediately changes it everywhere it’s referenced. If you update the business phone number custom value, every template and workflow using that variable reflects the new number on the next send.

This is a powerful capability for agency operations. Update a client’s hours seasonally, change promotional messaging, or rotate featured services — all by changing a single custom value that propagates across the entire location.

Common Questions

How do I reference custom values in templates? Custom values appear as merge fields in the template editor. The exact syntax depends on the context, but it’s typically {{custom_values.variable_name}}.

Can I use custom values in workflow actions? Yes. Any workflow action that supports merge fields can reference custom values.

What’s the difference between custom values and custom fields? Custom values are location-wide constants (same for everyone). Custom fields are per-record data (different for each contact).

Back to GHL MCP Guide