From 0d005bcee6abe029a2a09363258f69bb9c372679 Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Mon, 24 Aug 2026 16:08:55 +0000 Subject: [PATCH 1/2] docs: clarify HighLevel setup and Salesforce link-namespace troubleshooting --- src/provider-guides/highlevel.mdx | 8 +++++--- src/provider-guides/salesforce.mdx | 7 +++++++ 2 files changed, 12 insertions(+), 3 deletions(-) diff --git a/src/provider-guides/highlevel.mdx b/src/provider-guides/highlevel.mdx index 42e4dec9..1cb837e2 100644 --- a/src/provider-guides/highlevel.mdx +++ b/src/provider-guides/highlevel.mdx @@ -113,13 +113,15 @@ Follow the steps below to create an HighLevel app and add the Ampersand redirect ### Creating Client ID and Client Secret -1. Click **Advanced Settings -> Auth**, select the necessary **Scopes** and enter the **Redirect URL**. - +1. Click **Advanced Settings -> Auth**, select the necessary **Scopes** and enter the **Redirect URL**: `https://api.withampersand.com/callbacks/v1/oauth`. + 2. Click **Add** under **Client Keys** section, enter the Client Name and click **Add**. ![OAuth Creation](/images/provider-guides/highlevel_OAuth.gif) - Provide all the required details and submit them for review. Once the review is complete, your application will go live. +### Submit your app for review + +A HighLevel app cannot be used with Ampersand while it is in draft. After you finish adding the redirect URL, scopes, and client keys, provide all remaining required details in the HighLevel app dashboard and submit the app for review. Your app goes live once HighLevel completes the review. ## Add Your HighLevel App Info to Ampersand diff --git a/src/provider-guides/salesforce.mdx b/src/provider-guides/salesforce.mdx index 1c3b883e..1f764dcd 100644 --- a/src/provider-guides/salesforce.mdx +++ b/src/provider-guides/salesforce.mdx @@ -184,6 +184,13 @@ Please note that namespaces cannot be created in the Dev Hub Org you just enable * When prompted to authenticate, log into the Namespace Org from Step 2. If you are having trouble with this step, try again in an incognito window. * After linking, select **All Namespace Registries** filter to view the namespace. + +If the authentication step returns `error=invalid_client_id&error_description=client identifier invalid` — even in an incognito window — you are almost certainly signing in with the wrong org. Confirm both of the following: + +- You are authenticating with the **Namespace Org** credentials from Step 2, not the Dev Hub Org from Step 1. +- The Namespace Org is a Developer Edition org that does **not** have Dev Hub enabled. Namespaces cannot be created in a Dev Hub Org, and enabling Dev Hub on the org you intended to use as the Namespace Org will surface as this error. If Dev Hub is enabled on it, sign up for a fresh [Developer Edition org](https://developer.salesforce.com/signup), register the namespace there, and link that org instead. + + ![Link namespace](/images/provider-guides/salesforce/link-namespace.png) ![View namespaces](/images/provider-guides/salesforce/view-all-namespaces.png) From a1114a8b13f4506b52e8d24461a289ef212b6c3e Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Mon, 24 Aug 2026 16:10:51 +0000 Subject: [PATCH 2/2] docs: add SEO descriptions and remove em-dash clause joins --- src/provider-guides/highlevel.mdx | 1 + src/provider-guides/salesforce.mdx | 3 ++- 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/src/provider-guides/highlevel.mdx b/src/provider-guides/highlevel.mdx index 1cb837e2..e3239dbf 100644 --- a/src/provider-guides/highlevel.mdx +++ b/src/provider-guides/highlevel.mdx @@ -1,5 +1,6 @@ --- title: HighLevel +description: "Connect HighLevel to Ampersand: create the OAuth app, add the Ampersand redirect URL, submit it for review, and configure Client ID and Secret." --- ## What's Supported diff --git a/src/provider-guides/salesforce.mdx b/src/provider-guides/salesforce.mdx index 1f764dcd..210fed99 100644 --- a/src/provider-guides/salesforce.mdx +++ b/src/provider-guides/salesforce.mdx @@ -1,5 +1,6 @@ --- title: "Salesforce" +description: "Connect Salesforce with Ampersand: enable Dev Hub, register and link a namespace, create an External Client App, and troubleshoot common errors." --- The Salesforce connector supports: @@ -185,7 +186,7 @@ Please note that namespaces cannot be created in the Dev Hub Org you just enable * After linking, select **All Namespace Registries** filter to view the namespace. -If the authentication step returns `error=invalid_client_id&error_description=client identifier invalid` — even in an incognito window — you are almost certainly signing in with the wrong org. Confirm both of the following: +If the authentication step returns `error=invalid_client_id&error_description=client identifier invalid`, even in an incognito window, you are almost certainly signing in with the wrong org. Confirm both of the following: - You are authenticating with the **Namespace Org** credentials from Step 2, not the Dev Hub Org from Step 1. - The Namespace Org is a Developer Edition org that does **not** have Dev Hub enabled. Namespaces cannot be created in a Dev Hub Org, and enabling Dev Hub on the org you intended to use as the Namespace Org will surface as this error. If Dev Hub is enabled on it, sign up for a fresh [Developer Edition org](https://developer.salesforce.com/signup), register the namespace there, and link that org instead.