> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cognigy.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Nodes

<a href="/release-notes/2025.24"><Badge className="version-badge" color="blue">Updated in 2025.24</Badge></a>

*Nodes* are the fundamental building blocks of [Flows](/ai/agents/develop/projects-and-flows/overview). Nodes define the logic of AI Agents and are used to create complex conversational experiences. Each Node represents a specific action, decision point, or interaction in the Flow. Users can configure and connect Nodes to design guided interactions between AI Agents and users.

Cognigy.AI provides a wide range of [Node types](/ai/agents/develop/node-reference/overview) to allow diverse conversational experiences.

Some Node types, for example, [If Nodes](/ai/agents/develop/node-reference/logic/if) and [Lookup Nodes](/ai/agents/develop/node-reference/logic/lookup), include child Nodes to control the Flow execution logic. Child Nodes function as a decision branch in the Flow, allowing different outcomes depending on the user input.

## Working with Nodes

<Tabs>
  <Tab title="GUI">
    You can create and delete Nodes in the [Flow editor](/ai/agents/develop/projects-and-flows/editor). To edit a Node, open the Node editor by clicking the Node in the Flow editor. Node editors include settings specific to each Node type. In the Flow editor, you can also right-click a Node to copy, cut, and paste the Node as well as add comments to it.

    <Tip>
      To speed up building your AI Agent, use [keyboard shortcuts](/ai/administer/hotkeys).
    </Tip>
  </Tab>

  <Tab title="API">
    You can view, create, edit, and delete Nodes using the [Cognigy.AI API](https://api-trial.cognigy.ai/openapi#tag--Charts-v2.0). You can also search and move Nodes and add Locales to them. For Nodes that support Generative AI output, you can generate this kind of output through the API as well.
  </Tab>
</Tabs>

### JSON Data Fields in the Node Editor

Some Nodes, such as the [Say Node](/ai/agents/develop/node-reference/basic/say) or [Question Node](/ai/agents/develop/node-reference/basic/question), include JSON fields to send a `data` object with the output.

<Note>
  The JSON fields enforce JSON formatting at the root level. If you directly enter an array into a JSON field, for example, `["name", "surname", "email"]`, the Node unpacks the array into an object. The result is an object at the root level, for example, `{"0": "name", "1": "surname", "2": "email"}`.
</Note>

### Set Nodes as Entrypoints

If your AI Agent has, for example, a [Go To Node](/ai/agents/develop/node-reference/logic/go-to) or an [Execute Flow Node](/ai/agents/develop/node-reference/logic/execute-flow) to switch between Flows, you can set a Node as an *Entrypoint*. An Entrypoint is the Node at which the Flow starts. The **Start** Node is the default Entrypoint. To set a Node as an Entrypoint:

* right-click the Node in the Flow editor and select **Set Entrypoint**.
* select <img src="https://mintcdn.com/cognigy-15abf2ba/sIAERK2J23A3FpS0/_assets/icons/black-and-white/vertical-ellipsis.svg?fit=max&auto=format&n=sIAERK2J23A3FpS0&q=85&s=6d2d4d534ed7e5d4ea9442c1c11f87c8" alt="vertical ellipsis" width="20" height="20" data-path="_assets/icons/black-and-white/vertical-ellipsis.svg" /> **> Set Entrypoint** in the Node editor.

<Accordion title="Naming Entrypoints">
  Define unique names for each Entrypoint Node using the **Label** field in the Node editor's **Settings** section. This approach is helpful to easily differentiate a Node with an Entrypoint from other Nodes of the same type.
</Accordion>

### Create Flows from Node Branches

You can split complex Flows and create new ones from a child Node. To do so, right-click the child Node and select the **Create Flow from Branch** option in the context menu.

When you create a Flow from a child Node, you move the Nodes following the child Node to the new Flow. In the original Flow, these Nodes are replaced with an Execute Flow Node. The Execute Flow Node triggers the new Flow.

<Warning>
  NLU and Flow settings aren't copied to the new Flow. Check and adjust the **NLU** tab settings of the new Flow.
</Warning>

## Dynamic Content in Nodes

Most Nodes support [CognigyScript](/ai/platform-features/cognigyscript) and [Tokens](/ai/platform-features/tokens) for dynamic content use.

## Fallback Value in Node Fields

A *fallback value* is a default value automatically applied when required fields are empty due to updates in a Node. Fallback values keep existing Nodes working when new fields are added or existing ones are changed, so you don't need to reconfigure them immediately.

Fallback values are typically applied in the following cases:

* When a Node field is updated in a new release version.
* When a new Node field is added to the Node.
* When you upload a new version of the Node Extension.

Fields that use a fallback value are marked with the fallback icon <img src="https://mintcdn.com/cognigy-15abf2ba/I0ba9I1paCAUpGLP/_assets/icons/black-and-white/fallback.svg?fit=max&auto=format&n=I0ba9I1paCAUpGLP&q=85&s=55a74bdc77eae95a2b654bd565f28cf6" alt="fallback" width="24" height="24" data-path="_assets/icons/black-and-white/fallback.svg" />. After you update and save the field, the icon disappears.

## More Information

* [CognigyScript](/ai/platform-features/cognigyscript)
* [Tokens](/ai/platform-features/tokens)
* [Flows](/ai/agents/develop/projects-and-flows/overview)