This reference lists every GoHighLevel integration attribute available in the Newo.ai Builder. Use it alongside the GoHighLevel integration setup guide to understand what each setting controls and how settings depend on each other.

Booking architecture

When a caller requests an appointment, the AI Employee follows a six-step sequence to complete the booking:

The AI Employee conducts the conversation and gathers intent.
The AI Employee determines which calendar to use based on the Calendar Selection Logic (ghl_selection_type).
The AI Employee checks availability in GoHighLevel using the selected calendar (ghl_calendar or a dynamically matched calendar).
The AI Employee confirms a time slot with the caller.
The booking is created in the selected calendar.
Conversation data and call status are synced back to GoHighLevel (if ghl_enable_client_history and ghl_sync_conversation are enabled).

🗒️ NOTE

Steps 2 and 3 depend entirely on the calendar selection logic mode. In Single mode, the calendar is predetermined. In Name or Duration mode, the AI Employee must first identify the correct calendar from the conversation before checking availability.

Connection and authorization

GoHighLevel OAuth code

IDN:ghl_oauth_code

A single-use verification code generated during the OAuth authorization flow. This code establishes the secure connection between Newo.ai and a GoHighLevel sub-account by creating access tokens.

⚠️ CAUTION

The OAuth code expires after a single use. If authorization fails, repeat the entire OAuth flow to generate a new code.

Calendar selection

GoHighLevel Calendar Selection Logic

IDN:ghl_selection_type

Determines how the AI Employee selects a calendar during a booking conversation. Only one mode can be active at a time. Modes cannot be combined.

Mode	Behavior	Requirements
`Single`	Always uses the calendar set in `ghl_calendar`.	`ghl_calendar` must be set.
`Name`	Listens for a service name in the conversation and selects the matching calendar.	`ghl_selection_criteria` must contain selection instructions. Calendar names must match GoHighLevel exactly.
`Duration`	Detects the requested meeting length and selects the calendar with a matching duration.	`ghl_selection_criteria` must contain selection instructions. Separate calendars per duration must exist.

Dependencies:

When set to Single: ghl_calendar is used. ghl_selection_criteria is ignored. ghl_check_availability_on_conversation_start can be enabled.
When set to Name or Duration: ghl_calendar is ignored. ghl_selection_criteria is required. ghl_check_availability_on_conversation_start should be disabled.

GoHighLevel Default Booking Calendar

IDN:ghl_calendar

Specifies which GoHighLevel calendar the AI Employee uses when Calendar Selection Logic is set to Single. This calendar controls available time slots, meeting duration, time zone, assigned user or team, and booking rules.

❗❗ IMPORTANT

This setting is ignored when ghl_selection_type is set to Name or Duration. In those modes, the AI Employee selects a calendar dynamically based on the conversation.

🗒️ NOTE

If you recently added a calendar in GoHighLevel and do not see it in the dropdown, click Publish All to refresh the calendar list.

GoHighLevel AI Selection Instructions

IDN:ghl_selection_criteria

Provides the AI Employee with strict instructions on how to select the correct calendar when using dynamic selection logic.

Output rules:

The AI Employee must return plain text only.
The AI Employee must return a single value.
No explanations or additional text — extra output may break calendar selection.

Name mode example:

Identify the service the caller is requesting.
Available calendars: Consultation, Demo, Onboarding.
Return only one exact calendar name.

Duration mode example:

Extract the appointment duration in minutes from the conversation.
Return only the number (30 or 60).

⚠️ CAUTION

Calendar names in your instructions must match GoHighLevel calendar names exactly. Copy names directly from GoHighLevel to avoid mismatches caused by capitalization, spacing, or punctuation differences.

Time zone

GoHighLevel Detect Time Zone from Conversation

IDN:ghl_use_timezone_from_conversation

Controls whether the AI Employee infers the caller's time zone from the conversation and adjusts available time slots accordingly.

Value	Behavior	Best for
`True`	The AI Employee detects time zone cues (e.g., "I'm in PST") and shows slots in the caller's local time.	Remote or international services.
`False`	The AI Employee uses the calendar's fixed time zone for all slot times.	Local businesses with a physical location.

🗒️ NOTE

Enabling this setting does not change the calendar's configured time zone. It only affects how availability is presented to the caller.

Pre-load availability

GoHighLevel Pre-load Availability on Start

IDN:ghl_check_availability_on_conversation_start

When enabled, the AI Employee checks available time slots as soon as the conversation starts and can proactively suggest times without waiting for the caller to ask.

Dependency: Works only when ghl_selection_type = Single. In Single mode, the AI Employee knows which calendar to check before the conversation begins.

🚨 WARNING

Do not enable this setting with Name or Duration logic. The AI Employee will suggest availability from the wrong calendar before identifying the correct one, leading to incorrect slot offers.

Conversation history

GoHighLevel Save Conversation History

IDN:ghl_enable_client_history

Controls whether full conversation transcripts (voice and chat) are saved to the contact's Notes section in GoHighLevel. When enabled, transcripts appear as entries titled "Voice Agent Conversation Log" under Contacts > select a contact > Notes tab.

Does not affect AI Employee behavior or memory.
Useful for quality control, context transfer to human agents, and dispute resolution.

Call status sync

GoHighLevel Sync Call Status

IDN:ghl_sync_conversation

Syncs the final call outcome to the contact record in GoHighLevel after a conversation ends. Enable this setting only if you use GoHighLevel workflows that trigger on call status changes.

Possible statuses:

Status	Meaning
`completed`	The conversation connected successfully.
`voicemail`	The AI Employee reached an answering machine.
`busy`	The line was busy.
`no-answer`	The phone rang but the caller did not pick up.
`failed`	A connection error occurred.
`canceled`	The call was canceled before connecting.

Pipeline automation

GoHighLevel Update Pipeline Stage

IDN:ghl_update_pipeline

Enables the AI Employee to move opportunity cards between pipeline stages in GoHighLevel based on conversation outcomes. When set to False, all other pipeline settings are ignored.

GoHighLevel Select Pipeline

IDN:ghl_pipeline_item

Specifies which GoHighLevel pipeline the AI Employee updates. Select the pipeline from the dropdown that corresponds to the business process you want to automate.

GoHighLevel Pipeline Stages

IDN:ghl_pipeline_stages

Displays all stages configured in the selected pipeline as a JSON array. Use these exact stage names when writing stage selection rules in ghl_pipeline_criteria.

GoHighLevel Stage Selection Rules

IDN:ghl_pipeline_criteria

Maps conversation outcomes to pipeline stages. Write clear rules that tell the AI Employee which stage to assign based on the call result.

Example:

If the appointment was successfully scheduled, move to "Appointment Scheduled".
If the caller declined to book, move to "Closed Lost".
If the caller requested a callback, move to "New Lead".

❗❗ IMPORTANT

Stage names in your rules must match the exact names shown in ghl_pipeline_stages. Even small differences in capitalization, spacing, or punctuation cause matching failures.

Global security toggles

GoHighLevel Enable Availability Check

IDN:ghl_enable_availability_check

Allows the AI Employee to read available time slots from GoHighLevel calendars. If disabled, the AI Employee cannot tell callers when the business is free. Defaults to True so the AI Employee can check availability immediately after setup.

GoHighLevel Enable Booking

IDN:ghl_enable_booking

Allows the AI Employee to create appointments in GoHighLevel. This is write access to the calendar. If disabled, the AI Employee can check availability but cannot create bookings. Defaults to True so the AI Employee can book appointments immediately after setup.

GoHighLevel Enable Cancellation

IDN:ghl_enable_cancellation

Allows the AI Employee to cancel existing appointments in GoHighLevel. Disable this setting to prevent accidental cancellation of important meetings.

GoHighLevel Check Existing Client

IDN:ghl_check_existing_client

Before starting a conversation, the AI Employee looks up the caller's phone number in GoHighLevel. If found, it pulls the contact's name and history to personalize the interaction.

Publish and refresh rules

After changing any of the following settings, you must click Publish All for the changes to take effect:

ghl_selection_type (Calendar Selection Logic)
ghl_calendar (Default Booking Calendar)
ghl_selection_criteria (AI Selection Instructions)

Without publishing, the AI Employee continues using the previous configuration.

Next steps

Now that you understand the available settings, put them into practice:

Configure the integration end to end. Walk through the full setup — OAuth authorization, calendar selection, global toggles, and publishing — using the step-by-step instructions in GoHighLevel integration.
Build workflow automations. Use the Outbound Call and Send SMS Workflow Actions to trigger the AI Employee from GoHighLevel events like form submissions, tag changes, or pipeline stage updates. See GoHighLevel workflow automation.
Deploy a ready-made scenario. Choose a pre-built scenario with the exact settings and agent instructions already mapped out, so you can go live quickly. See GoHighLevel use cases and scenarios.

GoHighLevel integration

Configure outbound voicemail and call screening detection

GoHighLevel FAQ

GoHighLevel use cases and scenarios

GoHighLevel workflow automation