> ## Documentation Index
> Fetch the complete documentation index at: https://docs.meetdarwin.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Send leads to HubSpot

> Create or update a HubSpot contact for every lead Darwin captures in your website chat, through Zapier and without code.

<div className="darwin-location"><strong>Runs through</strong> Zapier → Darwin + HubSpot <a href="https://app.meetdarwin.ai/admin/settings/api">Open API settings ↗</a></div>

When a visitor leaves their name and email in Darwin's chat, Zapier creates the contact in HubSpot, or updates the one with the same email, with the page they chatted on and a link to the conversation.

<Note>
  This connection runs through Zapier: Darwin's Zapier app starts the Zap and Zapier's HubSpot app does the work in HubSpot. You choose the fields. This recipe is a two-step Zap, which Zapier's free plan includes.
</Note>

## Before you start

* A HubSpot account, free or paid. The person who connects HubSpot to Zapier needs Super Admin permission in HubSpot.
* Darwin added to your Zapier account and a Darwin key for Zapier. [Connect Zapier](/integrations/zapier) covers both in two minutes.

## Create a contact for every new lead

<Steps>
  <Step title="Choose the Darwin trigger">
    In Zapier, create a Zap. For the trigger, choose **Darwin** and the event **New Lead**. Connect your Darwin account with the key, then select **Test trigger** to load a sample.
  </Step>

  <Step title="Add the HubSpot action">
    Choose **HubSpot** as the action app and the event **Create or Update Contact**, then connect your HubSpot account.
  </Step>

  <Step title="Map the fields">
    Darwin's lead carries **Email**, **First name**, **Last name**, **Company** and **Phone** when the visitor gave them, plus **Page URL**, **Traffic source**, the UTM values, Darwin's grade and **Darwin url**, a link to the conversation. Map at least the email:

    | HubSpot field | Darwin field |
    | - | - |
    | Email | Email |
    | First Name | First name |
    | Last Name | Last name |
    | Company Name | Company |
    | Phone Number | Phone |
  </Step>

  <Step title="Test and publish">
    Test the action, check the result in HubSpot, then publish the Zap. The next lead from your website appears in HubSpot within a minute.
  </Step>
</Steps>

## Also useful

* **Log the conversation link.** Put **Darwin url** in a HubSpot contact property so a rep can open the whole chat from the record.
* **Book-ready visitors.** A second Zap on **Meeting Booked** can update the same contact, so reps see who booked from the chat.
* **Link the records back.** Add Darwin's **Create or Update Contact** action with **External ID** set to the HubSpot record ID, so both systems point at each other. Steps after the first need a paid Zapier plan.

## Good to know

* The Zap acts on leads from the moment you turn it on. Earlier leads are in Darwin under Conversations, which you can download as a CSV.
* Darwin sends each lead once. If the same person chats again with the same email, HubSpot updates the contact instead of adding another.

<AccordionGroup>
  <Accordion title="Darwin isn't listed in Zapier">
    Darwin is in private beta on Zapier. Open the invite link in [Connect Zapier](/integrations/zapier) while signed in to the Zapier account you build Zaps in.
  </Accordion>

  <Accordion title="Is this a native HubSpot integration?">
    No. It runs through Zapier: Darwin's Zapier app starts the Zap and Zapier's HubSpot app creates the contact. You choose which fields go where.
  </Accordion>

  <Accordion title="My Agent Studio test didn't start the Zap">
    Preview conversations never start a Zap, so testing your agent doesn't fill your tools. Chat on your live website to test end to end, or use the samples from **Test trigger**.
  </Accordion>
</AccordionGroup>

[Connect Zapier →](/integrations/zapier) · [All Darwin triggers and actions →](/integrations/zapier#triggers) · [Webhooks and the API →](/api-reference/introduction)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.