Skip to main content
When a sub-account uses GoHighLevel, your agent books into a GoHighLevel calendar, applies GoHighLevel tags, and writes GoHighLevel custom fields. Every one of those has an id inside the sub-account, and the settings that use them want the id, not the label. The dashboard reads the sub-account for you, so you pick them by name. A sub-account that keeps its contacts in Team Follow Up has its own calendars and its own custom fields instead. See Calendars and booking and Contacts without a CRM. Contacts change in GoHighLevel through the agent’s skills and the campaign’s workflow. The pickers can also create a new tag, or turn on a calendar, for you.

​
What you can read

Custom fields and custom values belong to the sub-account the agent’s project is connected to; calendars and tags likewise. Resolve them for that locationId, never for another client’s.

​
Using them in the prompt

Pick a custom field from the prompt’s Variable button, under Custom fields. It goes in as a short token, like {{what_service}}, and the lead’s answer is filled in when the call is placed. The agent can then say “I see you were asking about a kitchen remodel” rather than “you asked about our services”. In the prompt, the line reads Service they asked about, followed by the what_service field. On the call it reads kitchen remodel, and the agent says: I see you were asking about a kitchen remodel. In the prompt, the line reads Service they asked about, followed by the what_service field. On the call it reads kitchen remodel, and the agent says: I see you were asking about a kitchen remodel. Put the field in the prompt’s context and tell the agent what to do with it, rather than writing it inside a line the agent reads out. A lead with no answer leaves the token unfilled, so say what to do when it’s missing. See CRM context fields and The prompt.

​
When the connection is not healthy

Every setting that reaches into GoHighLevel depends on the project’s connection. Three error codes tell you what kind of broken it is: In the dashboard, a tag or calendar list that comes back empty can also mean the connection is broken. See Agencies, projects and sub-accounts for project states.

​
Boundaries

  • The dashboard reads the sub-account when a page loads. A tag created in GoHighLevel after that shows up once you reload the page, and custom fields have a Refresh button.
  • Ids are per sub-account. A calendar id from one client’s sub-account means nothing in another’s. This is why a master agent binds assets by name.
  • The dashboard’s contact lookup finds a contact by phone number only.

​
In the API

The CRM lookups the dashboard uses (tags, calendars, custom fields, custom values and the contact lookup) are not part of the public API. Read them from your CRM directly, then pass the ids to the settings that want them: