# Building Workflows

## The Workflows page <a href="#the-workflows-page" id="the-workflows-page"></a>

The [Workflows page](https://automations.ebbot.eu/flows) is your central hub for automation. From here, you can manage your existing flows, browse templates, and monitor the status of your published workflows.

### Creating a new workflow <a href="#creating-a-new-workflow" id="creating-a-new-workflow"></a>

To start building, you can either:

* Create a new workflow from scratch on the [Workflows page](https://automations.ebbot.eu/flows).
* Select a [Template](https://docs.ebbot.ai/ebbot-docs/automations/templates) from the **Templates** tab to start with a pre-filled workflow.

Both actions will open the **Flow Builder**, where you can design your automation visually.

### The Flow builder interface <a href="#the-flow-builder-interface" id="the-flow-builder-interface"></a>

The Flow builder provides a visual canvas for connecting nodes and configuring your automation logic.

* **Building blocks**: Access **Logic**, **Actions**, and **Triggers** from your toolbox, which are populated based on your connected integrations.
* **Workflow management**: The builder provides tools for managing versions, history, and publishing your flows.

Note: If you haven't connected any integrations, your library of actions and triggers will be empty.

### Node error detection <a href="#node-error-detection" id="node-error-detection"></a>

The builder includes real-time validation to ensure your workflows are configured correctly. If a node is missing required information (such as a mandatory API field or a next-step connection), the system will alert you to the problematic nodes.

All errors must be resolved before a workflow can be successfully published.

{% columns %}
{% column %}

<figure><img src="/files/7xz0DR8mc0mQKLljTiJZ" alt=""><figcaption><p>An error is visible in the toolbox and an outline of the node.</p></figcaption></figure>
{% endcolumn %}

{% column %}

<figure><img src="/files/FSeGiGWYgkmmNLbalkYM" alt=""><figcaption><p>In the node settings we can see that the required ticket_id argument is not set.</p></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

All flows in the system that you work with are potential versions that can be published (as long as they have no errors). Only one version of your flow is published at any time.

### Version history <a href="#version-history" id="version-history"></a>

We save a snapshot of your flow each time you make a change to it. You can see your changes in the history:

![Flow history](/files/uSn3kEYjEPM6WiwyZVdY)

You can view any old version and revert to it if necessary.

### Publishing your flow <a href="#publishing-your-flow" id="publishing-your-flow"></a>

You can publish your flow once you're happy with it. The flow will become active as soon as it's published. After your flow is published you can unpublish it to deactivate it.

### Editing your published flow <a href="#changing-your-published-flow" id="changing-your-published-flow"></a>

You can continue to make changes in an existing flow without changing the current live version. You can check the flow history to see which version is live:

![Live version](/files/4Y2FRGYlWPsoFQGpp1Sp)

Hit publish again to publish the version you're currently working with.

### Flow testing <a href="#flow-testing" id="flow-testing"></a>

There's currently no support for testing a flow except for taking it live. We recommend that you test your flows against a testing environment of your ticketing system before wiring it up to your live environment.


---

# 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.ebbot.ai/ebbot-docs/core-capabilities/automations/building-workflows.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.