Turn website chat enquiries into HubSpot contacts
Each enquiry your AI chat agent collects creates a HubSpot contact from the visitor’s email address, or updates the contact when it already exists. Your follow-up starts from one record instead of a forwarded email.
Sending enquiries to your tools is part of the Starter, Business and Scale plans. On Free, enquiries wait in Hazelchat. See pricing.
HubSpotFictional sample
- Contact email
- alex@example.com Mapped by the template
- Name
- Alex Example You map it
- Message
- Could you fit a team of 12 on Friday evening? You map it
What arrives in HubSpot
Zapier’s public template “Create or update HubSpot contacts from new Hazelchat enquiries” starts from Hazelchat’s New Enquiry trigger. This is what it puts in HubSpot:
| In HubSpot | From the template |
|---|---|
| Contact Email | The visitor’s email address. HubSpot finds the contact by it, or creates one. |
| Name and message | Not pre-mapped. HubSpot shows its contact properties only after you connect your account, so you map the name and message to the properties you use. |
| Website | Never mapped. It is your own website, not the visitor’s company. |
Conversation transcripts and your agent’s answers never leave Hazelchat. The link opens the enquiry and its conversation there.
Set it up in four steps
-
In Hazelchat
Switch visitor details on
In Hazelchat Settings, switch visitor details on and leave capture running, so visitors can leave an enquiry.
-
In Hazelchat
Create an API key
Create an API key in the Settings card for Zapier and copy it. It is shown once.
-
In Zapier
Open the template
Open the template in Zapier, connect Hazelchat with that key, then connect HubSpot and map the name and message to your contact properties.
-
On your site
Test, then turn it on
Leave a made-up enquiry in your chat, check what arrives, then turn the Zap on. Hazelchat marks each enquiry it sends.
Good to know
A copy, not a sync
Zapier copies each new enquiry into HubSpot once. Changes in HubSpot do not come back to Hazelchat, and deleting an enquiry in Hazelchat leaves the contact in HubSpot.
Installing the chat on a HubSpot site
This page is about the CRM. To put the agent on a website built with HubSpot’s CMS, see the HubSpot CMS install guide.
Every field the trigger sends
You can map any of these in the Zap, as well as or instead of the template’s choice.
| Field | What it holds |
|---|---|
id | The enquiry’s id in Hazelchat |
created_at | When the enquiry was saved, as an ISO time in UTC |
name | The name the visitor typed |
email | The email address the visitor typed |
message | The visitor’s note, which may run over several lines |
website | The website the chat ran on: yours, not the visitor’s |
last_question | The visitor’s last question before they left their details |
answered | answered or unanswered: whether your agent answered that question, never the answer itself |
enquiry_url | A link to the enquiry in Hazelchat |
utm_source, utm_medium, utm_campaign, utm_content, ad_click_network, referrer_host, chat_started_on and chat_opened_via | Where the visitor came from and where the chat started, each only when the visitor’s browser reported it |
There is no phone, company or consent field. Name, email, message and last question are what the visitor typed: treat them as untrusted text, and escape them before using them in HTML or email templates.
Other ways to send enquiries
Prefer n8n? Start a workflow with the Hazelchat Trigger and add n8n’s own HubSpot node after it. Hazelchat publishes no ready-made n8n workflow for this; the n8n guide covers the trigger.
The same trigger has public templates for Slack, Trello, Microsoft Teams and Google Sheets. The Zapier guide covers the trigger for unanswered questions, the enquiry search and the draft-answer action.
Your data controls still apply
Enquiries go to Zapier (US) and on to HubSpot. Pausing capture, turning visitor details off or leaving the paid plans cancels pending deliveries. Revoke the key to stop them.
Deleting an enquiry in Hazelchat cannot remove the copy already in HubSpot. Delete it there separately.
Every new enquiry, in HubSpot.
Build your AI chat agent first, from your own pages. Send enquiries on once it answers well. See all integrations.