This guide walks you through the process of integrating your GoHighLevel (GHL) CRM with your HealthSherpa Medicare account.

This works with all GHL/LeadConnector white-labels too – such as Done For You, AgentCRM, GoGuru, or any other white-label.

If you have any questions, email medicare-integrations@healthsherpa.com.

This streamlines your workflow from GHL, to quoting, to enrollment, eliminating dual data entry.

GHL contacts sync to HealthSherpa Medicare in real-time – both when created and when updated:

Each GHL contact gets a unique link to their HealthSherpa Medicare quoting session:

So, your GHL contact data flows to HealthSherpa Medicare all the way through quoting and enrollment – eliminating double data entry:

To send data from HealthSherpa Medicare back to GoHighLevel, you'll want to set up our webhook.

Make sure:

To set up the integration, watch this video – or follow the instructions below.

⚠️ If you need to edit Location IDs after generating your key, contact us: medicare-integrations@healthsherpa.com (soon you'll be able to do this yourself).

Log into your HealthSherpa Medicare account, and in the same browser, click one of these install links:

You’ll land on this page – scroll down and click the Next button:

Select the GHL Sub-account you'd like to integrate with:

Enter the API key you generated and press Verify & Install:

You'll be directed to HealthSherpa Medicare, and see this success message:

To set up Workflows, watch this video, or follow the instructions below.

In GHL, go to Settings > Custom Fields and add two custom fields attached to the Contacts object.

Then repeat the above, but using hsmedicare_redirect_url as the field name:

​

To access your Workflows in GHL, navigate to the Automations page.

1. Click the Create Workflow button, and select Start From Scratch:

2. Click Add New Trigger and choose Contact Created, then click the Save Trigger button.

(If you want, you can add a filter here. For example, if you have ACA and Medicare contacts, you can add a filter for contacts tagged "Medicare.")

3. Then, below that Contact Created trigger, click the plus sign to add an action, choose Assign to User, select yourself as the user, then click Save Trigger.

4. Add the Create Contact V1 workflow action defined in the HealthSherpa Medicare for Workflows app.

Then you'll see all of the fields that can be written to on HealthSherpa, and which fields from GHL should map to them. Make any edits you need here. When you're done, press the Save Action button.

5. Click the plus sign below Create Contact v1 to add an action, then:

6. Optional: Click "Test workflow" to test that a Contact is successfully created. If you have any issues, click into the "Execution logs" and click "View Details" for clues.

7. Finally, Save (if it isn't auto-saved) and Publish your Workflow to set it live:

Now you'll go through similar steps, but for the Update Contact Workflow, to trigger the Contact record in HealthSherpa to be updated to match the Contact record in GHL.

1. Go back to your Automations page, click the Create Workflow button, and select Start From Scratch.

2. Click Add New Trigger and choose Contact Changed.

3. Click Add Filters. Here's you'll choose which fields should – upon having their value updated – trigger this Workflow. For example, if you select email, then if the email in GHL, then the entire Contact record (not just the email field) will be updated on HealthSherpa.

​Important: these are AND filters, not OR filters, so you should only set 1 filter per trigger. Most likely, you'll want to set up multiple filters – in which case you'd add multiple triggers, with a filter each, like this:

4. Add the Update Contact V1 workflow action defined in the HealthSherpa Medicare for Workflows app.

Then you'll see all of the fields that can be written on HealthSherpa, and which fields from GHL should map to them. Make any edits you need here. When you're done, press the Save Action button.

5. Finally, Save (if it isn't auto-saved) and Publish your Workflow to set it live:

⚠️ Important: Make sure each contact is assigned to an agent with a HealthSherpa account and is connected to your agency. The sync will not occur if there is no agent assigned to the Contact.

⚠️ Important: If you'll be updating a contact's assigned agent over time, you'll need a separate custom Workflow – see below for how handle that.

Here's how to move all or some of your existing GHL Contacts over to HealthSherpa Medicare at once:

Tip: When backfilling many contacts at once, you might encounter a “Too Many Requests” error. In our internal testing, batches of ~20 contacts processed reliably; higher volumes (50–100) had intermittent failures. Consider chunking your batches into smaller sets to avoid this error.​

If you use GHL in a way where contacts may be reassigned from one agent to another over time, you’ll need to add a separate Reassignment Workflow to keep your sync working as expected.

Without this workflow, updating a contact’s assigned agent will fail to sync, because the contact remains tied to the original agent’s HealthSherpa account.

You'll account for this by building a Reassignment Workflow:

This workflow triggers when a contact's assigned agent changes and syncs the contact to the new agent’s HealthSherpa account.

⚠️ Important: This is not a true "transfer” of the Contact record in HealthSherpa – it results in a new contact being created in HealthSherpa, in the new agent's account.

Step 1. Create a new workflow

Step 2. Add conditional logic (important!)

This prevents the workflow from running for brand new contacts (since those should use the Create Contact workflow instead). It ensures this workflow only runs when an already-synced contact is being reassigned.

Step 3. Add the Create Contact workflow action

Step 4. Update the custom fields

What to expect

Let us know at medicare-integrations@healthsherpa.com if you have any questions.

​

Some agencies set up their GHL principal agent as a Sub-account, and downline agents are Users below that Sub-account. Other agencies set up their GHL principal agent as an Agency, and each downline agent is a Sub-account below that Agency. If you're operating this way, here's what you need to do:

⚠️ After you create your API key, if you need to add or remove Location IDs, go to your Integrations tab in HS, scroll to the GHL card, and click Update Location Id.

Below are the contact fields HealthSherpa expects, with their rules. Any optional fields that did not pass validation will be ignored and contact creation/update will sync, so long as the required fields pass validation:

If our two custom fields aren’t updating, or if the "Update contact" workflow has stopped working (even though the workflow log shows “success”) you may have a broken field mapping.

This is likely due to an action version number change. This can happen if you’ve deleted and re-added, or added more than one “Create Contact” action – which increments the internal action number – for example, if you've added a second Create Contact action it will be called "#2 Create Contact v1" and the custom field value hsmedicare_create_contact_v1.1.data.redirect_url will change to hsmedicare_create_contact_v1.2.data.redirect_url.

In other words, this error happens if the number on the right doesn't match the number on the left here:

To fix this issue: reopen your “Update Contact Field” action in your Create Workflow, re-select the correct two custom fields from the dropdown menu, save, and publish. If that doesn't work, delete and re-add the action:

In your GHL account, click into Settings and then Business Profile:

Not yet.

Yes, to send data from HealthSherpa Medicare back to GoHighLevel, you'll want to set up our webhook.

Note, you don't need a GHL API key for the above setup, only if you're also setting up our Webhook. For most users, you'll find your API key on the Settings > Business Profile page – see here for a video walkthrough. Some versions of GoHighLevel (such as GoGuru), only have it available under the "Private Integrations" page (also known as the "API keys" page) – to get it there, 1) click new integration 2) give it a name 3) for Scopes, select Edit Contacts and View Contacts, 4) you'll see a popup with your API key, like this.

​

If you're using AgentCRM, they've created a workflow template you can use, saving you some steps. See this video walkthrough, and reach out to them with questions.

​