Start free

Send enquiries to your tools with n8n

Each time a visitor leaves an enquiry, the Hazelchat Trigger starts your n8n workflow, on n8n Cloud or your own n8n. Business and Scale, on any website platform.

Hazelchat nodes for n8nSee the four steps

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

How an enquiry reaches your tools through n8n A visitor leaves an enquiry in the chat on your website. Hazelchat saves it in your workspace and sends its fields to n8n: 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. n8n 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 Hazelchat Trigger, signed n8n Starts your workflow · n8n Cloud or your own 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 Zapier, Make and n8n and copy it. It is shown once.

  3. In n8n

    Add the trigger

    Search the nodes panel for Hazelchat, add the Hazelchat Trigger and create a Hazelchat API credential with that key.

  4. On your site

    Test, then publish

    Click “Listen for test event” and leave a made-up enquiry, then publish the workflow. Hazelchat marks each enquiry it sends.

We tested the nodes on a self-hosted n8n on 13 October 2026. Your n8n must be reachable at a public HTTPS address, as n8n Cloud is. If it is not, use the Hazelchat node’s Get Many with n8n’s Schedule Trigger.

What goes to n8n

  • Sent

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

  • Left out

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

Hazelchat signs every delivery, and the trigger checks the signature before your workflow runs, so a forged or replayed request starts nothing.

Visitor text is untrusted plain text. Escape it before using it in HTML or email templates. “Sent to n8n” means n8n accepted the enquiry; it does not show that your workflow finished or that the enquiry is a qualified lead.

Your data controls still apply

Enquiries go to n8n (n8n Cloud in the EU, or your own server) and on to the tools in your workflow. Connect only tools you trust. Pausing capture, turning details off or losing the plan cancels pending delivery. Unpublish the workflow or revoke the key to stop it.

Deleting an enquiry in Hazelchat cannot remove copies already in n8n’s execution history or in another tool. A request already in flight cannot be recalled. Arrange deletion in those tools separately.

Help and technical reference

For help with a workflow, ask in the n8n community forum. For anything in Hazelchat, write to hello@hazelchat.co. The enquiry API reference describes the key, the routes, the fields and the signature. The nodes have one trigger and one action, Get Many, which only reads enquiries.

Every new enquiry, in your own workflow.

Enquiry delivery is part of Business and Scale. See pricing.

Start free