Hazelchat
Start free

Send enquiries to your tools with Make

Each time a visitor leaves an enquiry, Hazelchat’s “Watch new enquiries” trigger starts your Make scenario. Send it to Slack, your CRM, a spreadsheet or any other tool Make connects. Starter, Business and Scale, on any website platform.

Enquiry delivery is part of the Starter, Business and Scale plans. See pricing.

How an enquiry reaches your tools through Make A visitor leaves an enquiry in the chat on your website. Hazelchat saves it in your workspace and sends its fields to Make: name, email, message, website, last visitor question, answer status, time, a link to the enquiry, and where the chat started when the visitor’s browser reported it. Conversation transcripts and AI answers stay in Hazelchat. Make passes the enquiry on to the tools you connect, such as Slack, a CRM or a spreadsheet. Your website A visitor leaves an enquiry in the chat Hazelchat Sent Name, email, message, website, last question, status, time, link Stays here Conversation transcripts and AI answers “Watch new enquiries” Make Starts your scenario · Make (EU or US) Slack A CRM A spreadsheet, and more

Connect in four steps

  1. In Hazelchat

    Switch visitor details on

    In Hazelchat Settings, switch visitor details on and leave capture running.

  2. In Hazelchat

    Create an API key

    Create an API key in the card for Make and copy it. It is shown once.

  3. In Make

    Add the trigger

    Add Hazelchat’s “Watch new enquiries” to a scenario. Create a webhook, add a connection with that key and save. Hazelchat starts sending straight away.

  4. On your site

    Test, then switch it on

    Click “Run once”, leave a made-up enquiry on your website, then switch the scenario on. Hazelchat marks each enquiry it sends.

We tested a Slack message on 12 October 2026. Other tools work through Make in the same way, but we have not tested each one.

What goes to Make

  • Sent

    The enquiry’s name, email, message, website, last visitor question, answer status, time and a link to the enquiry in Hazelchat, plus where the chat came from when the visitor’s browser reported it.

  • Left out

    Preview and owner tests. Conversation transcripts and AI answers stay out.

Visitor text is untrusted plain text. Escape it before using it in HTML or email templates, and switch markdown off when you post it to a shared Slack channel. “Sent to Make” means Make accepted the enquiry; it does not show that your scenario finished or that the enquiry is a qualified lead.

While a scenario is switched off, Make keeps new enquiries in the webhook’s queue and runs them when you switch it on again. To stop sending, delete the webhook in Make or revoke the key in Hazelchat.

Your data controls still apply

Enquiries go to Make, in the EU or the US as your Make account is set up, and on to the tools you connect there. Make keeps scenario history for as long as your Make plan says. Connect only tools you trust. Pausing capture, turning details off or losing the plan cancels pending delivery.

Deleting an enquiry in Hazelchat cannot remove copies already sent to Make or another tool. A request already in flight cannot be recalled. Arrange deletion in those tools separately.

Help and technical reference

For help with a scenario, see the Make Help Center. For anything in Hazelchat, write to hello@hazelchat.co. The enquiry API reference describes the key, the routes and the fields. The app has one trigger, “Watch new enquiries”, and a “Make an API call” module for the same API.

Every new enquiry, where your team already works.

Prefer Zapier or n8n? See the Zapier guide and the n8n guide, or all the ways to connect Hazelchat.