Skip to content

Commit b06a93c

Browse files
committed
Move page to own node and add page to nave
1 parent 0221bde commit b06a93c

File tree

3 files changed

+5
-4
lines changed

3 files changed

+5
-4
lines changed

docs/integrations/builtin/core-nodes/n8n-nodes-langchain.chattrigger/index.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -80,7 +80,7 @@ If you select any option other than **Off**, you must connect the Chat trigger a
8080
Use this option when building a workflow with steps after the agent or chain that's handling the chat. Choose from:
8181

8282
* **When Last Node Finishes**: The Chat Trigger node returns the response code and the data output from the last node executed in the workflow.
83-
* **Using Response Nodes**: The Chat Trigger node responds as defined in a [Respond to Chat](/update/this/link/once/RespondToChat/hasItsOwnPage.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.
83+
* **Using Response Nodes**: The Chat Trigger node responds as defined in a [Respond to Chat](/integrations/builtin/core-nodes/n8n-nodes-langchain.respondtochat.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.
8484

8585
/// note | Using Response Nodes
8686
This mode replaces the 'Using Respond to Webhook Node' mode from version 1.2 of the Chat Trigger node.
@@ -116,7 +116,7 @@ If you select any option other than **Off**, you must connect the Chat trigger a
116116
Use this option when building a workflow with steps after the agent or chain that's handling the chat. Choose from:
117117

118118
* **When Last Node Finishes**: The Chat Trigger node returns the response code and the data output from the last node executed in the workflow.
119-
* **Using Response Nodes**: The Chat Trigger node responds as defined in a [Respond to Chat](/update/this/link/once/RespondToChat/hasItsOwnPage.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.
119+
* **Using Response Nodes**: The Chat Trigger node responds as defined in a [Respond to Chat](/integrations/builtin/core-nodes/n8n-nodes-langchain.respondtochat.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.
120120

121121
/// note | Using Response Nodes
122122
This mode replaces the 'Using Respond to Webhook Node' mode from version 1.2 of the Chat Trigger node.
@@ -140,7 +140,7 @@ In a basic workflow, the Agent and Chain nodes output a parameter named either `
140140
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.
141141

142142
/// note | Respond to Chat node
143-
When you are using a [Respond to Chat](/path/still/tbd) node to manually create the response sent to the user, you must set the Chat Trigger response mode to 'Using Response Nodes'.
143+
When you are using a [Respond to Chat](/integrations/builtin/core-nodes/n8n-nodes-langchain.respondtochat.md) node to manually create the response sent to the user, you must set the Chat Trigger response mode to 'Using Response Nodes'.
144144
///
145145

146146
## Common issues

docs/integrations/builtin/core-nodes/n8n-nodes-langchain.chattrigger/respondtochat.md renamed to docs/integrations/builtin/core-nodes/n8n-nodes-langchain.respondtochat.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ priority: critical
77

88
# Respond to Chat node
99

10-
Use the Respond to Chat node in correspondence with the Chat Trigger node to send a response into the chat and optionally wait for a response from the user. This allows you to have multiple chat interactions within a single execution and enables human-in-the-loop use cases in the chat.
10+
Use the Respond to Chat node in correspondence with the [Chat Trigger](/integrations/builtin/core-nodes/n8n-nodes-langchain.chattrigger/index.md) node to send a response into the chat and optionally wait for a response from the user. This allows you to have multiple chat interactions within a single execution and enables human-in-the-loop use cases in the chat.
1111

1212
/// note | Chat Trigger node
1313
The Respond to Chat node requires a [Chat Trigger](/integrations/builtin/core-nodes/n8n-nodes-langchain.chattrigger/index.md) node to be present in the workflow, with the [Response Mode](/integrations/builtin/core-nodes/n8n-nodes-langchain.chattrigger/index.md#response-mode) set to 'Using Response Nodes'.

nav.yml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -229,6 +229,7 @@ nav:
229229
- integrations/builtin/core-nodes/n8n-nodes-base.removeduplicates/index.md
230230
- Templates and examples: integrations/builtin/core-nodes/n8n-nodes-base.removeduplicates/templates-and-examples.md
231231
- integrations/builtin/core-nodes/n8n-nodes-base.renamekeys.md
232+
- Respond to Chat: integrations/builtin/core-nodes/n8n-nodes-langchain.respondtochat.md
232233
- integrations/builtin/core-nodes/n8n-nodes-base.respondtowebhook.md
233234
- integrations/builtin/core-nodes/n8n-nodes-base.rssfeedread.md
234235
- RSS Feed Trigger: integrations/builtin/core-nodes/n8n-nodes-base.rssfeedreadtrigger.md

0 commit comments

Comments
 (0)