> ## Documentation Index
> Fetch the complete documentation index at: https://docs.emanate.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Workflows
> Autonomous AI flows that classify and route incoming email, and drive systems that have no API
**Workflows** are autonomous flows you build once and let run. They handle the two kinds of automation that keep
inbound demand moving: **sorting and routing** the email that lands in your inboxes, and **driving a system on your
behalf** when there's no clean integration to plug into.
Open **Workflows** in the sidebar to build and manage them.
## Email routing workflows
An email routing workflow reads each incoming message and decides what should happen to it: which agent handles it,
which person it goes to, whether the AI should draft, reply, or step aside.
* **Classify incoming mail** by intent: a quote request, an order status question, a support issue, or noise to ignore.
* **Route across multiple inboxes** in a single deployment, so one workflow can cover `sales@`, `support@`, and `orders@` at once.
* **Choose the action per branch** with an **AI handoff** toggle: have the agent **draft** a reply, **reply**
automatically, or **hand off** to a human when a message needs a person.
* **Generated for you:** describe the mailbox and what you want in plain English, and Emanate builds the
classification and routing for you to review.
Start every branch on **draft** or **hand off**. Once you trust how a branch behaves, switch the ones you're
confident in to auto-reply. See [Channels](/channels/overview) for how the drafting itself is configured.
## Computer-Use workflows
Some of the systems your business runs on have no API: an ERP portal, a supplier site, an internal tool you log
into by hand. A **Computer-Use workflow** points an AI agent at that web app, has it **log in, click through the
steps, and return a result**, with a recording of what it did.
* **Describe the flow in plain English:** the pages to visit, the fields to fill, what to read back.
* **The agent drives the browser** the way a person would, so no integration work is required.
* **Every run is recorded**, so you can watch exactly what happened and trust the result.
The flagship use of Computer-Use workflows is **building quotes in an ERP**: an incoming RFQ becomes a quote entered
directly into the system that prices and fulfills it. See [Quotes](/demand/quotes) for the end-to-end flow.
## Guardrails
* Routing branches default to drafting or handing off. Automatic sending is something you turn on deliberately.
* Computer-Use runs return a result for review and a recording, so nothing happens invisibly.
## Next steps
The RFQ-to-ERP flow Computer-Use workflows power
How the AI email agent drafts and replies
The inboxes workflows route
Give agents tools to call inside a flow