> For the complete documentation index, see [llms.txt](https://docs.borndigital.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.borndigital.ai/digital-agent/conversation-flow/nodes-explained/decision-node.md).

# DECISION node

In this example overview, prerequisites are established through the ['Function' node](/digital-agent/conversation-flow/nodes-explained/function-node.md) or some variable in the[ 'Answer' node ](/digital-agent/conversation-flow/nodes-explained/answer-node.md)before reaching the 'Decision' node. To witness its application, refer to the chapter [Creating Your First Virtual Assistant](/digital-agent/building-new-projects.md):

* **County:** Tracks the number of times the user crosses the ['Function' node](/digital-agent/conversation-flow/nodes-explained/function-node.md).
* **Value:** Assuming the value is set to 32, multiple scenarios are crafted based on these values to bifurcate the [Conversation Flow](/digital-agent/conversation-flow.md).

<figure><img src="/files/KhqAGJijZRNMu65j92Gs" alt=""><figcaption><p>Decision node in nutshell</p></figcaption></figure>

Precise conditions within the ['Decision' node](/digital-agent/conversation-flow/nodes-explained/decision-node.md) hold utmost significance. Conditions are processed sequentially, moving from the first to the last. When a condition is met, the connected target node is triggered.&#x20;

In cases where no conditions match, the ['Decision' node](/digital-agent/conversation-flow/nodes-explained/decision-node.md) resorts to the 'Other' path, similar to a fallback function seen in other nodes. Visualize it as akin to an SQL Case function (when/else logic).

{% hint style="info" %}
Consider altering the condition order based on your flow logic and priority for optimal decision-making within your [Conversation Flow](/digital-agent/conversation-flow.md)
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.borndigital.ai/digital-agent/conversation-flow/nodes-explained/decision-node.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.