> For the complete documentation index, see [llms.txt](https://docs.wundaflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wundaflow.com/core-concepts/workflows.md).

# Workflows

Typically, when we refer to a *Workflow* we're actually talking about either a Workflow Definition or a Workflow Run.

### Workflow Definition

A Workflow Definition outlines the steps that a Workflow Run will perform. In Wundaflow, a Workflow Definition is named using kebab-case, e.g.: `send-notification-email`.

Workflow Definitions are created within the Wundaflow UI and are made up of at least one Workflow Task. Each Workflow Definition can be viewed in a similar way to a step-function - that is, each task (or, step) must execute successfully before the workflow will move to the next.

#### Workflow Definition Versioning

As with all engineering projects, Workflow Definitions may need to change over time. We support versioning using a simple incrementing integer. Workflow Runs can be started using **latest** or by specifying the `version` number required.

### Workflow Run

A Workflow Run is a specific instance (execution) of a Workflow Definition. Each instance of a Workflow Run can be identified within Wundaflow using a prefixed unique ID (e.g., `flow_4eC39HqLyjWDarjtT1zdp7dc`).

Each Workflow Run starts with an injected context that is persisted throughout the life of the Workflow Run. For a Run triggered from a blockchain event, this would include the related `transaction` and `block` objects.