Orchestrator v2 - Enhanced
Configured with Chain LLM, Chat Trigger, Email Send, HTTP Request, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- AI & models
- Code
- Web / API
- Data store
- Routing
- Messaging
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.
| Node | Category | Type | Operation |
|---|---|---|---|
| When chat message received | Trigger | Chat Trigger | See node parameters |
| Ollama Chat Model | AI & models | LM Chat Ollama | See node parameters |
| The Brain | AI & models | Chain LLM | See node parameters |
| The Processor | Code | Code | See node parameters |
| The Router | Web / API | HTTP Request | See node parameters |
| Response Processor | Code | Code | See node parameters |
| Store Request Log | Data store | N8N Data Store | create |
| Store Analytics | Data store | N8N Data Store | create |
| Check for Email | Routing | If | See node parameters |
| Send Notification | Messaging | Email Send | See node parameters |
| Generate Summary | Code | Code | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- 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
ollamaApi
Workflow notes
Orchestrator v2 - Enhanced
Orchestrator v2 - Enhanced
Purpose and structure
This folder contains the Orchestrator v2 - Enhanced workflow. Its executable nodes use chainLlm, chatTrigger, code, emailSend, httpRequest, if, lmChatOllama, n8nDataStore. 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
Nik Bear Brown; rights confirmed 2026-10-19 MIT; preserve source notices.