> For the complete documentation index, see [llms.txt](https://docs.n8n.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-langchain.chattrigger.md).

# Chat Trigger

Use the Chat Trigger node when building AI workflows for chatbots and other chat interfaces. You can configure how users access the chat, using one of n8n's provided interfaces, or your own. You can add authentication.

You must connect either an agent or chain [root node](/integrations/builtin/cluster-nodes/root-nodes.md).

{% hint style="warning" %}
**Workflow execution usage**

Every message to the Chat Trigger executes your workflow. This means that one conversation where a user sends 10 messages uses 10 executions from your execution allowance. Check your payment plan for details of your allowance.
{% endhint %}

{% hint style="info" %}
**Manual Chat trigger**

This node replaces the Manual Chat Trigger node from version 1.24.0.
{% endhint %}

## Node parameters <a href="#node-parameters" id="node-parameters"></a>

### Make Chat Publicly Available <a href="#make-chat-publicly-available" id="make-chat-publicly-available"></a>

Set whether the chat should be publicly available (turned on) or only available through the manual chat interface (turned off).

Leave this turned off while you're building the workflow. Turn it on when you're ready to publish the workflow and allow users to access the chat.

#### Mode <a href="#mode" id="mode"></a>

Choose how users access the chat. Select from:

* **Hosted Chat**: Use n8n's hosted chat interface. Recommended for most users because you can configure the interface using the [node options](#node-options) and don't have to do any other setup.
* **Embedded Chat**: This option requires you to create your own chat interface. You can use n8n's [chat widget](https://www.npmjs.com/package/@n8n/chat) or build your own. Your chat interface must call the webhook URL shown in **Chat URL** in the node.

#### Authentication <a href="#authentication" id="authentication"></a>

Choose whether and how to restrict access to the chat. Select from:

* **None**: The chat doesn't use authentication. Anyone can use the chat.
* **Basic Auth**: The chat uses basic authentication.
  * Select or create a **Credential for Basic Auth** with a username and password. All users must use the same username and password.
* **n8n User Auth**: Only users logged in to an n8n account can use the chat.

#### Initial Message(s) <a href="#initial-messages" id="initial-messages"></a>

This parameter's only available if you're using **Hosted Chat**. Use it to configure the message the n8n chat interface displays when the user arrives on the page.

### Make Available in n8n Chat <a href="#make-available-in-n8n-chat" id="make-available-in-n8n-chat"></a>

Choose whether to make the agent available to Chat Hub.

#### Agent Name <a href="#agent-name" id="agent-name"></a>

The name of the agent on Chat Hub.

#### Agent description <a href="#agent-description" id="agent-description"></a>

The description of the agent on Chat Hub.

## Node options <a href="#node-options" id="node-options"></a>

Available options depend on the chat mode.

### Hosted chat options <a href="#hosted-chat-options" id="hosted-chat-options"></a>

#### Allowed Origin (CORS) <a href="#allowed-origin-cors" id="allowed-origin-cors"></a>

Set the origins that can access the chat URL. Enter a comma-separated list of URLs allowed for cross-origin non-preflight requests.

Use `*` (default) to allow all origins.

#### Input Placeholder, Title, and Subtitle <a href="#input-placeholder-title-and-subtitle" id="input-placeholder-title-and-subtitle"></a>

Enter the text for these elements in the chat interface.

<details>

<summary>View screenshot</summary>

![Customizable text elements](/files/2mmV3lvJ6PWN9KdffS2f)

</details>

#### Load Previous Session <a href="#load-previous-session" id="load-previous-session"></a>

Select whether to load chat messages from a previous chat session.

If you select any option other than **Off**, you must connect the Chat trigger and the Agent you're using to a memory sub-node. The memory connector on the Chat trigger appears when you set **Load Previous Session** to **From Memory**. n8n recommends connecting both the Chat trigger and Agent to the same memory sub-node, as this ensures a single source of truth for both nodes.

<details>

<summary>View screenshot</summary>

![Connect nodes to memory](/files/dUzpxhLJEjSKMl8bNYi4)

</details>

#### Response Mode <a href="#response-mode" id="response-mode"></a>

Use this option when building a workflow with steps after the agent or chain that's handling the chat. Choose from:

* **When Last Node Finishes**: The Chat Trigger node returns the response code and the data output from the last node executed in the workflow.
* **Using Response Nodes**: The Chat Trigger node responds as defined in a [Chat](/integrations/builtin/core-nodes/n8n-nodes-langchain.chat.md) node or [Respond to Webhook](/integrations/builtin/core-nodes/n8n-nodes-base.respondtowebhook.md) node. In this response mode, the Chat Trigger will solely show messages as defined in these nodes and not output the data from the last node executed in the workflow.

{% hint style="info" %}
**Using Response Nodes**

This mode replaces the 'Using Respond to Webhook Node' mode from version 1.2 of the Chat Trigger node.
{% endhint %}

* **Streaming response**: Enables real-time data streaming back to the user as the workflow processes. Requires nodes with streaming support in the workflow (for example, the [AI agent](https://github.com/n8n-io/n8n-docs/blob/main/docs/integrations/builtin/cluster-nodes/root-nodes/n8n-nodes-langchain.agent) node).

#### Require Button Click to Start Chat <a href="#require-button-click-to-start-chat" id="require-button-click-to-start-chat"></a>

Set whether to display a **New Conversation** button on the chat interface (turned on) or not (turned off).

<details>

<summary>View screenshot</summary>

![New Conversation button](/files/n5rqy1GTgRznHyq3T77B)

</details>

### Embedded chat options <a href="#embedded-chat-options" id="embedded-chat-options"></a>

#### Allowed Origin (CORS) <a href="#allowed-origin-cors" id="allowed-origin-cors"></a>

Set the origins that can access the chat URL. Enter a comma-separated list of URLs allowed for cross-origin non-preflight requests.

Use `*` (default) to allow all origins.

#### Load Previous Session <a href="#load-previous-session" id="load-previous-session"></a>

Select whether to load chat messages from a previous chat session.

If you select any option other than **Off**, you must connect the Chat trigger and the Agent you're using to a memory sub-node. The memory connector on the Chat trigger appears when you set **Load Previous Session** to **From Memory**. n8n recommends connecting both the Chat trigger and Agent to the same memory sub-node, as this ensures a single source of truth for both nodes.

<details>

<summary>View screenshot</summary>

![Connect nodes to memory](/files/dUzpxhLJEjSKMl8bNYi4)

</details>

#### Response Mode <a href="#response-mode" id="response-mode"></a>

Use this option when building a workflow with steps after the agent or chain that's handling the chat. Choose from:

* **When Last Node Finishes**: The Chat Trigger node returns the response code and the data output from the last node executed in the workflow.
* **Using Response Nodes**: The Chat Trigger node responds as defined in a [Chat](/integrations/builtin/core-nodes/n8n-nodes-langchain.chat.md) node or [Respond to Webhook](/integrations/builtin/core-nodes/n8n-nodes-base.respondtowebhook.md) node. In this response mode, the Chat Trigger will solely show messages as defined in these nodes and not output the data from the last node executed in the workflow.

{% hint style="info" %}
**Using Response Nodes**

This mode replaces the 'Using Respond to Webhook Node' mode from version 1.2 of the Chat Trigger node.
{% endhint %}

* **Streaming response**: Enables real-time data streaming back to the user as the workflow processes. Requires nodes with streaming support enabled.

## Templates and examples <a href="#templates-and-examples" id="templates-and-examples"></a>

[Browse n8n-nodes-base.compression integration templates](https://n8n.io/integrations/chat-trigger) or [search all templates](https://n8n.io/workflows/)

## Related resources <a href="#related-resources" id="related-resources"></a>

View n8n's [Advanced AI](https://github.com/n8n-io/n8n-docs/blob/main/advanced-ai/index.md) documentation.

## Set the chat response manually <a href="#set-the-chat-response-manually" id="set-the-chat-response-manually"></a>

You need to manually set the chat response when you don't want to directly send the output of an Agent or Chain node to the user. Instead, you want to take the output of an Agent or Chain node and modify it or do something else with it before sending it back to the user.

In a basic workflow, the Agent and Chain nodes output a parameter named either `output` or `text`, and the Chat trigger sends the value of this parameter to the user as the chat response.

If you need to manually create the response sent to the user, you must create a parameter named either `text` or `output`. If you use a different parameter name, the Chat trigger sends the entire object as its response, not just the value.

{% hint style="info" %}
**Chat node**

When you are using a [Chat](/integrations/builtin/core-nodes/n8n-nodes-langchain.chat.md) node to manually create the response sent to the user, you must set the Chat Trigger response mode to 'Using Response Nodes'.
{% endhint %}

## Common issues <a href="#common-issues" id="common-issues"></a>

For common questions or issues and suggested solutions, refer to [Common Issues](/integrations/builtin/core-nodes/n8n-nodes-langchain.chattrigger/common-issues.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-langchain.chattrigger.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.