> For the complete documentation index, see [llms.txt](https://docs-conversational-ai.syntphony.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-conversational-ai.syntphony.com/build-dialogs/workspace-cells.md).

# Workspace Cells

Build and customize the logic of each flow directly in the Workspace.

**Workspace Cells** are available directly in the **Workspace**, allowing you to shape the behavior and progression of a specific flow as you build it.

**Learn more about** [<mark style="color:blue;">**Workspace**</mark>](https://docs-conversational-ai.syntphony.com/studio/workspace.md)

Use them to collect user input, process information, evaluate conditions, control navigation, route conversations, and define when a flow should end. Since they are created as part of the flow itself, each cell can be configured according to the needs of that particular conversational path.

Workspace Cells include Input, Code, Rule, Jump, Transfer, and End, covering different aspects of flow execution and orchestration:

* **Input:** waits for and collects user input, with the option to store it for later use.&#x20;
* **Code:** processes data.&#x20;
* **Rule:** evaluates conditions and defines different paths in a flow.&#x20;
* **Jump:** redirects execution to another cell or flow.&#x20;
* **Transfer:** routes conversations between NLU flows and AI Agents.
* **End:** ends the current flow execution.&#x20;

Explore each cell to understand its configuration, behavior, and recommended use cases.


---

# 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-conversational-ai.syntphony.com/build-dialogs/workspace-cells.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.
