Skip to main content

Connection

Open Sub Accounts → select a location → Connection tab.

This tab groups routing, WhatsApp tunnel/proxy, and automation hooks for one sub-account.

Outbound session selection​

When a sub-account has more than one WhatsApp session (number), WhatGHL must decide which session sends each outbound message from GoHighLevel. You control that with session priority, routing rules on this tab, and optional #WH / #WHN codes in the GHL message body.

  1. Configure outbound session selection (rule list, reorder, enable/disable steps as the UI allows).
  2. Set session priority on each WhatsApp number under Sessions when you use priority-based routing.

Including #WH (or a priority variant like #WH2) in the outbound text tells WhatGHL to prefer a specific session or priority for that message. Full syntax: Message codes from GoHighLevel.

Session selector​

The session selector is an ordered list of rules WhatGHL walks top to bottom whenever a message leaves GoHighLevel for WhatsApp. The first enabled rule that finds a valid session sends the message. You can drag rows to change priority, enable or disable individual rules, and save when you are done.

Typical rules (in the order you set): #WH code in the message, phone digits in contact tags, the GHL user who sent the message, the contact’s assigned owner, and finally a fallback to the first connected session by priority.

Reorder session selector rules on the Connection tab and save the configuration.

Good practices: keep at least one reliable fallback; test with a low-risk outbound after rule changes.

Connection proxy (WhatsApp)​

WhatGHL can route the WhatsApp session tunnel through a residential IP aligned with a country you choose. Use this when the client’s numbers or geography should match the egress region.

  1. Find Connection proxy (WhatsApp) on the Connection tab.
  2. Pick the proxy country (or clear it to use the default path).

Saving applies to that sub-account only. Wrong or frequent region changes can affect session stability — treat it as an infrastructure choice.

n8n Webhook & API​

WhatGHL can integrate with n8n per sub-account:

  1. Open the n8n Webhook & API card on the Connection tab.
  2. Set Webhook URL (n8n) — HTTPS endpoint of your workflow.
  3. Optionally set HMAC key if your workflow verifies signed callbacks.
  4. Set or generate an API key for your n8n credentials (n8n-nodes-whatghl or agency templates).
  5. Save n8n settings.

Treat the API key like a password; use HTTPS only; rotate keys if they leak.