> For the complete documentation index, see [llms.txt](https://docs.zerve.ai/zerve-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zerve.ai/zerve-docs/notebooks/blocks/logic-gate.md).

# Logic gate

Run the next blocks only when a condition is met.

{% hint style="info" %}
Logic gate blocks are only available in the **canvas view**.
{% endhint %}

A **logic gate** block checks conditions on variables from the blocks before it. The blocks after it only run if the conditions are met, so you can build branches into a workflow.

## Conditions

Conditions use variables from the blocks connected before the logic gate. They can check these kinds of variable:

* Integers
* Strings
* Booleans
* Lists

You can combine several conditions into groups, and nest groups inside each other, to build more complex rules.

## Example

A GenAI block scores how relevant a question is to a dataset, from 0 to 10. One logic gate lets the workflow continue to an analysis branch if the score is 5 or more; another sends it to a different branch if the score is below 5.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zerve.ai/zerve-docs/notebooks/blocks/logic-gate.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.