My workflow 3
Configured with Agent, Aggregate, Chain Retrieval Qa, Chat Trigger, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- Routing
- Transform
- AI & models
- Code
- Web / API
- Messaging
- Data store
- Files / media
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 |
|---|---|---|---|
| On form submission4 | Trigger | Form Trigger | See node parameters |
| Loop Over Items1 | Routing | Loop Over Items | See node parameters |
| If2 | Routing | If | See node parameters |
| Aggregate1 | Transform | Aggregate | See node parameters |
| Google Gemini Chat Model5 | AI & models | LM Chat Google Gemini | See node parameters |
| split the binary item | Code | Code | See node parameters |
| Parsing the document | Web / API | HTTP Request | POST |
| Check the parsing status | Web / API | HTTP Request | See node parameters |
| Provide the markdown | Web / API | HTTP Request | See node parameters |
| Google Gemini Chat Model6 | AI & models | LM Chat Google Gemini | See node parameters |
| Markdown | Transform | Markdown | See node parameters |
| Gmail | Messaging | Gmail | See node parameters |
| Code | Code | Code | See node parameters |
| Convert to File | Transform | Convert To File | toText |
| AI Agent | AI & models | Agent | See node parameters |
| Google Gemini Chat Model | AI & models | LM Chat Google Gemini | See node parameters |
| Information Extractor | AI & models | Information Extractor | See node parameters |
| Google Gemini Chat Model1 | AI & models | LM Chat Google Gemini | See node parameters |
| Convert to File4 | Transform | Convert To File | toText |
| Pinecone Vector Store | Data store | Vector Store Pinecone | See node parameters |
| Embeddings Mistral Cloud | AI & models | Embeddings Mistral Cloud | See node parameters |
| Default Data Loader | Files / media | Document Default Data Loader | See node parameters |
| Recursive Character Text Splitter | Transform | Text Splitter Recursive Character Text Splitter | See node parameters |
| When chat message received | Trigger | Chat Trigger | See node parameters |
| Question and Answer Chain | AI & models | Chain Retrieval Qa | See node parameters |
| Google Gemini Chat Model2 | AI & models | LM Chat Google Gemini | See node parameters |
| Vector Store Retriever | AI & models | Retriever Vector Store | See node parameters |
| Pinecone Vector Store1 | Data store | Vector Store Pinecone | See node parameters |
| Embeddings Mistral Cloud1 | AI & models | Embeddings Mistral Cloud | See node parameters |
| AI Agent1 | AI & models | Agent | See node parameters |
| Google Gemini Chat Model3 | AI & models | LM Chat Google Gemini | See node parameters |
| Translator Agent | AI & models | Agent | See node parameters |
| Analyzer Agent | AI & models | Agent | 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
None declared. HTTP requests and Code nodes may still need configuration.
Workflow notes
I'm a note
I'm a note
The below workflow is a chatbot workflow which will be triggered when a user types his/her prompt related to document the user provided for analysis on the chatbot link which was ent to the user via mail.
I'm a note
I'm a note
These two subflows are for trial purpose
I'm a note
I'm a note
This subflow is responsible for storing the translated as well as the analyzed contents into the vector database to feed as a knowledge to the chatbot
My workflow 3
My workflow 3
Purpose and structure
This folder contains the My workflow 3 workflow. Its executable nodes use agent, aggregate, chainRetrievalQa, chatTrigger, code, convertToFile, documentDefaultDataLoader, embeddingsMistralCloud, formTrigger, gmail, httpRequest, if, informationExtractor, lmChatGoogleGemini, markdown, retrieverVectorStore, splitInBatches, textSplitterRecursiveCharacterTextSplitter, vectorStorePinecone. 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
On form submission4, 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/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Code/1818_Code_Converttofile_Automate_Webhook.json MIT; preserve source notices.