View the technical docs for our webhook here:
https://docs.medicare.healthsherpa.com/webhooks/introduction

Push enrollment data to your CRM automatically

Our webhook pushes real-time enrollment data directly to your CRM or system of record at the moment an enrollment is submitted.

No exports, no manual dual entry, no lag.

Getting started

Create a HealthSherpa Medicare account
Go to the Integrations tab and in the Webhook card, click Add webhook.
Enter your Destination URL. This is the URL where we’ll send enrollment submission payloads. Your CRM should provide this to you.
Choose an Authentication method:
- API Key: Enter the API key from your CRM or destination system. We’ll send it as an X-API-Key header.
- None: Use this only if your destination URL already includes authentication or your endpoint does not require authentication.
Click Save webhook.
You'll then implement your destination URL to ingest the Submission Payload Schema. Use our Test button to send a sample payload to your destination URL that you can test with.

Video tutorials

These walkthroughs show how to connect your HealthSherpa Medicare webhook to a CRM. Before following along, make sure you've completed the Getting Started steps above to activate your webhook.

Setting up with your CRM directly (Salesforce, GoHighLevel, Zoho, etc.)

Use this if your CRM supports inbound webhooks natively – most do, including GoHighLevel (Automations), Salesforce (Flows), and Zoho (Flows).

Setting up with Zapier

Use this if you want to route enrollment data to any app Zapier supports – Trello, Google Sheets, HubSpot, and hundreds more.

Fields included

We include fields from the enrollment and contact records – see the full list here.

A note about agency accounts:
Your agency account and any connected downline agent accounts are included in the scope of this webhook.

Enrollments from accounts joined to you as captive agents send all application and all contact fields in the payload.
Enrollments from accounts joined to you as independent agents send all application fields and a limited subset of contact fields. See details here.
See the Submission payload schema for full field details.

A note about external_id:

If a contact is created directly in the HealthSherpa UI (rather than passed in via API), the webhook will return external_id: null. You can backfill this value using the PATCH endpoint on the Contacts API – see the contact schema docs for details. Once set, all future webhooks for that contact will include the external_id.

Agency accounts

You can connect webhooks to agent or agency accounts.

If you're connecting to an agency account, any downline agent accounts will be included in the scope of your webhook, meaning their enrollment submissions will trigger the sending of the payload to your webhook.

Note: The scope of webhooks is intra-agency, it doesn't extend to sub-agencies. Each agnecy/sub-agency will need to set up their own webhook.

Note: Captive downline agents can't set up webhooks, only the Primary Admin can.

Details

Event triggers

Currently, one event trigger is supported: enrollment submission. We may add more in the future.

Retries

There are three automatic retries if the webhook fails – at 20 seconds, 10 minutes, and 1 hour after the initial delivery.

Terms of Service

By adding a webhook, you're agreeing to send consumer data, including protected health information (PHI), to your destination URL in compliance with the HealthSherpa Terms of Service. You are responsible for ensuring your endpoint and any downstream systems handle this data in accordance with applicable privacy and security requirements.

FAQ

What's a webhook?

Our webhook is an automated, real-time notification system that sends data from our platform to your CRM instantly when an enrollment submission event occurs.

What's a destination URL?

A destination URL (also called a callback URL or webhook URL) is a web address your CRM generates that can receive data.

What's an API key?

An API key is a password-like string your CRM generates so we can authenticate when sending data to your endpoint. Some CRMs do not require a separate API key because authentication is built into the webhook URL. In this case, choose None as the authentication method. Only choose this option if your destination URL is already protected or your endpoint does not require authentication.

What triggers this webhook?

This webhook triggers when you submit an enrollment through our platform. Manually added enrollments don't trigger the webhook. We're aiming to add more triggers soon.

Does this work with my CRM?

The webhook works with any system that can receive an HTTP POST request to a URL. This includes GoHighLevel, Salesforce, Zoho, MedicarePro, Onyx, AgencyBloc, GoGuruX, EnrollHere, HubSpot, and most modern CRMs. You can also use Zapier or Make to connect to CRMs that don't have native inbound webhooks.

Does the webhook distinguish between new enrollments and re-submits?

No. Every enrollment submission fires the same event with the same payload structure regardless of whether it's a new enrollment, rewrite, or replacement.

What should I use to deduplicate or match contacts?

We recommend matching on first name + last name + MBI, or first name + last name + date of birth. The confirmation_number field is guaranteed unique per enrollment. The contact id is a stable UUID for each contact in our system.

Is my client data safe?

HealthSherpa does not sell, market to, or otherwise use your client data. The webhook sends data only to the destination URL you provide. See our privacy policy for details.

Where do I get my API Key on GoHighLevel?

It's on your Business Profile Settings page. See here for a video walkthrough.

Can my downline agents see the webhooks I set up for that?

No, if your downline agents look at their Integrations page, they won't see webhooks you've set up for them.

Can my independent agents set up their own webhooks?

Yes, whether or not you've set up webhooks as an agency, your independent agents can always add webhooks to their account.

How does this work with agency accounts?

In an agency context, only Primary Admins will be able to view and edit agency-level webhooks. Independent downline agents can add and manage their own agent-level webhooks. Captive downline agents do not see the webhook card. Please note that the scope of webhooks is intra-agency, it doesn't include sub-agencies.

Can I edit a webhook?
Not yet. To change a webhook, delete the webhook and add a new one.