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

# Workflows

> Build durable, inspectable SuperEmber workflows for repeatable work.

Workflows are durable process graphs. They make delegated work repeatable, inspectable, and governable.

Use workflows when a process needs structure: triggers, steps, waits, approvals, connected apps, run history, and published versions.

## Workflow Areas

| Area          | What it does                                                                                              |
| ------------- | --------------------------------------------------------------------------------------------------------- |
| Workflow list | Create and open workflow definitions.                                                                     |
| Studio        | Edit the draft package on a visual canvas.                                                                |
| Node palette  | Add triggers, agents, data steps, actions, waits, approvals, code, connectors, fleets, and sub-workflows. |
| Inspector     | Configure the selected node.                                                                              |
| Settings      | Edit metadata, visibility, bindings, and published versions.                                              |
| Runs          | Review recent workflow runs.                                                                              |
| Templates     | Browse reusable workflow packages with bindings stripped into setup placeholders.                         |
| Inbox         | Resolve open approval, input, choice, and channel-reply waits.                                            |

## Drafts, Test Runs, And Publishing

Workflows start as drafts. You can test a draft before publishing.

Publishing validates the package and creates an immutable version. Runs point to the version that executed, so later edits do not rewrite history.

## Common Workflow Uses

* recurring reporting
* lead qualification
* support triage
* customer follow-up
* approval-before-send flows
* connector-triggered work
* Slack channel intake
* scheduled checks
* research and synthesis
* internal review processes

## What A Workflow Can Contain

Workflows can combine deterministic steps and agent judgment:

* manual, webhook, schedule, and channel-message triggers
* agent tasks
* collaboration groups
* fleet orchestration
* conditions, switches, merge, stop, and error steps
* data set, map, transform, merge, and pick steps
* delay, callback, and channel-reply waits
* human approvals, inputs, and choices
* send-message, HTTP request, and connector action steps
* user-owned code runner steps
* sub-workflows

## When Not To Use A Workflow

Do not create a workflow for every chat request.

Use direct delegation when the task is one-off, exploratory, or best handled as a normal conversation. Create a workflow when the work should repeat, pause, branch, approve, retry, or be inspected later.

Workflow approvals are configured durable waits. They are different from automatic review of a dynamic agent tool call and from Personal Agent connector approvals. See [Approvals, review, and inbox](/product/approvals-and-inbox).