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

# Workflows

> Event-driven automations that fire when records, fields, or conversations change.

A **Workflow** is an event-driven automation: a trigger fires, a chain of actions runs, and edges decide which path each run takes. Workflows run as soon as the originating event is emitted.

## Anatomy

```mermaid theme={null}
flowchart LR
  Trigger([Trigger]) --> Action1[Action 1]
  Action1 --> Cond{Condition}
  Cond -->|matches| Action2[Action 2]
  Cond -->|else| Action3[Action 3]
  Action2 --> End([End])
  Action3 --> End
```

Every workflow has:

* A single **Trigger**. See [Triggers](/automation/workflows/triggers).
* One or more **Actions** wired up by **Edges**. See [Actions](/automation/workflows/actions) and [Edges & logic](/automation/workflows/edges).
* A status (enabled / disabled).

## When to use a Workflow vs a Sequence

| Use case                                                                | Pick                                       |
| ----------------------------------------------------------------------- | ------------------------------------------ |
| Fires immediately on a record, field, or conversation change            | Workflow                                   |
| Spans days or weeks with explicit waits                                 | [Sequence](/automation/sequences/overview) |
| Runs on a cron schedule over a filtered set of records or conversations | [Job](/automation/jobs/overview)           |
| Background bulk operation                                               | [Job](/automation/jobs/overview)           |

<Note>
  Scheduled, recurring runs are modelled as **Jobs**. An automation that runs on a schedule and selects which records or conversations to process each time. See [Jobs](/automation/jobs/overview).
</Note>

## Authoring

Open **Automations → New workflow**. Pick a trigger from the catalog, add actions onto the canvas, wire them with edges, and enable.

## Run history

Each workflow run is recorded with the data that triggered it, what each action received and produced, and any error message. Open the workflow → **Runs** to inspect.

## See also

* [Triggers](/automation/workflows/triggers)
* [Actions](/automation/workflows/actions)
* [Edges & logic](/automation/workflows/edges)
* [Sequences](/automation/sequences/overview)
* [Jobs](/automation/jobs/overview)


## Related topics

- [Workflow Actions](/automation/workflows/actions.md)
- [Workflow Triggers](/automation/workflows/triggers.md)
- [Install the widget](/comms/chat/widget-install.md)
- [Action Buttons](/surfaces/views/action-buttons.md)
- [Errors](/dev/errors/overview.md)