Send Leads to HubSpot with Webhooks

When a visitor fills in your chatbot's lead form, Hyperleap AI can send the details to a URL within seconds. HubSpot can't create a new contact from that request by itself, so a no-code tool sits in between: it receives the lead and creates or updates the contact in HubSpot. This guide uses Make, and covers Zapier as an alternative.

Setup takes about 15 minutes and needs no code.

Tip:

HubSpot workflows have a "When a webhook is received" trigger, but it only enrolls a contact that already exists in HubSpot. It can't create the contact for a new lead, which is why this guide uses Make or Zapier.

Before You Start

Hyperleap AI Pro or Max — Webhooks are on Pro and Max. See Webhooks for the full feature.
A website chatbot with the lead form switched on — Ask for an email and make it required. HubSpot identifies contacts by email. The Lead Captured event fires when a visitor submits the lead form in the website widget; without a lead form, visitors chat anonymously and there's nothing to send.
A Make account (or a paid Zapier plan) and a HubSpot user who can create and edit contacts.

Setup with Make

1. Create the webhook in Make

Start a scenario

In Make, create a new scenario. Name it something like "Hyperleap leads to HubSpot".

Add a Custom webhook

Add the Webhooks app and choose Custom webhook. Click Add, name the webhook, and save. Make shows the webhook address.

Copy the address

Copy the address. Make now waits for a first request so it can learn the shape of the data. Leave the scenario open.

Note:

Anyone who has this address can send data into your scenario. Paste it only into Hyperleap AI.

2. Point your chatbot at Make

Open Webhooks & Zapier

In Hyperleap AI Studio, open your chatbot, select the Integrations tab, and choose "Webhooks & Zapier".

Create a Lead Captured subscription

Under Subscriptions, paste the Make address into "Public HTTPS destination", set Event to Lead Captured, and click "Create subscription". It takes effect straight away.

Note the signing secret

Hyperleap AI shows the subscription's signing secret once. You don't need it for this setup; click "I have saved the secret".

3. Send a test lead

Open your chatbot where visitors see it (your website, or its public shareable URL) and fill in the lead form with test details. Make should show "Successfully determined" on the webhook. In Hyperleap AI, "Delivery history" should list a lead.captured delivery with a 2xx response.

4. Create or update the HubSpot contact

Add the HubSpot module

After the webhook, add the HubSpot CRM app and choose the module that creates or updates a contact. Connect your HubSpot account when Make asks.

Map the fields

Map the fields from the test lead, using the table below. Email is the one that matters most: it lets HubSpot update a returning visitor's contact instead of creating a duplicate.

From Hyperleap AI	HubSpot property	Notes
`data.email`	Email	HubSpot uses email to find an existing contact, so map it. An empty string if the visitor didn’t give one.
`data.name`	First name	The full name the visitor typed. The lead form has one name field, so it all goes into First name.
`data.phone`	Phone number	Includes the country code, for example +15551234567. Map it only if your lead form makes phone required: a blank phone arrives as "+".
`data.customFields.<field id>`	A custom contact property	One value per custom lead-form question, keyed by the field id set in the lead form.
`data.attribution.utmSource, utmCampaign, gclid, landingPage`	Custom contact properties (optional)	Where the visitor came from, when the website widget captured it.
`chatbotName`	A custom property (optional)	Useful when several chatbots send leads to one HubSpot account.

To keep custom lead-form answers, create matching contact properties in HubSpot first (Settings → Properties), then map each one. You can also set a fixed value, such as Lead status "New", so your team can find chatbot leads.

5. Turn the scenario on

Save the scenario, set it to run immediately as data arrives, and switch it on. Submit the lead form once more with a new test email and check the contact appears in HubSpot. Delete the test contacts when you're done.

Make counts each module run as an operation, so every lead uses a few operations from your Make plan. Check Make's pricing for your allowance.

Using Zapier Instead

Zapier works the same way. Webhooks are included on Zapier's paid plans, not on Free.

Catch the webhook

Create a Zap with Webhooks by Zapier → Catch Hook as the trigger and copy its URL.

Create the subscription and test

Create the Lead Captured subscription in Hyperleap AI with that URL, as in step 2, then send a test lead and let Zapier find it.

Add the HubSpot action

Add HubSpot as the action, choose the action that creates or updates a contact, and map the fields from the table above. Publish the Zap.

What Gets Sent

Example lead.captured request

{
  "eventType": "lead.captured",
  "chatbotId": "a1b2c3d4-...",
  "chatbotName": "Website Assistant",
  "timestamp": "2026-11-15T10:30:00Z",
  "deliveryId": "d9e0f1a2-...",
  "data": {
    "name": "Jane Smith",
    "email": "jane@example.com",
    "phone": "+15551234567",
    "customFields": { "budget": "5k" },
    "attribution": { "utmSource": "google", "utmCampaign": "spring-promo" }
  }
}

The full payload reference is in Webhooks.

Troubleshooting

No delivery appears in Delivery history — The lead form wasn't submitted, or the subscription is for a different chatbot or event.
Deliveries fail with a 4xx code — The address is wrong, or the Make webhook was deleted or left unused for days. Copy the address again and recreate the subscription.
Make received the lead but HubSpot has no contact — Check the scenario history for the HubSpot error. The usual causes are an empty email or Phone mapped while your form leaves it optional.
The whole name is in First name — Expected. The lead form asks for one name, so Hyperleap AI sends it as one value.

Next Steps

Send leads to Salesforce — The same setup for Salesforce Leads
Send leads to GoHighLevel — Directly into a HighLevel workflow
Webhooks — Every event, payload, and the retry rules