Infrastructure

HighLevel

Connect a HighLevel sub-account to Ploy to see every user of that sub-account and the role each one holds. Ploy can also add users, switch a user between account admin and account user, and take users out of the sub-account.

This integration is in beta

The HighLevel integration is in beta. It was built from HighLevel's documented API and has not yet been run against a live HighLevel account, so some behaviour may differ from what is described here until it has.

The first step of setup is a consent checkbox. Ticking it lets Ploy send redacted error data to its own monitoring when a call to HighLevel fails. Redacted means secrets, tokens and personal details are removed before anything is stored. Ploy uses it only to fix problems with the integration. You need to tick it to continue.

What Ploy reads

  • Every user of the connected sub-account, with their email address, name and role: Account admin, Account user, Agency admin or Agency user.

  • The sub-account itself, by name, so several sub-accounts connected to one Ploy organisation stay separate.

Users HighLevel has deleted are shown as no longer having access. HighLevel has no suspended state, and it does not report when a user last signed in or whether they use two-factor sign-in, so those are not shown. Contacts, opportunities, calendars and conversations are your customers' data, not people with access to HighLevel, and are not read.

One connection covers one sub-account. To cover several, connect each sub-account separately.

What Ploy can change

  • Add a user to the sub-account by email, as an Account user unless you choose Account admin. HighLevel requires a password when a user is created, so Ploy sets a long random one that nobody sees. The new user signs in by choosing "Forgot password" on the HighLevel sign-in page. Adding someone who is already in the sub-account counts as done.

  • Switch a user's role between Account admin and Account user. Agency users cover every sub-account, so their roles are changed from the agency, not from here.

  • Take a user out of the sub-account. A user who also belongs to other sub-accounts keeps those. A user who belongs only to this sub-account is deleted from HighLevel, which HighLevel completes within a few minutes. Agency users are removed from the agency, not from here.

Before you start

You need two things from the sub-account you want to connect:

  1. Its Location ID. In HighLevel, switch to the sub-account, open Settings, then Business Profile, and copy the Location ID. You can also copy the sub-account's address from your browser: Ploy takes the ID out of it.

  2. A Private Integration Token for that sub-account. In the same sub-account, open Settings, then Private Integrations, and create a new integration. Copy the token in full: HighLevel shows it once.

Give the private integration these scopes:

  • View Users and Edit Users, so Ploy can read users and add, change and remove them.

  • View Locations, so Ploy can show the sub-account's name and add users to it.

If Private Integrations is not in your settings, ask your agency admin to enable it for the sub-account.

Connect HighLevel to Ploy

  1. In Ploy, open Integrations and choose HighLevel.

  2. Tick the beta consent checkbox.

  3. Paste the Location ID.

  4. Paste the Private Integration Token.

  5. Select Test connection. Ploy reads the sub-account's users with the token. If the test fails, the message says what to check: a token from a different sub-account, a missing View Users scope, or a token that was deleted.

  6. Save. The first scan runs straight away and then every hour.

Troubleshooting

  • "HighLevel did not accept that Location ID for this token": the token was created in a different sub-account. Create a token in the sub-account whose ID you entered.

  • "That token cannot read this sub-account's users": the token is missing the View Users scope. Edit the private integration in HighLevel and add it.

  • The sub-account shows as an ID instead of its name: the token is missing the View Locations scope. Users are still read.

  • Adding, changing or removing a user fails with a permissions message: the token is missing the Edit Users scope.

Was this helpful?
Was this helpful?