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

# Build a workflow

> React to real customer events with clear branches, waits, and protected actions.

<Note>
  **Status:** Configuration: supported, but dependent on creator setup, provider credentials, or backend configuration.
</Note>

## Workflow model

**Execution shape**

```text theme={null}
Trigger → Conditions or waits → One or more branches → Actions
```

## Configure the graph

1. **Choose a trigger** - Start from a supported event such as a form submission, registration, payment, tag, or customer-path activity.
2. **Set conditions from dropdowns** - Use available CRM fields, statuses, tags, products, webinars, and event data. Do not type system identifiers into node labels.
3. **Add the branches you need** - A decision may have two or many outcomes. Give each branch a clear question-led condition such as “Payment made?”.
4. **Place waits and actions** - Use explicit durations or customer-event waits, then select supported email, CRM, webhook, or platform actions.
5. **Preview and publish** - Run a no-send simulation, resolve diagnostics, publish, then verify a controlled enrollment and its run.

## Runtime authority

The backend enrolls contacts, evaluates conditions, resumes waits, executes provider calls, records runs, and applies idempotent credit or access rules.

<Warning>
  **Published does not mean already triggered**

  A live workflow still needs a matching customer event. Use Runs to verify enrollment, current step, outcome, and any failure.
</Warning>