Path: Connectors → High Level → Configuration
What this page does
Some external systems are multi-tenant on your side — you might run several agencies, sub-accounts, or locations in the same vendor's product. High Level (GHL) is the canonical example: a single agency in High Level often manages dozens of sub-accounts, each with its own contacts, pipelines, and credentials.
Multi-instance connectors mirror this. You add as many instances as you need — Main Agency, West Coast Sub-Account, demo client, whatever — and Wazzi keeps them isolated. The MCP tools are namespaced per-instance so an AI agent can call "list contacts in Main Agency" or "create opportunity in West Coast" unambiguously.
Before you start — what you'll need from High Level
For each instance you want to add, you'll need two things:
- Location ID — the GHL location / sub-account ID. Find it in High Level under Settings → Business Profile → Location ID (it's a long alphanumeric string starting with
Zrg...). - Private Integration Token (PIT) — High Level's recommended way to authenticate API calls. Create one in Settings → Integrations → Private Integrations → + Create new integration. Grant it the scopes your team needs (Contacts, Opportunities, Calendars, Conversations, etc.).
Don't use a Marketplace App API key for this — it's a different auth flow. PITs are easier to manage and revoke per-instance.
What this connector unlocks for your team
Once configured, members with the right MCP permissions can ask Claude / ChatGPT / Cursor things like:
- "Show me all contacts in Main Agency tagged 'hot lead'."
- "Create an opportunity in West Coast worth $5k for the contact john@acme.com."
- "Find all appointments in Main Agency scheduled for next Tuesday."
- "Send a SMS to contact ID 12345 saying we'll follow up."
The exact set of available actions depends on which MCP toggles you've flipped on for the user's group — see Managing Permissions.
Steps
1. From the Connectors catalog, click Configure on the High Level tile.
You'll see the empty Configuration tab with an Add Instance button:
2. Click Add Instance.
A form appears asking for an instance Name, the Location ID, and an API Key (the Private Integration Token):
3. Fill in the form.
- Name — anything human-readable; this is just so your team can tell which instance is which when looking at the dropdown or invoking MCP tools. Examples: Main Agency, West Coast Sub-Account, Acme Corp (demo).
- Location ID — the GHL location / sub-account ID.
- API Key — your Private Integration Token.
Naming tip. If you have multiple instances, use a consistent format like
<Region> <Account>or<Customer Name> (<Environment>). Future-you will be grateful when there are 12 instances and you need to remember which one is the staging one.
4. Click Save Configuration.
The instance saves and the connector status flips to active. Repeat steps 2 to 4 for each additional instance.
The instance dropdown at the top of the form lets you switch between them. If a single instance has bad credentials, you'll see something like this:
This is exactly what you'll see in real life if a sub-account is deleted, an API token is rotated, or an integration is revoked. The connector dot turns red on the catalog page until the issue is fixed. Click Test Connection to surface the exact error.
The Access tab — permissions and data source linkage
Switch to the Access tab on the High Level edit page:
This tab does three jobs:
- MCP URL — copy this and paste it into your AI tool. The same URL covers all instances of the connector — instance selection happens at tool-call time. See Connecting Claude or Connecting ChatGPT.
- Manage Permissions — quick link to Managing Permissions filtered to High Level. Once you've granted a group Read + Create permissions, the access summary on this tab will reflect it.
- Manage Data Sources — quick link to Configuring Data Sources filtered to High Level. If you've wired GHL to power Portfolio Center categories (Contacts, Opportunities, Activity, Appointments), they'll show up listed here.
Troubleshooting
- "Test Connection failed: 401 Unauthorized" on a brand-new instance. PIT is wrong, copied incompletely, or already revoked in GHL. Generate a fresh PIT and try again. Make sure you're not using a Marketplace App key by mistake.
- "Test Connection failed: 404 Not Found." Location ID is wrong, or the location was deleted in High Level. Verify in GHL Settings → Business Profile.
- "Test Connection failed: 403 Forbidden." PIT is valid but lacks scopes. In GHL, edit the Private Integration and tick the scopes you need (Contacts, Opportunities, etc.).
- Test passes but MCP calls fail with 403 from the AI tool. Two possibilities: (a) the user invoking the call doesn't have the right MCP permission in Wazzi (see Managing Permissions), or (b) the PIT scope doesn't cover that specific action even though basic auth works. Re-edit the PIT in GHL and add the missing scope.
- An instance worked yesterday and fails today. Most common cause: someone rotated the PIT in GHL without updating Wazzi. Open the instance in Wazzi and update the API Key field.
- "Sub-account suspended" type error. Customer-side issue. Follow up with the GHL account holder for that location.
Best practices
- Name instances by their real-world identity, not their order. "West Coast" is durable; "Instance 2" breaks the moment you add a third.
- One instance per real-world boundary. Don't try to combine two distinct sub-accounts into one Wazzi instance — credentials don't compose, and the AI's mental model breaks.
- Use scoped PITs. Grant only the GHL scopes your team's MCP usage requires. Reduces blast radius if a token leaks.
- Plan for rotation. Set a reminder to rotate PITs every 90 days. Doing it in Wazzi is a 30-second update; doing it under pressure after a compromise is much worse.
- Test Connection after every credential change. Cheap, immediate feedback.
Frequently asked questions
How many GHL instances can I add?
No hard cap. Practically, more than ~20 starts to feel cluttered in the dropdown — consider whether you really need that many distinct ones.
Can different instances have different permissions per group?
Currently permissions are at the connector level, not per-instance. If you need per-instance access control, the workaround is to put each sub-account in a separate Wazzi org, but that's heavy.
Does removing an instance delete data from High Level?
No. Removing a Wazzi instance only invalidates Wazzi's stored credentials and unlinks any data sources pointing at that instance. The actual data in GHL is untouched.
Can I rename an instance?
Yes — open the instance, edit the Name field, save. The MCP tool names update immediately.
What's next
- Restrict who in your org can invoke GHL actions: Managing Permissions.
- Use the GHL connector to feed Wazzi's Portfolio Center: Configuring Data Sources.
- For a simpler single-instance pattern, see Setting Up the Asana Connector.
- To wire GHL into your AI tool, see Connecting Claude or Connecting ChatGPT.