How to connect HighLevel Location to Composio with your own OAuth app

5 min read

Composio connects AI agents to HighLevel, helping agencies and businesses automate their CRM. With Composio, developers can build agents that work with contacts, conversations, calendars, opportunities, and other sub-account data as part of automated workflows.

Access is always limited to the scopes approved during installation, so each sub-account stays in full control of its data.

Overview

This guide shows you how to create your own app in the HighLevel Marketplace, get its OAuth credentials, and use them to set up a custom auth config for the HighLevel Location toolkit in Composio.

The Location toolkit connects to a single sub-account (HighLevel calls these “locations”). If you need agency-wide access instead, use the HighLevel Agency guide instead.

  • Estimated time: about 10 minutes

  • Difficulty: Beginner, no code required

Before you begin

Make sure you have:

TIP: Keep the HighLevel Marketplace and the Composio Dashboard open in two browser tabs. You’ll copy values between them.

Part 1: Create your HighLevel Marketplace app

NOTE: Already have a Marketplace app that targets sub-accounts, with its Client ID and Client Secret? Skip to Part 2.

Step 1: Create a Marketplace App

1. Sign in to the HighLevel Marketplace, click My apps in the top menu, then click Create app.

My apps page in the HighLevel Marketplace with the Create app button

2. In the Start from scratch window, fill in the fields exactly as shown below:

  • App name: any name you’ll recognize, for example Composio Location Guide.

  • App type: Private for testing and small pilots, or Public if you plan to list the app.

  • Who is the target user of the app? Sub-Account. This is required for the Location toolkit.

  • Who can install the app? Everyone.

  • Listing type: White-label (Recommended).

3. Click Create app.

Start from scratch form with Private, Sub-Account, Everyone and White-label selected

IMPORTANT: Private apps are meant for small pilots. If a private app is active in more than 5 external agencies, new installs are blocked until you publish it.

Step 2: Add the Redirect URL

1. In your new app, open Advanced Settings → Auth from the left sidebar.

2. In the Redirect URL field, paste the Composio callback URL below:

https://backend.composio.dev/api/v1/auth-apps/add

3. Click + Add. The URL now appears under Added redirect URLs.

Composio redirect URL added under Added redirect URLs

IMPORTANT: This URL must match the Redirect URI in your Composio auth config (Step 5) character for character. Even a missing slash will cause the connection to fail.

Step 3: Choose Scopes

Scopes decide what your app is allowed to read or change. Customers must approve every scope when they install the app, so request only what you need.

1. On the same Auth page, scroll down to Scopes.

2. Type a scope name in Search scopes, for example locations.readonly.

3. Tick the checkbox next to each scope you need. The counter at the top shows how many scopes are selected.

locations.readonly scope selected in the Scopes section

NOTE: You’ll see a message like “8 scopes unavailable”. That’s expected: because the target user is Sub-Account, Agency-only scopes are hidden. Write down the scopes you pick, as you’ll select the same ones in Composio.

Step 4: Generate Your Client Keys

1. In the left sidebar, open Manage → Secrets.

2. In the Client keys section, click + Add.

Client keys section under Manage, Secrets

3. Enter a Name for the key, for example Composio Location Guide, and click Add.

Add a client key dialog

4. Copy the Client ID and Client secret from the new row and keep them somewhere safe.

SECURITY: Treat the Client secret like a password. Never share it publicly or commit it to a code repository.

Part 2: Create the auth config in Composio

With your Client ID and Client secret ready, open the Composio Dashboard.

Step 5: Create a HighLevel Location Auth Config

1. In the left sidebar, click Auth Configs, then click + Create in the top-right corner.

Auth Configs page with the Create button

2. In the search box, type HighLevel and select HighLevel Location.

Create Auth Config search results showing HighLevel Location

NOTE: You’ll see three HighLevel toolkits. Pick HighLevel Location, not HighLevel Agency or HighLevel MCP.

3. Enter a Config Name, for example HighLevel Location Guide, and click Next.

Config Name field

4. Under Authentication Method, select OAuth 2.0. Then paste your Client id and Client secret from Step 4.

OAuth 2.0 selected with Client id and Client secret fields

5. Scroll down and check that the Redirect URI shows https://backend.composio.dev/api/v1/auth-apps/add. It must match the URL you added in Step 2.

6. Open the Scopes dropdown and select the same scopes you chose in Step 3.

7. Click Create Auth Config.

Redirect URI and selected scopes in the Composio auth config

Step 6: Connect Your HighLevel Sub-Account

1. Open your new auth config and click + Connect Account. Open the link that Composio generates.

Connect Account button on the auth config

2. Sign in to HighLevel with your email and password, or with Google.

HighLevel sign-in page

3. In the Select Sub-Account window, tick the sub-account you want to connect.

Select Sub-Account window

4. Click Continue.

Sub-account selected with Continue enabled

5. On the Install confirmation page, review the app name, location, and requested permissions, then click Allow & install.

Install confirmation page with Allow and install button

6. You’re sent back to Composio. Your connected account now appears under Accounts with an Active status. 🎉

Active connected account in Composio

Base URL for the HighLevel API

All HighLevel API calls are made via:

https://services.leadconnectorhq.com/

That’s it! Your HighLevel Location + Composio OAuth integration is ready. Copy the Auth Config ID (ac_...) from the auth config page and use it in your code or secret manager.

Troubleshooting

  • “Redirect URI mismatch” error: the URL in HighLevel (Step 2) and in Composio (Step 5) must be identical, including https:// and no trailing spaces.

  • No sub-accounts listed when connecting: make sure the app’s target user is Sub-Account and that the HighLevel user you signed in with has access to at least one sub-account.

  • “Insufficient permissions” when running an action: the action needs a scope you didn’t select. Add it in HighLevel (Step 3) and in Composio, then reconnect the account.

  • Installs blocked: a private app active in more than 5 external agencies can’t be installed again until you publish it.

Revoking Access

You can disconnect HighLevel at any time:

  • In Composio: open the auth config under Auth Configs and delete the connected account, or disable the auth config.

  • In HighLevel: uninstall the app from the sub-account’s installed Marketplace apps. This immediately revokes its access.

Disclaimer: Composio uses AI and may make mistakes, so please review important outputs and confirm sensitive actions.

Share