@devries-cameron20 / composio Mirror · read-only
Fork 0

Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

Mirrored from https://github.com/Camo67/composio.git

Synced Nov 21, 06:00 UTC

next
md 73 lines 5.05 KB
Rendered Raw
1 ## How do I set up OAuth credentials for HighLevel Location?
2
3 HighLevel Location has no Composio-managed OAuth app, so to connect with OAuth you create your own app in the HighLevel Marketplace. The Location toolkit connects to a single sub-account (HighLevel calls these locations). For agency-wide access, use the HighLevel Agency toolkit instead.
4
5 ### Create the HighLevel Marketplace app
6
7 1. Sign in to the [HighLevel Marketplace](https://marketplace.gohighlevel.com/) with a developer account, click **My apps**, then click **Create app**.
8
9 ![HighLevel Marketplace My apps page with the Create app button](/images/toolkits/highlevel_location/my-apps-create-app.webp)
10 2. In the **Start from scratch** window, set:
11 - **App name**: any name you'll recognize, such as `Composio Location`.
12 - **App type**: **Private** for testing and small pilots, or **Public** if you plan to list the app.
13 - **Who is the target user of the app?**: **Sub-Account**. The Location toolkit requires this.
14 - **Who can install the app?**: **Everyone**.
15 - **Listing type**: **White-label**.
16
17 ![Start from scratch form with Private, Sub-Account, Everyone and White-label selected](/images/toolkits/highlevel_location/start-from-scratch.webp)
18 3. Click **Create app**.
19 4. Open **Advanced Settings** > **Auth**. In **Redirect URL**, paste `https://backend.composio.dev/api/v1/auth-apps/add` and click **+ Add**. It must exactly match the `oauth_redirect_uri` field in your Composio auth config.
20
21 ![HighLevel Auth settings with the Composio redirect URL under Added redirect URLs](/images/toolkits/highlevel_location/redirect-url-added.webp)
22 5. On the same page, under **Scopes**, search for and tick each scope you need, such as `locations.readonly`. A note like "8 scopes unavailable" is expected: Agency-only scopes are hidden for Sub-Account apps.
23
24 ![HighLevel Scopes section with locations.readonly selected](/images/toolkits/highlevel_location/select-scopes.webp)
25 6. Open **Manage** > **Secrets**. Under **Client keys**, click **+ Add**, name the key, and click **Add**.
26
27 ![HighLevel Client keys section under Manage, Secrets](/images/toolkits/highlevel_location/client-keys.webp)
28
29 ![HighLevel Add a client key dialog](/images/toolkits/highlevel_location/add-client-key.webp)
30 7. Copy the **Client ID** and **Client secret** from the new row.
31
32 A private app active in more than 5 external agencies can't be installed again until you publish it.
33
34 ### Create the auth config in Composio
35
36 1. In the Composio dashboard, go to **Auth Configs**, click **Create**, and select **HighLevel Location** (not HighLevel Agency or HighLevel MCP).
37
38 ![Composio Auth Configs page with the Create button](/images/toolkits/highlevel_location/composio-auth-configs.webp)
39
40 ![Create Auth Config search results showing HighLevel Location](/images/toolkits/highlevel_location/composio-search-highlevel.webp)
41 2. Name the config, click **Next**, and choose **OAuth 2.0**.
42
43 ![HighLevel Location auth config Config Name field](/images/toolkits/highlevel_location/config-name.webp)
44
45 ![HighLevel Location auth config with OAuth 2.0 selected and redacted Client id and Client secret](/images/toolkits/highlevel_location/oauth-credentials.webp)
46 3. Paste the **Client id** and **Client secret**, select the same scopes you chose in HighLevel, and click **Create Auth Config**.
47
48 ![HighLevel Location auth config with the Composio redirect URI and locations.readonly scope](/images/toolkits/highlevel_location/redirect-uri-and-scopes.webp)
49 4. Click **Connect Account** and open the generated link. Sign in to HighLevel, tick the sub-account to connect in **Select Sub-Account**, click **Continue**, then click **Allow & install**. Confirm the account shows as **Active**.
50
51 ![HighLevel Location auth config with the Connect Account button](/images/toolkits/highlevel_location/connect-account.webp)
52
53 ![HighLevel sign-in page](/images/toolkits/highlevel_location/sign-in.webp)
54
55 ![HighLevel Select Sub-Account window with a sub-account ticked and Continue enabled](/images/toolkits/highlevel_location/select-sub-account.webp)
56
57 ![HighLevel Install confirmation page with the Allow & install button](/images/toolkits/highlevel_location/install-confirmation.webp)
58
59 See [Custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
60
61 ### Scopes
62
63 The default auth config requests `locations.readonly`. Customers approve every scope at install time, so request only what your integration uses. If an action fails with insufficient permissions, add the missing scope in both HighLevel and the auth config, then reconnect.
64
65 ### Troubleshooting
66
67 - **No sub-accounts listed when connecting**: check that the app's target user is **Sub-Account** and that the HighLevel user you signed in with can access at least one sub-account.
68 - **Redirect URI mismatch**: the URL in HighLevel and in the auth config must be identical.
69
70 ### Revoke access
71
72 - In Composio, delete the connected account from the auth config, or disable the auth config.
73 - In HighLevel, uninstall the app from the sub-account's installed Marketplace apps. This revokes access immediately.