# Node

**Nodes are the key components of a workflow**, enabling the execution of a series of operations by connecting nodes with different functionalities.

## Core Nodes

<table data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>Start</strong></td><td>Defines the initial parameters for starting a workflow process.</td></tr><tr><td><strong>End</strong></td><td>Defines the final output content for ending a workflow process.</td></tr><tr><td><strong>Answer</strong></td><td>Defines the response content in a Chatflow process.</td></tr><tr><td><strong>Large Language Model (LLM)</strong></td><td>Calls a large language model to answer questions or process natural language.</td></tr><tr><td><strong>Knowledge Retrieval</strong></td><td>Retrieves text content related to user questions from a knowledge base, which can serve as context for downstream LLM nodes.</td></tr><tr><td><strong>Question Classifier</strong></td><td>By defining classification descriptions, the LLM can select the matching classification based on user input.</td></tr><tr><td><strong>IF/ELSE</strong></td><td>Allows you to split the workflow into two branches based on if/else conditions.</td></tr><tr><td><strong>Code Execution</strong></td><td>Runs Python/NodeJS code to execute custom logic such as data transformation within the workflow.</td></tr><tr><td><strong>Template</strong></td><td>Enables flexible data transformation and text processing using Jinja2, a Python templating language.</td></tr><tr><td><strong>Variable Aggregator</strong></td><td>Aggregates variables from multiple branches into one variable for unified configuration of downstream nodes.</td></tr><tr><td><strong>Variable Assigner</strong></td><td>The variable assigner node is used to assign values to writable variables.</td></tr><tr><td><strong>Parameter Extractor</strong></td><td>Uses LLM to infer and extract structured parameters from natural language for subsequent tool calls or HTTP requests.</td></tr><tr><td><strong>Iteration</strong></td><td>Executes multiple steps on list objects until all results are output.</td></tr><tr><td><strong>HTTP Request</strong></td><td>Allows sending server requests via the HTTP protocol, suitable for retrieving external results, webhooks, generating images, and other scenarios.</td></tr><tr><td><strong>Tools</strong></td><td>Enables calling built-in Vord tools, custom tools, sub-workflows, and more within the workflow.</td></tr></tbody></table>


---

# Agent Instructions: 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:

```
GET https://docs.glik.ai/deprecation/orchestration-interface/node-orchestration/node.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
