← All N8N workflows
Automation & utilitiesChatChat TriggerCodeHTTP RequestIf

receive chat events and http request and respond to chat

Configured with Chat, Chat Trigger, HTTP Request, Wait. Review the connections and setup before adapting this template.

Workflow preview
TriggerWhen chat messagereceivedChat TriggerWeb / APICreate ThreadHTTP RequestWeb / APIStart RunHTTP RequestTransformPoll StateEdit FieldsWaitWaitWaitWeb / APIGet runHTTP RequestRoutingIfIfWeb / APIGet MessageHTTP RequestTransformSet responseEdit FieldsRoutingIf1IfTransformMerge Thread IDEdit FieldsTransformMerge Thread ID1Edit FieldsTransformMergeMergeIntegrationRespond to ChatChatTransformCreate payloadEdit FieldsCodeSimple Thread StorageCodeCodeSimple Thread Storage 2CodeTransformSet thread idEdit Fields

Node categories in this workflow

  • Trigger
  • Web / API
  • Transform
  • Wait
  • Routing
  • Integration
  • Code

Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.

Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.

How it works

The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.

Workflow node names, types, and operations
NodeCategoryTypeOperation
When chat message receivedTriggerChat TriggerSee node parameters
Create ThreadWeb / APIHTTP RequestPOST
Start RunWeb / APIHTTP RequestPOST
Poll StateTransformEdit FieldsSee node parameters
WaitWaitWaitSee node parameters
Get runWeb / APIHTTP RequestSee node parameters
IfRoutingIfSee node parameters
Get MessageWeb / APIHTTP RequestSee node parameters
Set responseTransformEdit FieldsSee node parameters
If1RoutingIfSee node parameters
Merge Thread IDTransformEdit FieldsSee node parameters
Merge Thread ID1TransformEdit FieldsSee node parameters
MergeTransformMergeSee node parameters
Respond to ChatIntegrationChatSee node parameters
Create payloadTransformEdit FieldsSee node parameters
Simple Thread StorageCodeCodeSee node parameters
Simple Thread Storage 2CodeCodeSee node parameters
Set thread idTransformEdit FieldsSee node parameters

Setup

  1. Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
  2. Connect your own credentials through n8n’s credential store. Replace REPLACE_WITH_* values with your resource identifiers.
  3. Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
  4. Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.

Requirements

An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.

Credential types declared in the source

  • httpBasicAuth

Workflow notes

receive chat events and http request and respond to chat

receive chat events and http request and respond to chat

Purpose and structure

This folder contains the receive chat events and http request and respond to chat workflow. Its executable nodes use chat, chatTrigger, code, httpRequest, if, merge, set, wait. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.

Setup

Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.

Entry points

When chat message received

Verification

Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.

Attribution

https://github.com/blackbaddl13/r-KSODI-POC/blob/cbbe896ee41d933b114ddb8886c5a23d9b1bca89/n8n.json MIT; preserve source notices.

More in Automation & utilities