# Workflows docs

Describe how work moves across AI, software and people. Start it with an API key, let it stop for a person when it has to, and read every step afterwards.

Trigger: Billing system → Model: Ask the model → Logic: If → Wait: Wait for approval → Tool: Call a tool → Output: Respond

A workflow is a trigger and a list of steps. This one is the Refund approval example; each node shows the step kind it is written as in YAML.

## Where to go next

- [Your first workflow](/docs/workflows/quickstart/): Write a workflow, upload it, start a run with an API key and follow it to the end.
- [Triggers](/docs/workflows/triggers/): The requests a workflow accepts, how a run starts, and what a request does while a run is busy.
- [Step reference](/docs/workflows/steps/ask-the-model/): Every step, what it takes, what it gives back, and an example.
- [Refund approval](/docs/workflows/examples/refund-approval/): A complete workflow that pauses for a person above a threshold.
- [Tool servers](/docs/workflows/tool-servers/): Give every workflow in your organization the same tools from an MCP server.
- [Model calls](/docs/gateway/): Workflows call models through Momor Gateway, so the models can change without the process.