> ## Documentation Index
> Fetch the complete documentation index at: https://xura.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# What are Flows

> The automation graph Xura walks to accomplish something.

A **Flow** is a directed graph of steps. Xura executes it top-to-bottom, streaming progress into a live trace panel.

## Anatomy

Every Flow has:

* **One trigger** — Manual (click to run) or Scheduled.
* **Zero or more nodes** — data queries, agent calls, actions, conditions, approvals.
* **Edges** — connect nodes; approval / condition nodes emit branching edges.

## Node types

| Type          | Icon       | What it does                                                                           |
| ------------- | ---------- | -------------------------------------------------------------------------------------- |
| **Trigger**   | ▶          | Entry point. Every Flow has exactly one.                                               |
| **Data**      | Database   | Runs a query against your connected data (HubSpot, uploaded files).                    |
| **Agent**     | Bot        | Invokes a stored Agent — a scoped Claude turn with its own tools + skills.             |
| **Action**    | Zap        | Calls one tool (Gmail, MCP, integration). Args interpolate from previous step outputs. |
| **Condition** | Git-branch | Branches to two paths based on a boolean expression.                                   |
| **Approval**  | Lock       | Pauses the run. Presents findings + proposed action to the user.                       |

## The four stages

Regardless of node layout, Xura runs a Flow through four phases that map to tabs in the run panel:

<Steps>
  <Step title="Gather">
    Data nodes run. Xura queries your connected sources.
  </Step>

  <Step title="Analyse">
    Agent / reasoning nodes process the data.
  </Step>

  <Step title="Review">
    If there's an approval gate, Xura pauses here with findings + a proposed action.
  </Step>

  <Step title="Act">
    Action nodes execute — emails sent, tickets created, records updated.
  </Step>
</Steps>

See [The 4 stages](/flows/four-stages) for how tabs auto-advance and how you can navigate back.

## Two ways to create one

<CardGroup cols={2}>
  <Card title="Save an ad-hoc run" icon="floppy-disk" href="/flows/save-as-flow">
    Ask a question from home. Xura plans + runs it. Click **Save as Flow** on completion.
  </Card>

  <Card title="Plan from description" icon="sparkles" href="/flows/plan-from-description">
    Type what you want in the description field. Click **Plan from description** and Xura generates the graph.
  </Card>
</CardGroup>

## Manual editing

You can always add / remove / reorder nodes in the graph editor. The autosave persists changes as you go — no explicit Save button.