> For the complete documentation index, see [llms.txt](https://help.tillit.cloud/tillit/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tillit.cloud/tillit/knowledge-base/setting-up-tillit/integrations/wire-flow/getting-started.md).

# Getting Started

This page walks you through accessing Wire Flow and building your first workflow.

## Accessing Wire Flow

1. Log into TilliT.
2. Click ***Wire Flow*** in the side menu.

<figure><img src="/files/h6HDZKjthAyyrIOwzyeJ" alt=""><figcaption></figcaption></figure>

## Creating Your First Workflow

1. On the **Workflow List** page, click ***+ New Workflow***.
2. Enter a name and choose **EXPRESS** or **STANDARD**.
3. The editor opens with an empty canvas containing two nodes — Start and End.

<figure><img src="/files/OgefTGwjPQP2IY33GxFd" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/PRYDWIfcf16BlucDIGDY" alt=""><figcaption></figcaption></figure>

| Editor Area          | Purpose                                                    |
| -------------------- | ---------------------------------------------------------- |
| **Toolbar**          | Rename workflow, toggle type, view executions, deploy      |
| **Canvas**           | Drag nodes from the left palette, connect them with arrows |
| **Properties Panel** | Configure the selected node's settings                     |

{% hint style="info" %}
The minimum valid workflow is: **Start Event → Task → End Event**
{% endhint %}

## Basic Steps

1. A **Start Trigger** node is already on the canvas when you open a new workflow.

   <figure><img src="/files/2Eo9jdxxsIsF0rbg9Xul" alt=""><figcaption></figcaption></figure>
2. Drag a task node from the left palette onto the canvas (e.g., ***JSONata Transform***).

   <figure><img src="/files/g7JjoRqSgl5jBWmMZ18s" alt=""><figcaption></figcaption></figure>
3. Drag an ***End Event*** node onto the canvas.

   <figure><img src="/files/LgHyuyVAUC2ExvlwyEFj" alt=""><figcaption></figcaption></figure>
4. Connect the nodes: hover over a node until connection points appear on its edges, then drag from one node to the next.

   <figure><img src="/files/E9fprw5EeXdt4kGpQ6P5" alt=""><figcaption></figcaption></figure>

   <figure><img src="/files/n8u5pdDj2NVWPHPe5FVT" alt=""><figcaption></figcaption></figure>
5. Click a node to configure it in the **Properties Panel**. For example, enter a JSONata expression.

   <figure><img src="/files/Iy8YRg2f8FvgpWY3Jeys" alt=""><figcaption></figcaption></figure>
6. To test the expression, click ***Edit*** to open a full code editor with live preview.

   <figure><img src="/files/mB4xKS6w3ffkaGO6IpXl" alt=""><figcaption></figcaption></figure>
7. Click ***Deploy*** and ***Go Live*** on the toolbar when ready.


---

# 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://help.tillit.cloud/tillit/knowledge-base/setting-up-tillit/integrations/wire-flow/getting-started.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.
